Rivet
Rivet 3.0 Preview runs as one stateless binary on WarpDrive, with S3 as its only dependency.
◆Recent moves
- 3d ago
Introducing Rivet 3.0 Preview
⚡ SPARKThe October 5 plan to drop NATS for S3 is now a usable preview, built on a new storage engine called WarpDrive. It caps a run of releases aimed at making Rivet cheaper to operate wherever it runs.
- 17d ago
Introducing agentOS 0.4 & Hosted VMs
agentOS 0.4 lets developers create durable Hosted VMs by ID and drive them from RivetKit or plain HTTP, with scoped JWTs for direct client access. It fills in the sandbox half of the harness-in-backend, tools-in-sandbox split that Pi 1.0 and Pi Durable rely on.
- 22d ago
Introducing Pi Durable for Rivet
Pi Durable runs inside a Rivet Actor and checkpoints every model request and tool call to SQLite, so runs finish through crashes and deploys. A week after Pi 1.0 hosting, it adds durability, the property that makes multi-hour agent runs practical on Rivet.
- 24d ago
Replacing Our Message Broker with... S3?
⚡ SPARKRivet 3.0 replaces NATS with S3, leaving object storage as its only infrastructure dependency. It completes the S3-tiered storage arc that began with July's zero-disk SQLite engine, and it makes the BYOC and self-host stories much lighter to run.
- 28d ago
Introducing Pi 1.0 for Rivet
Pi 1.0 runs on Rivet Actors at 0.82 MB of RAM per session, with the harness in the customer's backend and tools in a separate sandbox. It is a concrete demonstration of the harness-outside-the-sandbox pattern Rivet has been advocating since July.
- 1mo ago
Introducing JWT Authentication for Rivet Actors
Short-lived, actor-scoped JWTs let clients connect to actors directly, with Auth0, Clerk, Better Auth, or custom sessions as the issuer. It removes the need for a proxy layer and is one of the enterprise controls stacked on top of BYOC.