How it works#
Tollan makes a device reachable from the internet without opening a single inbound port.
The core idea: dial out, never listen#
A traditional "expose a service" setup opens an inbound port and hopes your firewall, NAT, and ISP cooperate. Tollan inverts it.
The agent on your device makes an outbound, mutually authenticated connection to the Tollan relay and keeps it open:
Internet ──▶ Tollan relay ──(mutual TLS)──▶ Agent ──▶ your service
(public address) outbound tunnel 127.0.0.1:8080
(the device dials out) or a LAN hostBecause the tunnel is outbound, it works from behind NAT, CGNAT, and restrictive firewalls with no port-forwarding. Your device is never a listening target on the public internet — the only connection is the one it opened itself.
The pieces#
Agent — a small client on (or next to) your device. It opens the tunnel, keeps it alive, reconnects if the network drops, and connects each incoming request to the service you chose. It's available for Linux, macOS, and Windows (installed from a device bundle) and as the TollanAgent library for ESP32.
Relay — the public entry point. It receives visitors' connections, works out which device each one belongs to (by hostname or by port), and passes the traffic down that device's tunnel. For passthrough routes it never decrypts your traffic (see zero-knowledge passthrough).
Console — where you add devices and routes and manage certificates, your team, and billing, in the console or through the REST API. Changes reach the relay within seconds, with no restart and no dropped tunnels.
What happens on a request#
- A user opens
https://my-nas-anna.a.tollan.app/(or a port likerelay.tollan.ie:19000). - The relay matches the hostname or port to your device.
- Over the tunnel, it asks the device's agent to connect to the service configured for that route.
- The agent connects and streams the connection back; the relay forwards it to the visitor.
- When either side hangs up, that connection closes. The tunnel stays up, ready for the next one.
Two ways an agent answers#
- Handler mode — the device is the service. The agent hands incoming data to your code (this is how the ESP32 handler mode serves a response directly).
- Forwarding mode — the device is a proxy for other hosts on its LAN, so one agent can front a whole network of printers, cameras, and appliances.
In forwarding mode the agent only ever connects to targets on an allowlist you control. See routes and security.
Next: run through it yourself in the Quickstart.