tunll 1.0.0 - preview

Serve introspectable tunnels from localhost, internal web apps and containers on public internet.

Hosted and self-hosted options.

1 minute setup

Download

Visit our launch page on Producthunt!

We have launched! Join the community, give feedback and help improve tunll!

How it works

The tunll agent and server are connected together and creates a tunnel from the Internet edge to localhost or internal web apps.

Features

Serve apps and web services on the public internet

  • Tunnel localhost on the public internet
  • Share in-progress work
  • Tunnel into Docker containers
  • Tunnel into Kubernetes containers
  • Easily create webhooks for 3rd party web apps
  • Access IoT devices in the field
  • Connect to your customers' privately running software
  • Tunnel gaming servers on the internet

Works on any OS and CPU architecture

Windows, Linux, Mac OS, x64, ARM64, Docker and Kubernetes containers

Security and Authentication

Secure your apps at the Tunll edge with TLS certificates and basic authentication.

Observability

Inspect and replay HTTP traffic

Agent Usage

Example agent usage. You can copy and paste from commands below.

Serve localhost on the internet

tunll 5000 --authtoken YOUR_AUTHTOKEN

	# above is equivalent to: 

	tunll http 5000 --authtoken YOUR_AUTHTOKEN

Forward multiple local addresses 

tunll --forward localhost:5000 --forward ******.tunll.io,localhost:2222 --authtoken YOUR_AUTHTOKEN

	# above tunnels: 

	# https://abcdefghijkl.tunll.io => http://localhost:5000
	# https://abcdef.tunll.io => http://localhost:2222

Use custom hostname

tunll 5000 --hostname mytunnel.example.com --authtoken YOUR_AUTHTOKEN

	# or

	tunll --forward https://mytunnel.example.com,localhost:5000 --authtoken YOUR_AUTHTOKEN

	# both commands above tunnels:

	# https://mytunnel.example.com => http://localhost:5000

Various examples

tunll 8080                                                 # forward tunll.io subdomain to http port 8080
tunll http 8080                                            # forward tunll.io subdomain to http port 8080
tunll http example.com:8080                                # forward traffic to example.com:8080
tunll http 8080 --subdomain bar                            # request subdomain 'bar.tunll.io'
tunll http 8080 --hostname example.com                     # request custom domain (DNS NAME)
tunll http 8080 --basic-auth john:passwd                   # enforce basic auth on tunnel endpoint
tunll -f localhost:8080                                    # forward tunll.io subdomain to port 8080
tunll -f 8080 -f https://localhost:8090                    # tunnel http port 8080 and https port 8090
tunll -f https://mydomain.eu.tunll.io,localhost:8080       # tunnel from reserved subdomain
tunll -f https://dev.example.com,https://localhost:8080    # tunnel from reserved domain (DNS NAME)
tunll -f https://*.example.com,https://localhost:8080      # tunnel from wildcard reserved domain (DNS NAME)
tunll -f http://10.0.0.10
tunll 8080 --host-header example.com                       # rewrite the host header to 'example.com'
tunll 8080 --host-header rewrite                           # rewrite the host header to endpoint hostname
tunll -f ******.tunll.io,localhost:8080                    # choose length of subdomain with stars, minimum 6

Tunnel any TCP port such as SSH in this example 

tunll tcp 22 --authtoken YOUR_AUTHTOKEN

Connect to Self-Hosted server mytunllserver.example.com

tunll 5000 --server-address mytunllserver.example.com --server-port 3333 --authtoken YOUR_AUTHTOKEN

Self-Hosted Server Usage

Example tunll server usage. You can copy and paste from commands below.

Run self-hosted server

tunll server --listen-port 3333 \
--authtoken YOUR_AUTHTOKEN

# Or, with standalone server executable you can skip the 'server' argument: 

# tunllserv --listen-port 3333 ...

Run self-hosted server with limits

tunll server --listen-port 3333 \
--limit-connections 100 \
--limit-connection-rate 120 \
--authtoken YOUR_AUTHTOKEN

Run self-hosted server in a server cluster

Multiple load-balanced tunll servers

tunll server --listen-port 3333 \
--cluster CLUSTER_ID \
--authtoken YOUR_AUTHTOKEN

Hosted Plans

Connect tunll agents to our globally distributed hosted edge servers.

All features are free during our preview period. Your feedback is very much welcomed!

Free

$0

  • Ephemeral/Random Domains
  • Serve HTTP Apps, Webhooks, APIs, and TCP-based systems
  • Automated SSL/TLS certificates
  • Request Inspection & Replay
  • Restricted bandwidth and usage

Preview

$0 / preview period

  • ALL FREE FEATURES
  • Custom Domains
  • Wildcard Domains
  • TLS Edges and Tunnels
  • Role Based Access Control
  • Agent ACLs
  • IP Restrictions
  • Add as many as you need:
  • Team Members
  • Domains & TCP Addresses
  • Agents


Sign up for Free Preview to Get Started


Self-Hosted Plans

Download and host the tunll server executable on your own server(s) and connect the tunll agents to your own running tunll servers.

After our preview period we will publish additional self-hosted plans.

All Self-Hosted plans include

Run tunll server executable on your own computers/servers
Zero setup cost
No connection rate-limiting
Any public TCP ports
Unlimited custom domains
A tunnel, as related to Self-Hosted plans, is a tunll agent and server connected together.

Preview

Used during preview period

$0 / preview period

5 tunnels
  • Limited to 2 hour sessions


Sign up for Free to Get Started


Questions or need for a custom plan?

Contact us at

support@tunll.com

Frequently Asked Questions

What is the difference between the Hosted and Self-Hosted plans?

With a Hosted plan you only have to run the tunll agent on your own computers. The agent connects (creates a tunnel) to our secure public hosted edge servers. You automatically get a public address on the internet to which you can direct your traffic. The edge traffic will be tunneled to your running agent and from your agent to your forwarded address.

With a Self-Hosted plan you can download the tunll server executable and run it on your own computer(s)/server(s). You can connect any custom domain(s) and TLS certificates to the self-hosted tunll server. You connect your tunll agents to the tunll server(s) you have running.

Do the Self-Hosted servers need connectivity to the Internet?

Yes. They need outbound connectivity to the internet in order to connect to the tunll API web services in order to handle licensing via the authentication token.

Can I try before I buy?

Yes. You can try both the Hosted and Self-Hosted plans for free with restrictions.

Do you have a annual plans?

Contact us. We do not yet have any published annual plans.

Can I use my license at work and at home?

Yes.

Can I add more tunnels during a subscription period?

Yes, you can upgrade or downgrade your subscription at any point. The difference will be paid pro-rated.

How long will the preview period last?

Until we consider it to be stable. We assume we'll be in preview for about 1 month.

Share if you like tunll

Share on Twitter

Follow us on Twitter

Contact Us

tunll

tunll is a product of Codemander AS and was built by Kurt I. Gronbech as the tunneler for Codemander - Online Development Platform.

Industriveien 5
7072 Trondheim, Norway