Subscription Pricing

Choose inlets Pro to expose your own services, or Inlets Uplink for customer connectivity.

Evaluating Inlets Uplink?

Reach out with a work email address for a 50% discount in your first month.

Contact Us

inlets Personal

$25 /mo

For personal use only by one individual.

Buy Personal
Features
Feature Included
Tunnels included. 5 tunnels
Cost per tunnel. Included
Tunnel HTTP. Expose multiple HTTP services over a single tunnel HTTP, REST, gRPC, WebSockets, SSE, etc
Tunnel TCP. Expose non-HTTP services over a single tunnel TLS, databases, RTSP, SSH, Kubernetes, etc
TCP multiplexing. Control how TCP ports map to upstream services Multiple TCP ports to one upstream host
High-throughput mode. Opens a separate connection for each remote connection to reduce head-of-line blocking and improve throughput. No
Rate limits. Unlike SaaS based tunnel solutions, there are no restrictive rate-limits on connections or requests/second No
Remote forwarding Expose a private service using an inlets client Yes
Local forwarding Access a remote service through a local port using an inlets client Yes
OAuth for HTTP tunnels Authenticate tunnelled HTTP services that you expose to the Internet GitHub (username, email)
IP Whitelist/ACL Restrict which client IPs can connect to tunnels for defense in depth Yes
Kubernetes Integration. Wire up TCP LoadBalancers using inlets-operator. For Uplink, tunnels are defined via a CRD. inlets-operator for L4 LoadBalancers
Commercial use. No
Update seat count via API. Standard REST API, requires approval for access No
Payment method. Personal card only.
Support
Feature Included
Discord server. Yes
Email support. No
Free onboarding call. No
Buy Personal

inlets Pro Commercial

$125.00 /mo

For use at work, in teams, and shared environments.

Features
Feature Included
Tunnels included. 5 tunnels
Cost per tunnel. 25 USD / mo
Tunnel HTTP. Expose multiple HTTP services over a single tunnel HTTP, REST, gRPC, WebSockets, SSE, etc
Tunnel TCP. Expose non-HTTP services over a single tunnel TLS, databases, RTSP, SSH, Kubernetes, etc
TCP multiplexing. Control how TCP ports map to upstream services Multiple TCP ports to one upstream host
High-throughput mode. Opens a separate connection for each remote connection to reduce head-of-line blocking and improve throughput. No
Kubernetes Integration. Wire up TCP LoadBalancers using inlets-operator. For Uplink, tunnels are defined via a CRD. inlets-operator for L4 LoadBalancers
Rate limits. Unlike SaaS based tunnel solutions, there are no restrictive rate-limits on connections or requests/second No
Remote forwarding Expose a private service using an inlets client Yes
Local forwarding Access a remote service through a local port using an inlets client Yes
OAuth for HTTP tunnels Authenticate tunnelled HTTP services that you expose to the Internet Google or GitHub (username, email, organisation)
IP Whitelist/ACL Restrict which client IPs can connect to tunnels for defense in depth Yes
Commercial use. Yes
Update seat count via API. Standard REST API, requires approval for access Yes
Payment method. Corporate card
Support
Feature Included
Discord server. Yes
Email support. Yes
Free onboarding call. No

Inlets Uplink

$250 /mo

For service providers and managed access to customer services.

Buy Uplink
Features
Feature Included
Tunnels included per cluster. 10
Cost per additional tunnel. 25 USD / mo
Tenancy model. Kubernetes namespaces, IAM, and network policies
Tunnel HTTP. Expose multiple HTTP services over a single tunnel HTTP, REST, gRPC, WebSockets, SSE, etc
Tunnel TCP. Expose non-HTTP services over a single tunnel TLS, databases, RTSP, SSH, Kubernetes, etc
TCP multiplexing. Control how TCP ports map to upstream services Multiple upstream hosts with port remapping
High-throughput mode. Opens a separate connection for each remote connection to reduce head-of-line blocking and improve throughput. Yes
Kubernetes Integration. Wire up TCP LoadBalancers using inlets-operator. For Uplink, tunnels are defined via a CRD. Define tunnel servers via namespaces and CRDs
Rate limits. Unlike SaaS based tunnel solutions, there are no restrictive rate-limits on connections or requests/second No
Remote forwarding Expose a private service using an inlets client Yes
Local forwarding Access a remote service through a local port using an inlets client Yes
OAuth for HTTP tunnels Authenticate tunnelled HTTP services that you expose to the Internet n/a
IP Whitelist/ACL Restrict which client IPs can connect to tunnels for defense in depth Yes
Commercial use. Yes
Update seat count via API. Standard REST API, requires approval for access Yes
Payment method. Corporate card
Support
Feature Included
Discord server. Yes
Email support. Yes
Free onboarding call. Yes
Buy Uplink

What you get

Shared capabilities across inlets Pro and Uplink, with the detailed plan differences in the pricing tables above.

  • HTTP and TCP tunnels for public endpoints or private access.

  • Tunnel clients on Windows, macOS, Linux, containers and Kubernetes.

  • Remote and local forwarding with self-hosted control over your data plane.

  • Kubernetes support for ingress, load balancers, operators and hybrid environments.

  • Multiple domains and services per tunnel where the architecture allows it.

How many licenses do we need?

A license is needed for each inlets TCP or HTTP client that you intend to run, however a single tunnel can multiplex many different services.

There are two ways to multiple different sites or domains:

  • 1. With an inlets HTTP tunnel server/client, you can specify different domains for different services.
  • 2. With an inlets TCP tunnel you can expose ports 80 and 443 from a reverse proxy or Ingress Controller to act like a cloud load-balancer.

How many domains or sites can I expose over a single tunnel?
Inlets HTTP tunnels can multiplex many different domains over a single client. If you expose a reverse proxy or a Kubernetes Ingress Controller using a TCP tunnel, then you can expose as many sites as you want.
When do I need multiple HTTP tunnels clients?
You can expose as many HTTP endpoints as you like so long as they are reachable by the tunnel client. If your sites are spread across isolated networks, then you would need one per network.
Can I connect multiple clients to the same HTTP tunnel server?
Yes, this is possible, even if the tunnel clients are in different networks. Make sure you specify the domain name to use for routing. When the same name is given by multiple clients, the server will load balance.
Does Uplink charge extra for high-availability of tunnel clients?
For Uplink, you can have up to two identical replicas of the same tunnel client connected to the same tunnel server, at no additional cost.
When should we consider Uplink over inlets Pro?
Use Uplink when your product needs to create and manage tunnels for customers on a dynamic basis. Uplink also supports high bandwidth and throughput use-cases through an additional stream per connection, called demux mode.
How does licensing work for Inlets Uplink?
A subscription is required for each Kubernetes cluster, which includes 10 tunnels. Additional tunnels come in bundles of 5 at 25 USD / mo per tunnel. Volume pricing available for high quantities.
How do we update seat count as we provision new tunnels?
For inlets Pro standalone and inlets Uplink, an API can be enabled subject to approval to update the seat count for a subscription as new tunnels are provisioned.
How do we pay for dev or test installations of Inlets Uplink?
Every cluster requires a license, whether used for testing, non-production, or live customer traffic. For dev and testing clusters, we are currently offering a promotion. Get a perpetual 50% discount on non-production installations subject to case-study being published on our blog.

Ask us a question

If you have questions for us, you can get in touch below.

Contact Us