Tubu vs ngrok
Compare Tubu and ngrok for local HTTPS tunnels, reusable hostnames, access controls, and traffic inspection.
Compare local tunnel features
| Feature | Tubu | ngrok |
|---|---|---|
| Setup | Run tubu-cli with a local target, hostname, and publisher API key. | Run ngrok http with a local port after configuring your agent token. |
| Hostnames | Choose an available third-level tubu.dev hostname. Reserve a fourth-level hostname on an eligible paid plan. | Use the assigned development domain or configure another domain subject to plan limits. |
| Access controls | Require a shared secret or enforce access in your application. | Use Traffic Policy actions such as OAuth or webhook verification, subject to plan limits. |
| Traffic inspection | Inspect requests in your local application logs. | Use Traffic Inspector in the ngrok dashboard. |
See ngrok HTTP endpoint documentation and ngrok pricing and limits.
Choose a tunnel for your workflow
Tubu fits a local service that already handles authentication and logs its own requests. Consider ngrok if you need dashboard inspection or traffic policies. If you already have a tunnel, follow the migration steps.