AddToThese vs ngrok
Both give a local service a public URL through an outbound tunnel. The difference is what you pay for the features most developers end up needing.
The short version
If you already use ngrok, the workflow is the same: run one command, get an HTTPS URL. AddToThese includes reserved subdomains, custom domains and TCP tunnels in a single €4/month plan.
Feature by feature
| Feature | AddToThese Pro | ngrok |
|---|---|---|
| Public HTTPS URL for localhost | Yes | Yes |
| Reserved subdomains | 5 included | Depends on plan |
| Custom domains | 2 included | Depends on plan |
| TCP tunnels | Included | Depends on plan |
| Monthly transfer | 50 GB included | Depends on plan |
| Two-factor login | TOTP + recovery codes | Yes |
| Price | €4 / month or €40 / year | See ngrok.com/pricing |
ngrok changes its plans often, so check ngrok.com/pricing for its current limits before you decide.
Moving over
Replace the binary, log in once, and use the same port you used before:
addtothese http 3000 --subdomain myapp
Webhooks pointing at your old ngrok URL need updating once. After that the reserved name never changes.
When ngrok is the better fit
ngrok offers enterprise features AddToThese does not try to match, such as traffic policy rules, edge-level OAuth in front of your tunnel and a global edge network. If you need those, stay with ngrok. If you need a stable URL, a custom domain and TCP at a low price, AddToThese covers it.
Plans
Free
For trying things out and the odd webhook test.
- Random subdomains
- 1 GB transfer / month
- HTTP + TCP tunnels
- Tunnels last 8 hours
- Two-factor login included
Pro
For developers who need stable URLs every day.
- 5 reserved subdomains
- 2 custom domains
- 50 GB transfer / month
- HTTP + TCP tunnels
- No tunnel time limit
- Email support
Team
For heavier use: more names, domains and transfer.
- 25 reserved subdomains
- 10 custom domains
- 5 team seats
- 500 GB transfer / month
- HTTP + TCP tunnels
- No tunnel time limit
- Priority email support