Rivet vs Prometheus
Side-by-side trajectory, velocity, and editorial themes.
Rivet pivots from actor backend to a coding-agent OS, and is building the ecosystem to match.
Rivet began as an actor and serverless backend platform — RivetKit, Rivet Actors, Rivet Compute — and has spent the last month reorienting around agentOS, a WebAssembly-based Linux environment for running coding agents without a heavy sandbox. The June and July releases show both threads running in parallel: native language SDKs (Rust, Effect) for Actors, and a fast-maturing agentOS that now has its own package registry.
The center of gravity is shifting from hosting stateful actors to being the runtime coding agents execute inside. agentOS went from a v0.2 sandbox alternative to shipping a package registry and a sub-millisecond package manager in under two weeks, a sign Rivet wants to own the developer surface around agent execution, not just the compute underneath it.
Expect agentOS to keep accreting ecosystem pieces — more registry content and tighter orchestration — while the Actors SDKs settle toward maintenance. A likely next move is deeper coupling between agentOS and Rivet Compute so agents run on Rivet's own cloud.
Prometheus ships 3.13 LTS while hardening the 3.5 line against a steady drip of CVEs
Prometheus is running two supported tracks at once: the long-lived 3.5 LTS, which now takes near-monthly security-only patches, and the new 3.13 LTS, which lands a large batch of PromQL, service-discovery, and TSDB work. The bulk of recent releases are security maintenance and incremental engine improvements rather than new user-facing surface.
The center of gravity is experimental PromQL (start-timestamp-aware rate/increase, smoothed/anchored rate over native histograms, new scalar and search functions) and native-histogram maturation across TSDB and scrape. Alongside that runs a disciplined security cadence — sanitize-html bumps, credential-forwarding fixes on redirects, snappy-decode limits — backported across both LTS lines.
Expect 3.13.x to stabilize out of RC and continue the native-histogram and start-timestamp buildout behind feature flags, with the 3.5 LTS line receiving security-only patches as new CVEs surface.
See more alternatives to Rivet →
See more alternatives to Prometheus →