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?

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

Do I need to pay to have high-availability of tunnel clients?

You can have up to three identical replicas of the same inlets tunnel client connected to the same tunnel server, at no additional cost.

When should we consider uplink over the stand-alone version?

Inlets uplink is for service providers and SaaS companies who need to create tunnels on a dynamic basis.

When do I need multiple TCP tunnels clients?

As a default, a TCP tunnel can only expose ports from a single upstream, however the

inlets-pro sshmux

command can be used to multiplex multiple SSH endpoints or TLS endpoints over one TCP tunnel.