October 10, 2026
OpenTunnel moved to Rust and 10 Fly.io regions: tunnels reconnected on their own
The OpenTunnel backend was rewritten in Rust and moved from a Cloudflare Worker to 10 Fly.io machines, per a tweet from Oct 10, 2026. Clients reconnected on their own, with no manual steps, and tunnels opened during the move ran through a fallback path on the Worker.
dax
@thdxr
I asked opencode to rewrite the opentunnel backend in Rust and move it from Cloudflare to 10 Fly regions around the world. It carefully ran the migration, and all tunnels simply reconnected to the new system. Nice.
· 75.4K views
The tweet's author had OpenCode rewrite the backend in Rust. The server used to run on a Cloudflare Worker with Durable Objects, a certificate Workflow, and a TCP relay on AWS. Now it's a single binary on Fly.io, with ten machines in the iad, ord, sjc, gru, lhr, fra, bom, sin, nrt and syd regions behind one anycast address. The HTTP API, bridge protocol, hostnames, and tokens are unchanged, so clients didn't need any changes.
How to start. Install with brew install anomalyco/tap/opentunnel or npm install -g opentunnel. The command opentunnel route add 3000 creates a tunnel on first run and prints a public address like https://<id>.<id>.opentunnel.xyz. The --name api flag gives the address a readable name. The name is not a form of protection: anyone who knows the address can reach the service.
Releases are coming almost daily: eight CLI versions shipped between Oct 7 and Oct 10, the latest v0.5.0.
Source