With inlets you are in control of your data, unlike with a SaaS tunnel where shared servers mean your data may be at risk. You can use inlets for local development and in your production environment. It works just as well on bare-metal as in VMs, containers and Kubernetes clusters.
inlets is not just compatible with tricky networks and Cloud Native architecture, it was purpose-built for them.
Common use-cases include:
- Exposing your local endpoints on the Internet
- Self-hosting Kubernetes or K3s clusters
- Deploying and monitoring apps across multiple locations
- Supporting your customers remotely
- Hybrid cloud for legacy TCP applications
Every inlets tunnel has two parts: its server and its client, but they're one binary and can run entirely within userspace. This makes it very easy to customise and distribute for different use-cases.
- It's a single binary for MacOS, Windows and Linux
- Works on bare-metal, in VMs, in containers and on Kubernetes
- Set it up manually, with Helm, or with a Kubernetes Operator
inlets just works, why not test it and see?
The tunnel client usually runs in a private network, and the server may run on a network with a public IP. When the two are connected, it's like the private server is actually on the Internet.
Inlets is not a VPN, it's for exposing local services on another network or on the Internet. You can read more in our FAQ
- Host your tunnel server wherever you want for low latency
- Use it in development and production environments
- Expose as many HTTPS websites as you like
- Expose whatever TCP ports you need
- Get more done, without running into rate-limits imposed by a service provider
- Use your own DNS instead of paying per domain.
A valid license key or Gumroad subscription is required to launch or deploy inlets. By using the software you agree that you have purchased a license and are bound by the terms of the End User License Agreement (EULA)
Find out more:
- Kubernetes Ingress with the inlets-operator
- Expose Ingress with the helm chart
- Reliable local port-forwarding from Kubernetes
- How to connect your on-premises databases to Kubernetes in the cloud
- How to monitor multi-cloud Kubernetes with Prometheus and Grafana
- Tutorial: Expose one or more local HTTP services via HTTPS
- When you can't get a static IP from your ISP
- The Simple Way To Connect Existing Apps to Public Cloud
- Tutorial: Tunnel a private Postgresql database
You'll need a subscription for inlets, but can pay monthly or save money through an annual subscription.
Both the client and server are contained within the same binary.
It is recommended that you use inletsctl, or inlets-operator to create inlets tunnel servers, but you can also create these manually.
The inlets binary can be obtained as a stand-alone executable, or via a container image.
-
As a binary:
curl -SLsf https://github.com/inlets/inlets-pro/releases/download/0.9.23/inlets-pro > inlets-pro chmod +x ./inlets-proOr find a binary for a different architecture on the releases page
See also CLI reference guide
-
As a container image
A container image is published at as
ghcr.io/inlets/inlets-proSee the various tags available: View tags
-
Kubernetes Helm charts & Operator
Run ad-hoc clients and servers on your Kubernetes clusters
See the helm chart
Or try the Operator if you want an integration for your LoadBalancers on Kubernetes.
If you want to contact someone about inlets, please feel free to get in touch via this form: