Rivet - Infrastructure for the Agentic Era - Rivet

Skip to main content

GitHubSign In

Introducing agentOS Execution API for JavaScript and Python<br>Infrastructure for<br>software that thinks.<br>Actors are the primitive for AI agents — and the realtime apps and workflows around them. They burst when traffic spikes, sleep when idle, and run anywhere: Rivet Cloud, your VPC, or fully air-gapped.<br>Start Buildingnpx skills add rivet-dev/skillsGive this to your coding agent

The Thinker<br>Auguste Rodin · modeled 1880

The Thinker<br>Auguste Rodin · modeled 1880

One actor per agent, per session, per user.

Rivet Actors give agents and realtime apps durable, stateful compute in your existing Node.js or Bun backend.<br>DocumentationDetails

In-memory state<br>Co-located with compute for instant reads and writes.

Runs indefinitely, sleeps when idle<br>Long-lived when active, hibernates when idle.

Scales to zero, bursts to thousands<br>Sleeps at near-zero cost when idle, fans out when traffic spikes.

Global edge network<br>Deploy close to your users without complexity.

WebSockets<br>Real-time bidirectional streaming built in.

Workflows, Queues, Scheduling<br>Multi-step operations, durable queues, and timers.

Give your agent an OS without a sandbox.

A lightweight library that gives agents a file system, networking, bash, Python, and Node.No containers, no VMs. Powered by Rivet Actors.Isolated with Wasm. Runs in your own backend.<br>Compared to running agents in a sandbox microVM:<br>92×faster cold starts47×less memory254×cheaper to run<br>Explore agentOS→

Built-In Observability

Debugging and monitoring for actors and agents, from local development to production at scale.

SQLite Viewer<br>Browse and query SQLite databases in real-time across actors and agent sessions

Workflow State<br>Inspect workflow progress, steps, and retries as they execute

Event Monitoring<br>Track every state change, action, and agent event as it happens in real-time

REPL<br>Debug actors and agent sessions by calling actions, subscribing to events, and interacting directly with your code

Works with your stack.<br>Standard Node.js, Bun, and Deno. Your frameworks, your tools. No custom runtime, no rewrite.

Frameworks

ReactNext.jsSvelteHonoExpressElysiatRPC

Runtimes

Node.jsBunDeno

Tools

VitestPinoAI SDKOpenAPIAsyncAPITypeDoc

Integrations

FlueVercel EveVercel Workflows

Start local. Scale to millions.

A library in development, a platform in production. Your backend keeps deploying wherever it already does — Rivet connects to it.

Just a Library

Install a package and run locally. No servers, no infrastructure. Actors run in your process during development.

npm install rivetkit

Get Started

Rivet Cloud

Fully managed Actors and agentOS on a global edge network. Connects to your existing cloud — Vercel, Railway, AWS, wherever you deploy.

Sign Up<br>Self-Host

Single Rust binary or Docker container. Works with Postgres, file system, or FoundationDB (enterprise). Full dashboard included.

docker run -p 6420:6420 rivetdev/engine

Self-Hosting Docs

Your backend deploys toRivet ComputeVercelCloudflareSupabaseRailwayKubernetesAWSGCPHetznerVMCustom Platform

Run it where your data lives.

A single binary you control. Deploy Rivet inside your VPC, your customer’s VPC, or fully air-gapped, with the compliance you already have.<br>Air-gapped and on-prem: no outbound calls, no telemetry leaving your boundary<br>Embed in your customers’ VPCs: they keep their data, you keep your product<br>FedRAMP, HIPAA, sovereign clouds: stay inside the boundary your controls already cover<br>Talk to an engineerRivet for Enterprise

Your perimeterYour backend<br>Actors run in your Node.js or Bun process

Rivet Engine<br>Single binary for orchestration and routing

Your storage<br>File system, Postgres, or FoundationDB

No outbound connections. No telemetry.

Infrastructure for<br>the agentic era.

Build with agents, build for agents, and run it where your data lives.<br>Start BuildingTalk to an Engineer