immudb
immudb made itself speak Postgres — while its announced v2 rearchitecture sits unfinished.
Comparison · DevOps
Vitess vs Appwrite
A side-by-side editorial comparison of Vitess and Appwrite — release velocity, themes, recent moves, and the top alternatives to consider.
Vitess vs Appwrite: at a glance
| Feature | Vitess | Appwrite |
|---|---|---|
| Sector | DevOps | DevOps |
| Velocity score | 0.0 | 10.0 |
| Sparks · 30d | 0 | 3 |
| Top themes | sharded mysql, patch cadence, dual branch, go module tags | mcp, backend-as-a-service, agent-native, cloud-pricing |
| Last editorial update | 2h ago | 7h ago |
| Website | Visit → | — |
What is Vitess?
Two patch lines, every release published twice, and no feature news since v24.0.0.
The recent window is maintenance on two supported branches: v24.0.2 (34 merged pull requests) and v23.0.5 (35) in late June, preceded by v24.0.1 and v23.0.4 in May. None of these releases describe their contents — each body is a pull-request count and a contributor list, with the actual changelog behind a link. Every release also appears a second time as a `v0.x.y` Go-module tag carrying only a sign-off line.
What is Appwrite?
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.
Vitess vs Appwrite: editorial side-by-side
Vitess
0.0DEVOPS
Two patch lines, every release published twice, and no feature news since v24.0.0.
◆ Current state
The recent window is maintenance on two supported branches: v24.0.2 (34 merged pull requests) and v23.0.5 (35) in late June, preceded by v24.0.1 and v23.0.4 in May. None of these releases describe their contents — each body is a pull-request count and a contributor list, with the actual changelog behind a link. Every release also appears a second time as a `v0.x.y` Go-module tag carrying only a sign-off line.
◆ Where it's heading
Feature work is concentrated in the majors, not the patches. v24.0.0 at the end of April was the substantive release: window function pushdown for sharded keyspaces, view routing rules, tablet targeting through USE statements, VTGate binlog streaming and structured logging, with external decompressors no longer read from the backup manifest by default. Since then the branches have been in pure upkeep.
◆ Prediction
On the pattern here — a major in April followed by monthly patches on both supported branches — the next thing to expect is continued v23.0.z and v24.0.z patches rather than new capability. The bodies give no indication of what a v25 would contain.
Appwrite
10.0DEVOPS
Appwrite turns Functions into MCP hosting while quietly putting a meter on Cloud storage.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Vitess and Appwrite
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 Vitess or Appwrite.
Sonic
Sonic is shipping tokenizer control and a dependency diet, two tags at a time.
Postgres Operator
Zalando's Postgres Operator finally shipped v2 — and had to reissue it within a day.
NebulaGraph
A graph database spending its releases on query-language parity and traversal speed.
Manticore Search
Manticore tags a GitHub release per commit, so the real news is one entry in five.
pgBackRest
PostgreSQL 19 support lands, and pgBackRest stops letting you run most commands as root.
See all Vitess alternatives → · See all Appwrite alternatives →
Recent activity from Vitess and Appwrite
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoAppwriteDeploy your own MCP server with the new Functions template ⚡
- 4d agoAppwritePricing update: storage costs for builds and deployments will be enforced ⚡
- 4d agoAppwriteEasier project discovery and targeting in the Appwrite CLI
- 7d agoAppwriteThe Appwrite MCP server is now remote ⚡
- 8d agoAppwriteNon-destructive column updates and renames in the Appwrite CLI
- 15d agoAppwriteAnnouncing Appwrite 1.9.6 for self-hosted deployments
- 1mo agoVitessVitess v24.0.2 patch release (34 pull requests)
- 1mo agoVitessGo-module tag for the v24.0.2 release
- 1mo agoVitessVitess v23.0.5 patch release (35 pull requests)
- 1mo agoVitessGo-module tag for the v23.0.5 release
- 3mo agoVitessVitess v24.0.1 patch release (6 pull requests)
- 3mo agoVitessGo-module tag for the v24.0.1 release
Frequently asked questions
What is the difference between Vitess and Appwrite?
They serve adjacent needs but don't currently overlap on shipped themes. Appwrite is currently shipping more aggressively (velocity 10.0 vs 0.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.
Is Vitess better than Appwrite?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Appwrite is currently shipping more aggressively (velocity 10.0 vs 0.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.
What are the best alternatives to Vitess?
Top Vitess alternatives in DevOps are ranked by recent ship velocity. Browse the "Vitess alternatives" section above for the current picks, or visit /alternatives/vitess for the full list with editorial commentary on each.
What are the best alternatives to Appwrite?
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.