Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Inlets reinvents the concept of a tunnel for a Cloud Native world.

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.

For production and development too.

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

What's it look like?

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

Quick tunnel

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.

How's it different to other solutions?

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.

Getting started

Find out more:

For cloud natives

For modernizing apps and exposing private services

Getting inlets

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 > inlets-pro
    chmod +x ./inlets-pro

    Or 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

    See 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.

Want to speak to someone?

If you want to contact someone about inlets, please feel free to get in touch via this form: