inlets PRO - Secure HTTP and TCP tunnels that just work
inlets PRO replaces SSH tunnels, VPNs, SaaS tunnels, port-forwarding and dedicated connections.
Sound like it could be useful? Show your support with a GitHub Star
It's compatible with any HTTP (L7) or TCP (L4) software and can work through the most challenging network conditions like captive portals, HTTP proxies, firewalls and NAT to give you access to services.
You can run the tunnel as a process, container or Kubernetes Pod, and it's easy to configure or automate it.
Example of inlets PRO with a TCP tunnel for hybrid cloud. Kubernetes is optional
It's up to you whether you want to use inlets PRO as a way of exposing private traffic to the Internet, or whether you just want to make it available privately to your organisation on another network for hybrid cloud.
You can learn specific use-cases and problems that inlets PRO can solve for Kubernetes below, or check out how it can be used as a Software Defined Network or VPN replacement in the docs
- Get Kubernetes LoadBalancers for customer demos or local development
- The Simple Way To Connect Existing Apps to Public Cloud
- Reliable local port-forwarding from Kubernetes
- How we scaled inlets to thousands of tunnels with Kubernetes
- Learn how to manage apps across multiple Kubernetes clusters
inlets-pro forwards TCP or HTTP / REST traffic over an encrypted websocket secured with TLS.
A quick overview showing a HTTP tunnel to expose a private Node.js service on a private network.
Whichever type of service is used, inlets-pro supports load-balancing of connections and multiple clients connected to the same server. When automatic TLS is used (default) then all data is encrypted through a TLS connection.
For TCP services:
- Tunnel any L4/TCP protocols - such as databases, remote desktop, gRPC, HTTP/2 and SSH
- Legacy protocols which do not support TLS are automatically "upgraded" through the encrypted tunnel
- Pass-through TLS support for reverse proxies, Kubernetes, IngressControllers and TLS
- Multiple TCP ports are supported and can be updated by the client
For HTTPS/REST services:
- Reverse proxy with support for multiple upstreams through using the
- Automatic Let's Encrypt for exposed using HTTP01 challenge
- Support for websockets
- A single static binary is available for MacOS, Windows, and Linux. Arm is also supported
systemdunit files for automatic restarts and logging from
- Official container image available on public registry
- Kubernetes integration via
inlets-operator, YAML or Helm
License & Pricing
inlets-pro is a L4 and L7 TCP tunnel, service proxy, and load-balancer product distributed under a commercial license.
In order to use inlets-pro, you must accept the End User License Agreement - EULA. The server component runs without a license key, but the client requires a valid license.
You can purchase a license for personal or business use on the inlets website
inlets-pro can be used to provide a Public VirtualIP to private, edge and on-premises services and Kubernetes clusters. Once you have set up one or more VMs or cloud hosts on public cloud, you can utilize their IP addresses with inlets-pro.
You can get incoming networking (ingress) to any:
- gRPC services with or without TLS
- Access unsecured private services like MySQL, but with TLS link-encryption
- Command & control of Point of Sale / IoT devices
- SSH access to home-lab or Raspberry Pi
- TCP services running on Linux, Windows or MacOS
- The API of your Kubernetes cluster
- A VM or Docker container
For example, rather than terminating TLS at the edge of the tunnel, inlets-pro can forward the TLS traffic on port
443 directly to your host, where you can run a reverse proxy inside your network. At any time you can disconnect and reconnect the tunnel or even delete the remote VM without loosing your TLS certificate since it's stored locally.
See also: reference architecture diagrams
You can follow one of the tutorials above, or use inlets PRO in three different ways:
- As a stand-alone binary which you can manage manually or automate
- Through inletsctl which creates an exit server with
inlets-pro serverrunning with systemd in one of the cloud / IaaS platforms such as AWS EC2 or DigitalOcean
- Through inlets-operator - the operator runs on Kubernetes and creates an exit server running
inlets-pro serverand a Pod in your cluster running
inlets-pro client. The lifecycle of the client and server and exit-node are all automated.
Tutorials and examples
Get the binary
Both the client and server are contained within the same binary.
The inlets-pro binary can be obtained as a stand-alone executable, or via a Docker image.
As a binary:
curl -SLsf https://github.com/inlets/inlets-pro/releases/download/0.8.9/inlets-pro > inlets-pro chmod +x ./inlets-pro
Or fetch via
inletsctl download --pro
Or find a binary for a different architecture on the releases page
See also CLI reference guide
A docker image is published at
See the image on GitHub Container Registry
Automatic tunnel servers and clients through LoadBalancer/Ingress
See also: inlets-operator
Kubernetes Helm charts
Run ad-hoc clients and servers on your Kubernetes clusters
See chart for the inlets-pro TCP client and server mode
A separate helm chart is available to inlets-pro customers for the HTTP client and server mode
Pre-provisioned inlets tunnel servers
Sample Kubernetes YAML files
Get in touch
Got questions? Send us an email to [email protected].