immudb
immudb made itself speak Postgres — while its announced v2 rearchitecture sits unfinished.
A side-by-side editorial comparison of Sonic and Appwrite — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Sonic | Appwrite |
|---|---|---|
| Sector | DevOps | DevOps |
| Velocity score | 5.0 | 10.0 |
| Sparks · 30d | 0 | 3 |
| Top themes | search-index, rust, tokenizer, dependency-hygiene | mcp, backend-as-a-service, agent-native, cloud-pricing |
| Last editorial update | 2h ago | 8h ago |
| Website | Visit → | — |
Sonic is shipping tokenizer control and a dependency diet, two tags at a time.
Sonic is a lightweight Rust search index that now releases in pairs — a server tag (v1.7.x) and a core-crate tag (v0.1.x) covering the same underlying commits. The recent work splits between tokenizer behavior, where pattern matching became opt-in and special tokens stopped being split apart, and a dependency audit that pinned every crate, disabled default features across the board, and trimmed unused RocksDB functionality. Release cadence is tight, with several tags landing within days.
Appwrite turns Functions into MCP hosting while quietly putting a meter on Cloud storage.
Two arcs run in parallel. On the product side, Appwrite is making itself the place AI clients connect to: its own MCP server moved to a hosted endpoint with OAuth on July 31, and a Functions template now lets developers deploy their own MCP servers on Appwrite infrastructure. Alongside that, configuration keeps moving into code through the Projects API, non-destructive CLI column updates and renames, and project targeting without a linked directory. On the business side, Cloud economics are tightening step by step: dev-key creation paused, dormant free projects deleted after 90 days, and build and deployment storage billed from September 1.
Sonic is a lightweight Rust search index that now releases in pairs — a server tag (v1.7.x) and a core-crate tag (v0.1.x) covering the same underlying commits. The recent work splits between tokenizer behavior, where pattern matching became opt-in and special tokens stopped being split apart, and a dependency audit that pinned every crate, disabled default features across the board, and trimmed unused RocksDB functionality. Release cadence is tight, with several tags landing within days.
Two things are happening at once. The tokenizer changes are aimed at correctness for users indexing identifiers and structured strings — the recurring theme of treating more strings as IDs and performing implicit AND on ID queries suggests the index was mangling exactly the inputs developers reach for it with. The dependency work reads as supply-chain and binary-size discipline: pinning everything and disabling default features is what a project does when it wants a small, auditable, reproducible build. The core/server split into separate crates is what makes the paired tags necessary.
Expect the tokenizer work to continue toward configurable behavior rather than better defaults, given pattern matching was made opt-in and non-breaking in the same release. The paired v1.7.x/v0.1.x tagging will keep producing two changelog entries per actual release.
Two arcs run in parallel. On the product side, Appwrite is making itself the place AI clients connect to: its own MCP server moved to a hosted endpoint with OAuth on July 31, and a Functions template now lets developers deploy their own MCP servers on Appwrite infrastructure. Alongside that, configuration keeps moving into code through the Projects API, non-destructive CLI column updates and renames, and project targeting without a linked directory. On the business side, Cloud economics are tightening step by step: dev-key creation paused, dormant free projects deleted after 90 days, and build and deployment storage billed from September 1.
Appwrite is repositioning from a backend-as-a-service into an agent-facing platform where the unit of deployment is as likely to be a tool endpoint as a REST route. Every developer-experience release in this window reduces the setup tax on that path: no local MCP install, no API keys to distribute, no directory linking. The commercial moves run in the opposite direction, converting previously unmetered Cloud consumption into billed usage with dated deadlines. Self-hosted releases continue in their own lane, with 1.9.6 repairing the upgrade breakage 1.9.5 introduced.
Expect the MCP surface to keep expanding, most likely with authentication and scoping controls for user-deployed tool servers, and expect more previously free Cloud allowances to gain enforced limits ahead of the September 1 date. The dev-key deprecation on the same date suggests the two arcs are being sequenced together.
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Sonic or Appwrite.
immudb made itself speak Postgres — while its announced v2 rearchitecture sits unfinished.
Zalando's Postgres Operator finally shipped v2 — and had to reissue it within a day.
A graph database spending its releases on query-language parity and traversal speed.
Manticore tags a GitHub release per commit, so the real news is one entry in five.
PostgreSQL 19 support lands, and pgBackRest stops letting you run most commands as root.
Two patch lines, every release published twice, and no feature news since v24.0.0.
See all Sonic alternatives → · See all Appwrite alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Appwrite is currently shipping more aggressively (velocity 10.0 vs 5.0), with 3 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Appwrite is currently shipping more aggressively (velocity 10.0 vs 5.0), with 3 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Sonic alternatives in DevOps are ranked by recent ship velocity. Browse the "Sonic alternatives" section above for the current picks, or visit /alternatives/sonic-search for the full list with editorial commentary on each.
Top Appwrite alternatives in DevOps are ranked by recent ship velocity. Browse the "Appwrite alternatives" section above for the current picks, or visit /alternatives/appwrite for the full list with editorial commentary on each.