Rivet vs Kubernetes
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.
etcd 3.7 lands RangeStream and drops the last of v2store as Headlamp becomes the cluster's UI
The Kubernetes ecosystem is advancing on two fronts at once: the core datastore and the operator-facing UI. etcd 3.7.0 shipped GA with RangeStream, a full switch to v3store-only bootstrap, and a protobuf overhaul that cuts control-plane CPU. In parallel, Headlamp — the sanctioned successor to the now-archived Kubernetes Dashboard — is accumulating a plugin layer (Cluster API, Volcano, Knative) that pulls specialized workflows into one visual interface.
The center of gravity is efficiency in the control plane and consolidation in tooling. etcd's removal of legacy v2store and its feature-gate lifecycle signal a deliberate cleanup that Kubernetes 1.37 will draw on via the EtcdRangeStream gate. Around it, the project is standardizing operator experience on Headlamp rather than a proliferation of one-off dashboards, and formalizing how AI-assisted contributions enter the codebase. This is maintenance-era maturity, not new surface area.
Expect Kubernetes 1.37 to expose RangeStream behind its feature gate and more SIG projects to ship Headlamp plugins as the default visual entry point. The v3.8 line will likely complete the v2store removal by dropping v2 snapshot generation and the --snapshot-count flag.
See more alternatives to Rivet →
See more alternatives to Kubernetes →