Pricing
Two plans: Community and Pro. Everything is self-hosted.
Feature comparison
| Feature | Community | Pro |
|---|---|---|
| User seats | 1 | 2 |
| Tunnel tier | Standard tunnel | High-speed tunnel |
| Devices | 1 | 2 |
| Self-hosted | Yes | Yes |
| Add seats | No | $19.9 /seat/year |
Frequently Asked Questions
Any privacy concerns?
No. Everything runs in your self-hosted environment, so your code and data stay on your own infrastructure.
Will Git worktrees interfere with my existing workflow?
No. Each task runs on its own branch in an isolated worktree directory. We only write changes inside that worktree, so your main working directory stays untouched; review the Diff and merge when you're ready.
What is a seat?
A seat equals one CoolVibe user that can log into your self-hosted server. Community supports 1 user. Pro includes 2 seats and you can add more (Dashboard → License).
How are tunnels counted?
Tunnels are counted per device (one tunnel per device). Both plans can create tunnels: Community focuses on reachability and does not provide a speed SLA; Pro includes the high-speed tier with higher bandwidth limits and more consistent throughput (it falls back after expiry).
How do I access it from my phone?
If your phone is not on the same LAN, enable public access via the tunnel: first authorize your CoolVibe account in the client, then create a public tunnel to get a public URL and open it in your phone browser. Community focuses on reachability; Pro provides higher bandwidth and more consistent speed.
How do I enable LAN access?
Run coolvibe expose (sets HOST=0.0.0.0 and restarts), or edit the config shown by coolvibe config to set HOST to 0.0.0.0 and restart the service. Then visit http://<server-ip>:<PORT> from another device on the same LAN.
Does the tunnel impact privacy?
No. The tunnel gateway is a relay (like a reverse proxy): it only reads the minimum request headers for routing/auth/rate-limiting, forwards payloads as a byte stream, and does not store your request content or touch your local repo/database files.
Do I have to use the tunnel?
No. You can access your self-hosted instance over LAN, or put it behind your own reverse proxy (Nginx/Caddy, etc.). The tunnel is only for getting a reachable domain when you don't have a public IP.