Skip to main content
Tunnelbyte has three tiers. You can go all the way up without ever talking to a human.
AnonymousFree accountPaid
Signupnoneemail magic linkcard on file (Stripe)
Bytes (rolling 7 days)1 GiB5 GiBunmetered
Session time (rolling 24 h)30 min2 hunmetered
Concurrent tunnels2210 (raisable on request)
Regionanyanyany
API accessself-service tokenself-service tokenself-service token
Pricingfreefree€0.01/min + €0.02/GiB
billed monthly via Stripe
Get theretunnelbyte sintunnelbyte signuptunnelbyte upgrade
Caps are enforced server-side and tracked independently per dimension. Check the live values any time with GET /v1/usage or watch them tick in the status line while a tunnel is up.

​
Anonymous

For trying it out and one-off jobs. Token is bound to your install fingerprint (/etc/machine-id on Linux, IOPlatformUUID on macOS). Reinstalling on the same machine reuses the token; spinning up a fresh VM gets a fresh one.

​
Free account

For hobby projects and dev work. Email + magic link, no password. The signup is one curl from your terminal: 
$ tunnelbyte signup
5 GiB per rolling 7-day window for bytes, 2 h per rolling 24-hour window for time, no per-session wall-clock cap, and the ability to use the account across machines (each device runs tunnelbyte login). For anything serious - scrapers, CI, ad / SEO verification, synthetic monitoring, regional API access. Run tunnelbyte signup first (if you’re still on the anonymous tier - paid needs an account-on-file email for invoices), then tunnelbyte upgrade to add a card via Stripe Checkout. From then on, sessions bill at €0.01/min + €0.02/GiB (pro-rated per second and per byte, no daily quota). tunnelbyte billing opens the billing portal to update cards, view invoices, or cancel.

​
How billing works

  • €0.01 per minute of session duration (start → tear-down), pro-rated per second. A 30-second curl costs ~€0.005, not a full cent.
  • €0.02 per GiB of traffic through the tunnel (sum of bytes_in + bytes_out), pro-rated per byte.
  • Both metered live; the running cost shows in the status line while a tunnel is up (e.g. · €0.04).
  • Invoiced monthly via Stripe. The canonical billed total is whatever your monthly invoice says.
  • All prices and invoices are in EUR. Stripe Checkout will display the amount in your local currency for context, but the charge on your card is in EUR; your bank applies its own FX rate.

​
No per-session cap

Paid sessions run as long as you keep them up; an idle session (no handshake for 5 minutes) is reclaimed by the node. Re-run tunnelbyte <region> any time for a fresh session - no quota consequences.

​
Why not “Pro” / “Team” / “Enterprise”

There’s no per-seat pricing. Multi-user setups happen by sharing an API key inside your CI / infra. The price model is pure usage, so a team using one key is billed identically to a team using one key per developer. What sharing a key means in practice:
  • Anyone holding the key can create sessions, see all sessions on the account via GET /v1/sessions/{id}, and read aggregate usage via GET /v1/usage. There’s no per-developer isolation under one key.
  • Concurrent-tunnel cap (10 on paid by default) counts sessions across the whole account, not per device. Ten parallel tunnels usually covers a small team’s CI + a few devs comfortably. If you regularly bump up against it, email hello@tunnelbyte.dev and we’ll raise it on your account.
  • If you need per-developer usage attribution or per-key revocation, sign up multiple accounts. We don’t issue scoped child keys in v1.

​
What’s planned

The current tier structure reflects datacenter-only infrastructure. More datacenter regions are planned as demand justifies them - please email hello@tunnelbyte.dev if there’s one you’d be interested in. Per-key scoping (child tokens with their own quotas and visibility) is also on the wishlist. Residential-IP egress is not on our v1 roadmap. It’s a different product with different economics and ethics, and we’d rather say “not us” than ship a watered-down version. If your use case actually needs residential IPs, this isn’t the right tool yet.

​
Trying to switch tiers

  • Anonymous → Free is a one-way upgrade (tunnelbyte signup). The same install fingerprint stays.
  • Free → Paid = tunnelbyte upgrade. Card on file; next session bills.
  • Paid → Free = cancel from the billing portal (tunnelbyte billing). You drop back to the free tier’s caps at the end of the current billing period.