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 guidesConfigure InstaTunnel with config files and environment variables for persistent settings.
Create a global config file at ~/.instatunnel.yaml:
💡 Tip: Config file is automatically loaded if present in your home directory.
Use a custom config file location with the --config flag:
InstaTunnel automatically reads environment variables that match config keys:
🔒 Security: Never commit API keys to version control. Use environment variables for sensitive data.
InstaTunnel follows this configuration priority (highest priority first):
--api-key your_keyAPI_KEY=your_key~/.instatunnel.yaml| Option | Flag | Env Variable | Description |
|---|---|---|---|
api_key | --api-key | API_KEY | Your InstaTunnel API key |
server_url | --server | SERVER_URL | InstaTunnel server URL |
🎯 Best Practice: Store your API key in the config file (~/.instatunnel.yaml) or environment variable for convenience. Use command-line flags for temporary overrides.
See plans, then jump into a guided start whenever you are ready.
For MCP endpoints on Pro/Business, use: instatunnel 8787 --mcp.