We built it because nobody else would.
It started with Starlink, a Minecraft server, and a lot of frustration.
We were running a Minecraft server from home. Starlink. CGNAT. Double-NAT behind a satellite dish bolted to a roof. No public IP. No port-forwarding. No way to tell your friends to just type in an address and connect.
So we tried everything. ngrok — dropped UDP, so no Minecraft. Cloudflare Tunnels — same problem, HTTP/TCP only. Tailscale — beautiful software, wrong answer: it makes a private mesh, not a public address. frp, chisel, rathole — the self-managed path means you already have a public VPS, which is the thing you were trying to avoid needing.
There was no product that said: here is a public IPv6 (and IPv4 when you need it), inject it into your Docker container, every protocol works, unlimited bandwidth — speed-tiered, never data-capped — cancel any time.
So we built it. One container, one IP, no NAT, no proxy. The thing we actually wanted to buy.
We are not a venture-backed startup. We are not trying to be the next Cloudflare. We are two people who got tired of explaining why Minecraft from home requires a side server, and the founding community that funded us to ship it.
Andrew — infrastructure, networking
Mira — DMCA, ops, abuse policy
+ no metered bandwidth, ever — speed-tiered, never data-capped
+ no per-container fees, ever
+ Free plan + paid plans from $0.99/mo
+ 14-day money-back guarantee on all paid plans
+ warrant canary signed monthly · forever
+ RAM-only DB · no traffic logs · architecturally
+ pay by card, PayPal, or Bitcoin Lightning
→ Container-level network injection — not a userspace proxy; each container gets a dedicated interface and a real public IP
→ Per-peer isolation — every container gets its own private network segment; peers cannot reach each other at the relay
→ Post-quantum encryption — mandatory on all connections since initial release; connections without post-quantum negotiation are rejected
→ Unlimited bandwidth — no GB caps, no data overage charges; all tiers unmetered
→ UDP fully supported — ngrok and Cloudflare Tunnels cannot route UDP; we solve this problem
→ 6 relay POPs across 5 regions — US-East · US-West · US-West1 · CA-East · EU-West · EU-Central
→ Automatic agent updates — the sidecar agent self-updates via systemd; no manual intervention required
→ Dispute-triggered teardown — confirmed chargebacks automatically revoke peer access; no manual ops step
→ Bitcoin Lightning payments — annual billing via BTCPay; no payment processor middleman