About
Rivet builds open-source infrastructure for AI agents, realtime applications, collaborative software, and durable workflows. Its core Actors provide durable, stateful compute that can scale, sleep when idle, and run through Rivet Cloud, customer VPCs, on-premises, or air-gapped environments—giving developers and enterprises more deployment and data-control flexibility than conventional serverless platforms.
Market
Rivet competes in stateful serverless and AI-agent infrastructure, serving applications that need long-lived execution, persistent state, realtime communication, and durable workflows. Its differentiation is an actor-per-entity model with in-memory state, hibernation, realtime behavior, global deployment, and support for local, cloud, BYOC, or self-hosted operation. Compared with workflow-centric platforms such as Temporal and Inngest or stateful serverless offerings such as Cloudflare Durable Objects and PartyKit, Rivet emphasizes a developer-friendly library that connects to existing Node.js, Bun, and Deno applications without requiring a custom runtime.
Rivet targets software teams—from startups prototyping AI products to enterprise engineering organizations—that are building AI agents, realtime collaborative applications, workflows, chat, or other stateful services. The primary buyers and users are backend, platform, and AI application developers who want durable, low-latency compute without adopting a custom runtime or managing a separate infrastructure stack.
At a Glance
Problem
Modern AI agents, collaborative applications, and other real-time workloads are difficult to run on conventional request-oriented backends because developers must separately assemble persistent state, process lifecycle management, WebSockets, queues, timers, retries, and observability. Rivet targets this infrastructure gap with a stateful runtime in which each agent, session, user, document, or tenant can have a durable process. Its strongest use case is an AI agent that needs persistent context and memory, can remain active across interactions, and can schedule tool calls reliably.
The economic pain is that these workloads are often bursty but need to feel continuously available. Rivet addresses that by letting workloads sleep when idle and scale to zero, while claiming approximately 6 ms cold starts, 22 MB of RAM, and infrastructure costs substantially below full sandbox-based execution. The same model also applies to collaborative documents, chat rooms, per-tenant applications, and multi-step workflows that must survive failures or span long periods.
Product / Service
Rivet provides Actors, a primitive for stateful workloads, together with agentOS, an open-source operating system for agents. Actors colocate in-memory state with compute, support long-lived execution and hibernation, and include real-time WebSockets, workflows, queues, scheduling, and observability. Each AI agent can run as its own actor with persistent context, memory, and scheduled tool calls. agentOS adds an agent runtime that can be embedded in an existing backend, with controlled access to tools and files and a security model based on WebAssembly and V8 isolates.
The delivery model is deliberately flexible. Developers can use RivetKit as a library and run locally in-process, connect to fully managed Rivet Cloud on a global edge network, deploy through a bring-your-own-cloud model, or self-host the Apache 2.0 software in a VPC, on-premises environment, or air-gapped network. This gives Rivet a usage-based cloud business, an enterprise deployment path, and a portability proposition for customers that want to avoid infrastructure lock-in.
Market
Rivet competes in the emerging infrastructure market for AI agents, stateful serverless applications, real-time collaborative software, and durable execution. The clearest named comparison in the available evidence is Cloudflare Durable Objects: Rivet has been described as open-source actor infrastructure similar to that product. It also sits adjacent to AI-agent cloud and sandbox providers such as E2B, although Rivet's differentiation is the combination of durable state, long-lived actors, workflow primitives, and self-hosting rather than only isolated code execution.
Rivet appears commercially launched rather than merely pre-revenue: its offering includes free and paid cloud plans, usage-based compute and storage, and enterprise editions, while the open-source repositories provide visible developer traction. The main Actors repository reports 5,746 stars and agentOS reports 4,265 stars; Rivet also states that it is backed by Y Combinator and a16z Speedrun. A 2024 Show HN discussion claims Rivet already served millions of monthly active users in production, but that is a secondary, self-reported data point, and the available evidence does not provide audited revenue, customer counts, or a confirmed financing total.
Founders & Leadership
Funding History
Y Combinator
Recent News
Rivet described a SQLite storage engine for Rivet Actors that uses S3-compatible object storage for cold data, point-in-time recovery, and high-performance commits. The design supports large numbers of isolated databases without relying on local disks.
Rivet published agentOS as a library for running agents in an existing backend without sandboxes, virtual machines, or SaaS dependencies. The project is powered by WebAssembly and V8 isolates.
Rivet announced an agentOS Execution API for JavaScript and Python. The broader agentOS positioning connects to existing cloud deployments and backends rather than requiring a separate hosting environment.
Rivet's changelog listed Flue support for agentOS, indicating an integration that extends agentOS compatibility to Flue.
Rivet's changelog listed support for agentOS in Vercel's Eve, indicating an integration between the two products.
A Hacker News discussion covered Rivet's release of SQLite storage for Actors under Apache 2.0. The approach gives each Actor its own isolated SQLite database and is intended to support very large numbers of independent databases.
Rivet reported a Swift SDK for native iOS/macOS development, Vercel deployment examples, a GitHub Action for publishing skills, and the launch of the Sandbox Agent SDK. The update also mentioned Claude human-in-the-loop improvements, PostHog analytics integration, Inspector debugging, and a universal agent schema.
Rivet introduced the Sandbox Agent SDK, designed to work with Rivet Actors. The associated project provides a server inside a sandbox so applications can remotely control coding agents including Claude Code, Codex, OpenCode, Cursor, Amp, and Pi.
Rivet v2.0 reworked the platform around Rivet Actors and made it easier to build stateful workloads on Node.js or Bun. The release added bring-your-own-database support, multi-region deployment, broad cloud and self-hosting flexibility, and Apache 2.0 open-source licensing.
Active Roles
1Business Model
Rivet monetizes managed Rivet Cloud through free, subscription-based Hobby plans starting at $20 per month and Team plans starting at $200 per month, plus metered usage charges. It also sells a custom-priced Enterprise Edition with closed-source production, compliance, on-premises, VPC, and air-gapped deployment features, while the core platform remains open source and self-hostable.