
Inlets can tunnel either HTTP or TCP traffic: If you have questions or cannot find what you need, there are options for connecting with the community at the end of this page. These guides walk you through a specific use-case with inlets. inlets also supports local forwarding and can be used to replace more cumbersome services like SSH, complex VPNs or expensive direct connect uplinks. There is more that inlets can do for you than exposing local endpoints. You may be working with webhooks, integrating with OAuth, sharing a draft of a blog post or integrating with a partner's API.Īfter deploying an inlets HTTPS server on a public cloud VM, you can then connect the client and access it. One of the most common use-cases is to expose a local HTTP endpoint on the Internet via a HTTPS tunnel. Over that private connection, you can then tunnel HTTPS or TCP traffic to computers in another network or to the Internet. Inlets tunnels connect to each other over a secure websocket with TLS encryption. What is your strategy for connecting existing applications to the public cloud? Read: The Simple Way To Connect Existing Apps to Public Cloud. Deploying and monitoring apps across multiple locations.Self-hosting from a homelab or on-premises datacenter.Exposing local endpoints on the Internet.Inlets is not just compatible with tricky networks and Cloud Native architecture, it was purpose-built for them. It works just as well on bare-metal as in VMs, containers and Kubernetes clusters. You can use inlets for local development and in your production environment. With inlets you are in control of your data, unlike with a SaaS tunnel where shared servers mean your data may be at risk. If you have comments, questions or suggestions, please let us know on GitHub. This rewrite aims to be less verbose, to connect you with practical task-driven examples and to make it easier to find what you need. Welcome to the new inlets documentation site launched Nov 2021.
