Rivet
Find the right starting point: quickstarts by Actor type, architecture, guides, deploying, and self-hosting.
Rivet runs agents, workflows, sandboxes, and generated apps as Rivet Actors: long-lived processes with durable state. One control plane schedules them, routes requests to them, and persists their state. Your code runs in workers you operate, on your own infrastructure or on Rivet Cloud.
Start Building
Pick the Actor type closest to what you are building. Each has its own quickstart; everything on this tab applies to all of them.
Actors
Durable state, actions, realtime events, queues, and scheduling.
Workflows
Multi-step operations that replay instead of starting over.
agentOS
A filesystem, shell, and network for code you did not write.
Dynamic Apps
A backend per user, deployed the moment it is generated.
Learn How It Works
Architecture
Namespaces, Actors, workers and pools, the gateway, and serverless vs. long-running workers.
Guides
Worked examples: an AI agent, a chat room, a multiplayer game, a per-tenant database.
Deploy
Rivet Cloud
Managed control plane. Deploy workers with the CLI or connect your own.
Bring Your Own Cloud
Rivet runs the control plane inside your cloud account.
Self-Host the Control Plane
Kubernetes, Docker Compose, or a VM, with your own database.
Deploy Workers
Per-platform guides: Vercel, Cloudflare, Kubernetes, Railway, Lambda, and more.
Connect and Operate
| I want to | Read |
|---|---|
| Point my backend and clients at Rivet | Connect |
| Let a browser or mobile app reach an Actor without a secret | Authentication, JWTs |
| Separate production from staging, or one customer from another | Namespaces |
| Run workers and route Actors to the right hardware | Workers & Pools |
| Ship new code without downtime | Versions & Upgrades |
| Place Actors near users or data | Regions & Multi-Region |
| Trace a request across Actors | OpenTelemetry |
| Understand why an Actor is pending or crashed | Actor Statuses, Troubleshooting |
| Inspect Actors and workers over HTTP | Management API |
| Run a game server or batch job as an Actor without RivetKit | Containers, Unity, Godot |
Tools
- CLI: deploy to Rivet Cloud and run local development for serverless platforms.
- Rivet MCP and the Rivet skill: connect your AI coding assistant to Rivet.
- Integrations: frameworks and libraries that run on Rivet Actors.
- Registry: every Actor type, first-party and community.