Multiple Hubs

Restunnel supports running multiple independent hubs on different servers. Each hub manages its own exit nodes, its own proxy, and its own authentication — hubs don't know about each other.

Why Multiple Hubs

• Different servers, different proxies. An AI agent on Hetzner uses Hub A, a crawler on AWS uses Hub B. Each gets its own exit nodes.
• Geographic diversity. Hub in Europe with a European phone, hub in Asia with an Asian phone. Route traffic through the region you need.
• Isolation. If one hub has issues, the other is unaffected.

Exit Nodes Connect to Multiple Hubs

A single device can serve as an exit node for multiple hubs simultaneously:

📱 Phone (LTE)
   ├── Connected to: Hub A (Hetzner)
   └── Connected to: Hub B (AWS)

💻 Laptop (Home WiFi)
   └── Connected to: Hub A (Hetzner)

Each hub connection is independent — separate Noise sessions, separate authentication, separate traffic. Pausing or removing one hub connection doesn't affect the others.

On Android

Tap Scan QR to Enroll for each hub. The app shows all hubs in a list with individual connection status.

On Desktop (macOS)

Click Add Hub and paste each hub's enrollment URL. The menu bar shows aggregate status.

On CLI

Run separate restunnel-node instances, each with its own --data-dir:

# Connect to Hub A
restunnel-node --data-dir /var/lib/restunnel-node-a

# Connect to Hub B (separate terminal or service)
restunnel-node --data-dir /var/lib/restunnel-node-b

Hubs Are Fully Independent

• Each hub has its own keypair and its own list of authorized nodes
• Enrolling with Hub A doesn't grant access to Hub B
• Revoking a node on Hub A doesn't affect Hub B
• No coordination, no shared state, no central registry