Release cadence
CLI and docs release notes are updated continuously, with version-specific compatibility notes.
View release notesAnswer-first summary
Follow this order: Install CLI, authenticate, run first tunnel, then move to MCP/webhooks/referrals based on your use case. Use CLI Flags and Troubleshooting for day-to-day operations.
Quick command
instatunnel auth login -e you@example.com && instatunnel 3000 --subdomain docs-demoCommon failures and quick fixes
Use these references when evaluating compatibility, reliability, and security posture.
CLI and docs release notes are updated continuously, with version-specific compatibility notes.
View release notesReview policy enforcement, auth layers, and operational safeguards in the security whitepaper.
Open security whitepaperTroubleshooting guides cover common failures, recovery steps, and CLI compatibility baselines.
Read troubleshooting guidesInstaTunnel supports two levels of authentication: creating an account for enhanced features, and securing your tunnels with password protection or basic auth.
InstaTunnel works without signup for quick testing. Use CLI 1.1.24 or newer; anonymous tunnels get a random subdomain, and the CLI handles the private connection token automatically. Do not share that token. Anonymous use is limited to 2 active tunnels and 6 new tunnels per 24 hours per network, and is monitored for abuse; tunnels used for phishing are suspended automatically. Browser visitors see a one-time warning page; automated tests can send the X-InstaTunnel-Skip-Warning header to skip it. Sign in to choose a named subdomain and for higher limits.
Password protection is available on Pro and Business. Visitors need to enter the password before accessing your tunnel.
Browser visitors see a password form. API and webhook clients can send the password directly:
X-InstaTunnel-Password: mypassword123Webhook providers must support sending this header. If they cannot, use an unprotected endpoint and verify the provider's webhook signature in your app.
HTTP Basic Authentication is available on Pro and Business. Browsers display their native login prompt, while API clients can use credentials such as curl -u admin:secret123 https://abc123.instatunnel.my.
🔒 Security: Never hardcode passwords in scripts or commit them to version control. Always use environment variables.
| Feature | Anonymous | With Account | Password/Auth |
|---|---|---|---|
| Setup Required | None | Email registration | Set --password or --auth |
| Session Duration | 24 hours | 24 hours (Free) / Unlimited (Pro) | Same as account level |
| Custom Subdomains | ❌ | ✅ | Same as account level |
| Visitor Warning Page | Shown once per browser | None | Same as account level |
| Tunnel Limits | 2 active, 6 per 24 hours (per network) | Per plan | Same as account level |
| Tunnel Security | Public access | Public access | Protected access |
| Best For | Quick testing | Development | Demos, staging |
💡 Recommended: Start with an updated CLI and a random anonymous tunnel for quick testing. Sign in for a named subdomain; Pro or Business is required for password protection and Basic Auth.
See plans, then jump into a guided start whenever you are ready.
For MCP endpoints on Pro/Business, use: instatunnel 8787 --mcp.