Svelte vs Rivet
Side-by-side trajectory, velocity, and editorial themes.
SvelteKit's remote functions mature as the toolchain quietly lines up SvelteKit 3
Svelte ships a monthly What's-new digest whose center of gravity is SvelteKit, not the compiler. Remote functions are the most active subsystem—forms, queries, and enhance callbacks have churned through repeated breaking changes as the API finds its final shape. The CLI (sv) and language tools are kept in lockstep so newly scaffolded projects reflect the latest syntax.
The clearest through-line is the road to SvelteKit 3: config is moving into vite.config.js, and experimental explicit environment variables preview the eventual replacement for the $env/* modules. Alongside that, remote functions are gaining realtime (query.live) and file-upload ergonomics while their rough edges get sanded down.
Expect continued SvelteKit 3 previews—likely a beta that makes the vite.config.js and explicit-env changes the default—plus further remote-function stabilization. This is grounded in the recurring 'preview of how Kit 3 will work' notes across the recent entries.
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.
See more alternatives to Svelte →
See more alternatives to Rivet →