 So let's change the topic and now we'll talk about secure remote access within Stabime. Hi. Okay, so Bime, we at Bime believe that the PKI and X509 certificates are basically good things, but they are not as convenient enough for more widespread use. So we make some tools to make it a bit more easier. Me, I'm Ilya, I'm a systems and software engineer for quite a while. I work at Bime and I have my own open source project. It's called Next Generation Shell. You can just Google it. Okay, so let's say you have just installed Next Cloud and you want to remotely access it. So you have a few alternatives and apart from citing some more exotic alternatives, you are basically with Let's Encrypt. And so you need to get your own domain name. You need to get the certificate from Let's Encrypt. You configure your web server and then you need to configure your router and maybe firewall. And your other option is to use Bime and that is how it's happening. You install Node.js, you install our NPM package, which is Bime Instacel. You go to the App Store, you download the Next Cloud plugin. After that, you go to our site, you register and you get a token. With that token, you go to the admin screen in the Next Cloud. Here's the screenshot. You paste it in here, click Finish and you are set. You can run the tunnel now. You just press the Start button and here how it looks like when it's running. You get the link. The link is under our domain. You can stop the tunnel anytime if you want to do it for any reason. So how does it work? When you activate the tunnel, the tunnel connects to our server, our tunnel server, and waits for incoming connections. And when a browser connects, it looks up in DNS and the DNS points to our infrastructure. So the connection is made to our tunnel server. But what's actually happening is pretty much end-to-end TLS between the TLS client, which is the browser, and our Bime client code, which runs on your server. So let's say you have more needs than that and you want to connect SSH to your server to do some administration tasks. We can help you with that, too. Bime SSL can be configured for this use case. It's a bit more complex configuration and it looks like this. So we have now two Bime clients and both of them need to have X519 certificates. Only trusted certificates can connect to the server and how it looks like network-wise. On the right side, where's the client, there's a TCP socket exposed, and when you say connect SSH, you connect SSH to localhost, and then it's like you have connected to the SSH on the other end because everything in between is transparent. So why is it secure? Because the proxy server does not have the key to decrypt the traffic, so we cannot decrypt your traffic and we are definitely not interested in doing so because if someone cracks us, we don't want our users to be exposed. Your private key does not leave your server. So it's another layer of security. So sometimes you may experience with different providers some latency issues. So for better performance, we placed our servers in different regions and when Bime client connects to it, it connects to the nearest server so the latency is not bad. We tried, for example, SSH and Remote Desktop and they look fine. They work as almost you connected directly. So if your security needs are more advanced than that, there's Bime Gatekeeper product. It does a lot of things. It can manage users. You can send tokens to your friends to connect, and then they will get their own X, Y, and Y certificates. If your security needs are that advanced, I suggest you come and talk to me because it's a very large topic. And thank you.