Guides

Log users in on your backend, mint a JWT scoped to each user's Rivet Actor, connect from the browser with it, and authorize actions inside the Actor.

Why actors eliminate complexity instead of managing it, and how merging state and compute removes the biggest source of latency in modern applications.

Give each user their own agent that they sign in to with their phone number and talk to by text message.

Run an agent whose conversation, in-flight tool calls, and plan survive crashes, deploys, and restarts.

Split a large task across an orchestrator agent and specialist agents that work in parallel.

Let users connect their ChatGPT plan so your agents run on it, with no OpenAI API key.

Run Claude Code in a cloud sandbox from your app, one session per Rivet Actor, and stream its output as it works.

Run the OpenAI Codex CLI in a cloud sandbox from your app, one session per Rivet Actor, and stream its output as it works.

Run OpenCode in a cloud sandbox from your app, one session per Rivet Actor, and stream its output as it works.

Run the Amp CLI in a cloud sandbox from your app, one session per Rivet Actor, and stream its output as it works.

Pause a workflow or an agent's tool call until a person approves or rejects it, even if the answer takes days.

Chain LLM calls and tool calls into one job that picks up at the failed step after a crash or a rate-limit error.

Accept webhooks from Stripe, GitHub, or Shopify, process each event once, and keep events for the same customer in order.

Run a daily report on a cron schedule inside a Rivet Actor, then add one-shot and fixed-interval jobs that survive sleep, restarts, and deploys.

Send your app's events to customer endpoints in order, retry failed deliveries, and turn off endpoints that keep failing.

Build a realtime chat room backend with Rivet Actors: one actor per room, SQLite-backed message history, and WebSocket broadcast to every connected client.

Build a collaborative text editor such as Google Docs or Notion with Yjs, where one Actor per document relays edits and presence and saves the document.

Build a collaborative text editor with operational transformation, where one Actor per document orders every edit and keeps the operation log.

Build live cursors and presence for a shared canvas, where one room Actor tracks who is connected and broadcasts every cursor move.

Deploy each app that your app builder generates as its own live app, with its own URL, backend, and data.

Give every tenant its own SQLite database by running one Rivet Actor per tenant, with tables and migrations scoped to that tenant.

Build a battle royale game like Fortnite, Apex Legends, or PUBG, where players fill a lobby and fight in a shrinking zone until one is left.

Build an IO game like Agar.io or Slither.io, where players drop into an open lobby at any time and the server moves everyone.

Build an arena game such as a team deathmatch, a free-for-all, or a Rocket League style match, where players queue for a mode and play a fixed-size match.

Build a turn-based game such as correspondence chess, where a match Actor validates every move and keeps the board between turns.

Build a Minecraft-style open world that is split into chunks, with one Rivet Actor per chunk and players walking between them.

Build a party game with private lobbies, where a host creates a room, friends join with a party code, and the host starts the game.

Build a ranked queue that pairs players by rating, runs each duel in its own match Actor, and updates ratings and a leaderboard when it ends.

Build an idle game like Cookie Clicker, where each player's world Actor keeps producing resources while they are offline and a shared leaderboard ranks everyone.

Build a 2D multiplayer physics game where a Rivet Actor runs Rapier on the server and streams every body's position to the players.

Build a 3D multiplayer physics game where a Rivet Actor runs Rapier on the server and players render the world with three.js.