Support

Register an account, then submit a public key from the Keys panel (proven via a signed challenge nonce) — this key encrypts your traffic over the relay. Build a route by picking a hop count and exit country, then download the client and drop in the route's config to connect.

Every account gets a permanent deposit address for each supported network, shown as a QR code on the Billing panel — choose Solana, Bitcoin, or Ethereum first. Send SOL, USDC, or USDT on Solana, BTC on Bitcoin, or ETH on Ethereum — the currency is auto-detected on-chain and credited to your balance once confirmed. There's nothing to regenerate between deposits.

If your balance can't cover a renewal (or auto-renew is off), the account is suspended and new routes are paused — existing keys and configuration aren't deleted. Top up your balance and the very next billing cycle automatically reactivates the account, no manual steps needed.

Yes — subscribe to a different plan any time from the Billing panel. The new plan's price is debited from your balance immediately and your renewal date resets from that point.

No — relay is protocol-blind by design. Every hop forwards encrypted bytes and has no visibility into what's riding on top of the connection, so there's nothing application-layer to log even if a hop wanted to.

Only your Entry node, since your client connects to it directly. Middle nodes never see it — they're addressed by rotating ._ztr aliases and only know the hop before and after them. The destination only ever sees your Exit node's address.

No. There's no HTTP layer anywhere in the relay path — it's a raw TCP/UDP tunnel. See the About page for exactly what that does and doesn't cover.

Open the route's diagram in your dashboard to see which hop is affected. If it's the Exit node, you can swap it for another one in the same or a different country right from the route detail view — no need to rebuild the whole route.

Naturally — every time the client Python package calls set_tunnel(), it establishes the route with fresh Middle aliases, on every plan. Plans that include on-demand rotation also let you force new aliases for an existing route from the dashboard at any time, without reconnecting — check your plan's features on the Pricing page.

Yes — map your IPv4 to a ._ztr alias from the Address Aliases panel and hand that alias out as the destination instead of the raw address. One IPv4 can back as many aliases as you want, so mint a separate one per person: revoking any single person's access is just deleting their alias — everyone else's alias, and the real IP behind all of them, is untouched.