Meilisearch vs Rivet
Side-by-side trajectory, velocity, and editorial themes.
Meilisearch hardens auth and speeds synonyms as its new settings indexer nears completion
Meilisearch is on a fast weekly point-release cadence centered on engine performance and security. Its new settings indexer reached feature-complete in v1.47, synonym storage was reworked for up to 13x faster search on large synonym sets, and two authentication CVEs were patched across the 1.47 and 1.48 branches. Experimental work on a render-template route and multimodal fragments points at deeper embedder tooling underneath the search core.
The near-term arc is consolidation: finishing the settings-indexer migration, tightening authentication, and stabilizing the S3 snapshot and remote-federated-search paths. The experimental render-template and fragment routes suggest Meilisearch is building out its vector and multimodal search story so document templates and embedders can be tested and iterated before indexing.
Expect v1.50 to graduate some of the experimental render-template and embedder tooling toward stable, while security and settings-indexer hardening continue in the point releases.
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 Meilisearch →
See more alternatives to Rivet →