Frequently asked questions

The practical boundaries of building with R3verb.

What runs locally, what R3verb manages, when a public URL works, what replay does, and how hosted and AI-assisted paths differ.

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.

What projects can the CLI start?

R3verb has conventions for Node.js, Go, Python, Rust, and Java. Explicit commands, ports, build steps, and worker roles in r3v.yaml cover projects that do not fit those defaults.

Is replay safe for requests with side effects?

Replay sends another request. Review the destination, method, headers, and body before running it, especially for writes, payments, notifications, or other non-idempotent operations.

How is AI used?

AI-assisted generation, analysis, and mutation are conditional features. They require the configured model-router integration; the core tunnel, traffic, and non-AI management paths remain available without it.

Why is there no public Pro price yet?

The previous pages showed conflicting amounts and billing units. We are keeping paid checkout terms off the public page until the amount shown here, the configured Stripe price, and enforced entitlements can be verified together.

Ready to try the core loop?

Open the quickstart