Pinned Tweet
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
Discord: rivet.dev/discord
Rivet retweeted
In the next version of Rivet:
๐ป 25% less RAM on RivetKit (JS)
๐ป 33% less RAM on the control plane under SQLite load
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
Discord: rivet.dev/discord
Rivet retweeted
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....
GitHub: github.com/rivet-dev/rivet
Discord: rivet.dev/discord






