Free
$0
No paid checkout
A bounded workspace for learning the local-to-public workflow.
- Up to 3 active tunnels
- 100 captured requests per day
- 5 replays per day
- 1 day of capture retention
- Up to 3 builder services
Plans and limits
Clear boundaries now. Verified paid terms next.
R3verb currently enforces three organization plans. Free is $0. Paid dollar amounts and billing units are intentionally withheld until the public catalog and configured checkout price are verified together.
Pro
Active projectsPaid plan
Terms confirmed before purchase
Higher limits for developers using R3verb in active projects.
- Up to 25 active tunnels
- 1,000 captured requests per day
- 50 replays per day
- 30 days of capture retention
- Up to 25 builder services
Enterprise
Custom
Defined in your order
A separately agreed plan for organizations with larger operating needs.
- Organization-specific operating limits
- 90 days of capture retention
- Deployment and support scope agreed in writing
- No public SSO, SLA, or compliance promise
- Sales-assisted onboarding
Enforced allowances
The same boundaries, in one comparison.
These values mirror the current control-plane plan configuration. Enterprise uses separately agreed scope for most operating limits.
| Resource | Free | Pro | Enterprise |
|---|---|---|---|
| Active tunnels | 3 | 25 | Order-specific |
| Domains | 1 | 50 | Order-specific |
| Captured requests / day | 100 | 1,000 | Order-specific |
| Replays / day | 5 | 50 | Order-specific |
| Capture retention | 1 day | 30 days | 90 days |
| Builder services | 3 | 25 | Order-specific |
| Builder deployments / day | 5 | 50 | Order-specific |
| AI analyses / day | 10 | 100 | Order-specific |
Reaching a finite limit stops the corresponding operation; this page does not advertise automatic overages. AI allowances apply only where AI is configured and the relevant workflow is available.
Practical answers
Know what you are buying—and what you are not.
The product mechanics and current commercial caveat in plain language.
What runs on my laptop?
Your application and its normal framework watcher run locally. R3verb starts or supervises the command you configure, then connects that running process to its development environment.
What does R3verb manage remotely?
The current development path provisions PostgreSQL and Redis when the imported application needs them. R3verb injects their connection details into the local process; other detected integrations remain external unless a supported workflow says otherwise.
Does the public URL stay online when my laptop disconnects?
No. A development URL forwards to the running local HTTP service. Stop the process or disconnect the laptop and that local-backed route cannot serve the app. Hosted versions use a separate promotion lifecycle.
Does R3verb upload code every time I save?
No. Your framework reloads itself when it has a watcher. For compiled or explicitly configured services, R3verb can rebuild and restart the local process. The tunnel forwards traffic; it is not a per-save deployment pipeline.
Can I run background workers?
Yes. A service declared with the worker role can use managed dependencies and a restart loop without receiving a public HTTP route. HTTP traffic capture does not claim to trace every job or downstream call.