prevu.cloud
Preview environments for coding-agent work.
Prevu gives external coding agents a real VM-backed environment to run work-in-progress changes, expose a live preview, and let humans review the result before production.
The gap
Coding agents can change code, run tests, and explain what happened. But when the work needs to be reviewed, teams still fall back to local servers, screenshots, fragile staging boxes, or production-adjacent deploys. A pull request shows text. Review still needs behavior.
The workflow
- 1.
Agent changes the project
Claude Code, Codex, Cursor, OpenCode, or another agent works in your repo and prepares a runnable change.
- 2.
Prevu runs it in staging
The agent connects to a reusable Linux environment, starts the app with the project’s own commands, and exposes the right port.
- 3.
Humans review the URL
Open the HTTPS URL from any device, share it with a teammate, and ask the agent to iterate in the same environment.
A real review surface
The environment page keeps the useful state in one place: connection context, running services, logs, ports, and the URLs humans can actually open.
- Not just a diff. Review the running feature, not only the code that produced it.
- Not production hosting. Use Prevu before production, while the work is still messy and reviewable.
- Not deploy inference. The agent owns how the project runs. Prevu owns the environment, bindings, and review surface.
Built for agents
- Stable surfaces. MCP, CLI, REST API, SSH, and the dashboard expose the same environment operations.
- Agent context block. Every environment gives agents the id, status, ports, SSH command, and workspace path without re-explaining state.
- No deploy inference. Prevu does not guess your framework or runtime. Your agent runs the project; Prevu gives it a place to run.
- Private by default. URLs are created explicitly when the agent or human exposes a port.
Developer resources
Agents can discover Prevu through plain-text docs, OpenAPI, MCP metadata, and well-known endpoints.
FAQ
Is this a Vercel or Railway replacement?
No. Prevu is for reviewing work before production. Use your production platform when the work is ready to ship.
Does Prevu run the coding agent?
No. Your external agent connects to Prevu and operates the project there. Prevu provides the staging environment and review URL.
Why not just use CI?
CI validates changes. Prevu gives humans and agents a running surface to inspect, click, debug, and iterate on before production.
Give your agent a place to show its work.
Create a staging environment, expose a URL, and review the running result before production.