Skip to main content
Sign In

Give agents an operating system as a library.

Each agent gets files, processes, shell, and networking in one lightweight OS. One package, with WebAssembly isolation instead of a separate microVM fleet.

92×faster cold starts47×less memory254×cheaper to run

Bring any agent or framework.

Pi, Claude Code, Codex, and OpenCode on the same virtual operating system—with native Rivet coordination and integrations for Eve and Flue.

Tiny runtime.
Isolation built on WebAssembly.

Powered byWebAssemblyandV8 isolates.

The same technology poweringChromeandCloudflare Workers.

Linux-compatiblewith POSIX files, processes, and networking.

Cold starts

92× faster

4.8 ms p50

agentOS
4.8 ms p50

Sandbox
440 ms p50

Memory per instance

47× smaller

~22 MB per instance

agentOS
~22 MB

Sandbox
~1024 MB

Cost per execution-second

254× cheaper

$0.000000073/s

Metering 100,000 concurrent VMs

agentOS$0.09
Sandbox$22.20

Library, not extra infrastructure

Install agentOS from npm and run it inside the backend process you already operate.

WebAssembly + V8, not a microVM

V8 isolates run JavaScript while WebAssembly contains compiled tools inside the same compact runtime.

Direct function calls, not extra APIs

Connect agents to your application with ordinary JavaScript calls instead of another network service.

Scoped access, not exposed credentials

Bind trusted host functions without ever giving the agent your raw secrets.

One process, not a VM per agent

Many isolated agent operating systems share one compact runtime instead of duplicating a full microVM stack.

Runs anywhere, no nested virtualization

Deploy on standard Linux infrastructure without a hypervisor or nested virtualization.

Execution

Run Bash, Node.js, Python, and registry software inside the same isolated VM.

  • Native JavaScript performance

    Run Node.js on native V8 isolates with the full JIT, not JavaScript compiled to WASM.

  • Built-in type checks

    Type-check agent-generated code and return diagnostics so the agent can fix errors.

  • Bindings

    Expose typed backend functions without giving credentials to the VM.

  • Subprocesses

    Spawn, stream, signal, and manage child processes with Linux-like semantics.

  • Network requests & servers

    Make outbound requests or serve HTTP from inside the VM under explicit permissions.

Explore execution docs
The agent writes one program instead of a chain of tool calls.
Node.js runtime docs

Filesystem

Every agent gets its own persistent POSIX filesystem. Mount S3, Google Drive, host directories, or a full sandbox at a normal path, then use familiar files and shell tools everywhere.

Explore the filesystem
StorageFilesystem path
Host directory
/workspace
S3
/data
Google Drive
/documents

Mounted into one persistent POSIX filesystem.

Coordinate agents. Automate durable work.

agentOS owns the agent's computer: its files, processes, shell, and network. Connect agents and share live sessions here; use Workflows when multi-step work must wait, retry, and resume.

Write code
Review
Decision
ShipApproved
RetryRejected
Workflows records completed operations and the decisions needed to resume.
Workflows docs

Whatever the workload, there's a package for it.

Extend agentOS with agents, filesystems, browsers, and software from one registry.

Built for flexible agent workloads.

Persist agent state, expose backend functions, review tool calls, route models, and attach a full sandbox only when a workload needs one.

Durable agentsPersist sessions and transcripts so fault-tolerant agents can pause and resume across restarts.Sleeps when idleIdle VMs sleep to free resources, then wake automatically with durable state when work arrives.BindingsExpose typed JavaScript functions as CLI tools while credentials remain on the host.Human in the loopPause permission requests for review, then approve or reject them in your own UI.Sandbox mountingMount a full Linux sandbox only when native binaries or heavy compilation need one.BrowsersConnect agents to serverless browser providers like Browserbase without running a browser inside the VM.ObservabilitySurface structured logs, resource snapshots, and warnings before bounded limits are reached.Preview URLsExpose services running inside a VM through signed, time-limited URLs.Cron jobsSchedule commands or agent sessions while agents sleep between runs.Resource LimitsSet per-VM caps for processes, memory, files, sockets, and execution time.Client-server & React SDKsConnect backends and live agent interfaces with typed clients and first-party React hooks.Built on standardsACP and A2A at the agent boundary. WebAssembly and POSIX underneath.

Develop locally. Deploy when ready.

Deploy on Rivet Cloud, or self-host Rivet inside your own infrastructure.

Local

Install agentOS and run it locally while you build.

Open the quickstart

Rivet Cloud

Deploy agentOS on Rivet Cloud with managed infrastructure and persisted Actor data.

Open the dashboard

Self-Host

Run the open-source Rivet control plane as a Rust binary or container on your infrastructure.

Read self-hosting docs

Turn your backend into the agent platform.

Open source under Apache 2.0. One npm install away.

Read the Docs