Introducing Pi 1.0 for Rivet
Running agents inside the sandbox is simple in theory
But in production, the sandbox's blast radius becomes your agent's blast radius:
π₯ Sandbox OOMs β agent dies
π Credentials β need a proxy
π€ Sandbox asleep β no crons
π Update β redeploy every VM
Now with Rivet, you can run the vanilla Pi harness in your backend, separated from the sandbox
The sandbox can crash, sleep, or fill its disk. Your agent keeps running
Built for background & multiplayer agents
Introducing agentOS 0.4 & Hosted VMs
WebAssembly Linux sandboxes, now as a library or a managed HTTP API
β‘ ~5 ms boot & ~22 MB RAM
πΎ Durable, sleeps when idle
π₯ Multiplayer, crons, workflows, & JWT
π Many many bux fixes
Rivet now supports Pi Durable on Actors
πΉοΈ Multiplayer streaming
πͺΆ Lightweight β ~1.3 MB per agent, starts in ms
πΎ Durable β survives crashes, exactly-once input
π¦ Harness outside the sandbox
π₯§ Vanilla Pi
π± Schedules, JWT, sandboxes & more
S3 is the only dependency in Rivet 3.0 (coming soon)
It's architected for easy self-hosting and embedding in your own apps
But that also meant getting rid of NATS.... https://t.co/l7334blnrR
Introducing Pi 1.0 for Rivet
Running agents inside the sandbox is simple in theory
But in production, the sandbox's blast radius becomes your agent's blast radius:
π₯ Sandbox OOMs β agent dies
π Credentials β need a proxy
π€ Sandbox asleep β no crons
π Update β redeploy every VM
Now with Rivet, you can run the vanilla Pi harness in your backend, separated from the sandbox
The sandbox can crash, sleep, or fill its disk. Your agent keeps running
Built for background & multiplayer agents