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 guidesCreate memorable, consistent URLs for your tunnels with custom subdomains. Perfect for demos, development, and sharing.
Sign in with an InstaTunnel account to choose a subdomain, including on the Free plan. Anonymous tunnels use random names only. First-party and security-sensitive names such as api, login, and support cannot be claimed.
Instead of random URLs like abc123.instatunnel.my, get memorable URLs like myapp.instatunnel.my
When no subdomain is specified, InstaTunnel automatically generates a unique 6-character subdomain.
Use consistent naming patterns for organized development workflows.
Available names are first-come-first-served for signed-in users. Reserved names are unavailable even when not in use. Try a different name or use a random subdomain.
🎯 Best Practice: Use descriptive subdomains for demos and consistent subdomains for development environments. For quick testing, random subdomains work perfectly.
See plans, then jump into a guided start whenever you are ready.
For MCP endpoints on Pro/Business, use: instatunnel 8787 --mcp.