Frequently asked questions

Zorven is a connectivity platform that runs on your own server: it publishes your local services (website, API, database, game server) on your own domain with one command, joins your devices into a private network, and lets you decide who reaches what. Tunnels, private networking and zero-trust access live in one panel.

Yes. Zorven is open core (AGPLv3); install the server component on your own server and keep all traffic within your infrastructure. The hosted service is also available at panel.zorven.app.

Zorven is self-hostable and open core; you control your data and domains. Beyond tunnels, it brings a private network (Zorven Network), a policy engine, Secret Vault, device policies, a request inspector and load balancing into one platform.

The Free plan costs nothing and needs no credit card: 2 clients, 2 tunnels and 5 GB of monthly traffic. Paid plans add custom domains, higher limits and team features. See the pricing page for details.

Download the desktop app for Windows or install the CLI in one command: on macOS and Linux curl -fsSL https://zorven.app/install.sh | sudo bash, on Windows via PowerShell irm https://zorven.app/install.ps1 | iex. Then link your account with zorven authtoken <token> and publish with zorven http 3000.

Yes (Hobby and above). Once you verify a domain via DNS, its subdomains (like api.example.com) can be attached to tunnels without extra verification. TLS certificates are issued automatically.

Besides HTTP/HTTPS and WebSocket, raw TCP, SNI mode and UDP tunnels are supported. Share SSH, PostgreSQL/MySQL, Redis, RDP and game servers such as Minecraft. You pick the protocol per tunnel in the panel.

Yes. Use a raw TCP tunnel for Minecraft Java (TCP 25565) and a UDP tunnel for Bedrock (UDP 19132). In reserved-port mode, visitors connect via zorven.app:PORT with no extra setup.

No. The client connects outward, so it works without router port forwarding, with a dynamic IP, and behind CGNAT.

Yes. In the panel you see the headers and body of every incoming request and can replay it with one click. Log retention is between 1 and 90 days depending on your plan, and it is enforced. Requests rejected early by authentication, policy or IP rules (401, policy, IP) are not recorded.

Yes. Per tunnel you can apply Basic Auth (username and password) or Google/GitHub visitor sign-in; Pro and above also get an IP allowlist. With the policy engine you define rules such as rate limits, deny, redirects, enforced mTLS, WAF and webhook signature verification, with no code (Pro and above).

Traffic is encrypted with TLS. When you run Zorven on your own server, your tunnel traffic does not reach a third party (if you enable Google/GitHub sign-in, those providers take part in authentication). In the panel, secrets are stored encrypted in Secret Vault; an audit log and 2FA protect your account.

A private network that joins your devices without exposing them. On the client you enter it through a local SOCKS5 proxy with zorven connect. It is available on Team and above.

In the self-hosted model, traffic and data stay on your own server, an architecture that suits organizations that do not want data passing through a SaaS abroad. For KVKK requests, see the KVKK notice and write to kvkk@zorven.app.

If you believe a *.zorven.app address is being abused, email abuse@zorven.app. The platform can freeze suspicious tunnels and runs automated phishing scanning.

Yes. In the Gmail app (Android and iOS) add an account, choose "Other" or "Personal (IMAP)"; server mail.zorven.app, IMAP 993 (SSL/TLS), SMTP 587 (STARTTLS) or 465 (SSL/TLS). Use the app password you created in the dashboard. Outlook, Apple Mail and Thunderbird work too.

IMAP only; POP3 is not offered. The Gmail website adds external accounts over POP3, so you cannot add this account on gmail.com. Use the Gmail app or another IMAP client.

The same plan rule as webmail applies: sending to external recipients is available on Enterprise. Internal platform addresses are delivered on every plan.

Enable the web door (Pro and above). The tunnel gets a door URL like door--label.zorven.app; once the visitor signs in with a password or Google / GitHub, their own IP address is allowed on the tunnel port for 1 hour, 12 hours, 24 hours or 7 days (your choice). Connections without a grant are silently dropped. You can see and revoke grants.

A Zorven-styled login page instead of the browser password popup: username and password, or continue with Google / GitHub. Every attempt is recorded for statistics (never passwords); the list and summary are available from the API for now.