Sanity vs Appwrite
Side-by-side trajectory, velocity, and editorial themes.
Sanity is quietly wiring its CMS to be operated by agents as much as by humans.
Sanity is shipping on several fronts in parallel: a maturing MCP server and agent tooling, a Media Library growing real asset-management depth, and steady Studio and SDK ergonomics. The recent run is incremental but coherent — richer Media Library metadata and reference tracking, searchable reference fields, and a stream of MCP tool fixes. Nothing here reshapes the product; it is compounding polish on an already broad platform.
The clearest theme is agent-operability. The MCP server, a skills-install CLI command, agent-focused doc quickstarts, and copy-paste commands 'for humans and agents' all point at Sanity treating AI coding agents as a first-class way to drive the CMS. In parallel, Media Library is being built out toward a full DAM, and @sanity/presets is trimming schema boilerplate.
Expect the MCP and agent surface to keep expanding and Media Library to keep gaining DAM-grade features; the presets package suggests more ready-made schema building blocks ahead.
Appwrite hardens auth and broadens its framework and runtime surface as a Firebase alternative.
Appwrite is an open-source backend-as-a-service competing with Firebase and Supabase across auth, functions, storage, realtime, and hosted Sites. The recent cadence is broad and infrastructure-heavy: auth hardening (password strength, email policies), new realtime primitives (Presences), storage speedups, more build runtimes (Bun, Deno, Dart, Flutter), and a first-class React library. It also tightened free-tier economics by deleting long-paused free projects.
The platform is investing on two fronts at once — developer experience (React hooks, monorepo-aware Git build triggers, a Claude Code plugin) and backend breadth (presence, auth policies, faster uploads). The pattern is filling parity gaps with Firebase and Supabase while courting framework-native and agent-assisted workflows. Free-tier cleanup suggests attention to cloud cost discipline alongside feature growth.
Expect the React library to grow past auth into data and realtime hooks, and continued runtime and framework additions for Sites and Functions.
See more alternatives to Sanity →
See more alternatives to Appwrite →