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.

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

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

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:

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 https://github.com/inlets/inlets-pro/releases/download/0.9.23/inlets-pro > inlets-pro
chmod +x ./inlets-pro

Or find a binary for a different architecture on the releases page

See also CLI reference guide

Want to speak to someone?

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

Contact us

soitun/inlets-pro

ErrorLooks like something went wrong!

About

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Languages

Error
Looks like something went wrong!

Packages