rivet-dev/rivet

Rivet Actors are the primitive for stateful workloads. Built for AI agents, collaborative apps, and durable execution.

View on GitHub ↗Jump to charts ↓Open shareable report →

rivet-dev/rivet has 6k+ stars and 250+ forks on GitHub, is written in Rust, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 49 minutes ago
Added to GitGenius on September 24th, 2026
Created on June 16th, 2023
Open Issues & Pull Requests: 345 (+0)
GitHub issues: Enabled
Number of forks: 280
Total Stargazers: 6,312 (+0)
Total Subscribers: 19 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.7 hours
Mean response time: 60.4 days
90th percentile: 316.7 days
Tracked items: 149

Maintainer activity

6 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 92% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 8 hours, while "enhancement" waits about 4 months. 70% of issues opened in the past year have been closed, leaving a working backlog. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 25
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 67 days
Stale 30+ days: 11
Stale 90+ days: 2

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (29)
  • bug (23)
  • maintenance (8)
  • good first issue (6)
  • workflows (5)
  • documentation (3)
  • Medium priority (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Rivet is a runtime for building stateful workloads using actors as the primitive, designed for AI agents, collaborative applications, and durable execution.

Rivet addresses the challenge of managing long-lived, stateful services by providing actors—lightweight processes that maintain in-memory state with automatic persistence. Each actor can run indefinitely while idle, hibernating to zero cost when not in use. State lives co-located with compute for instant reads and writes, persisting to SQLite or a custom database. The platform includes built-in WebSockets for real-time communication, workflows with automatic retries, durable message queues, and scheduling capabilities like timers and cron jobs. Actors scale infinitely and deploy across a global edge network, allowing you to run one actor per agent, session, user, or tenant without managing infrastructure complexity.

Rivet suits teams building AI agents with persistent context and memory, real-time collaborative applications, multi-step workflows, or per-tenant systems where low-latency in-memory access matters. It works well for sandbox orchestration, chat systems, and any workload that benefits from long-lived state without the operational overhead of traditional infrastructure. The README compares actors favorably to Kubernetes pods and virtual machines on cold start time, memory overhead, and idle cost, and to Redis and Postgres on read latency for in-memory state access.

The project shows active development with regular updates to its documentation and changelog. The team maintains a public Discord community and social presence for user engagement. The codebase is written in Rust, indicating a focus on performance and reliability for the runtime layer.