Appwrite vs Weaviate
Side-by-side trajectory, velocity, and editorial themes.
Appwrite ships platform-grade upgrades while opening direct lanes to agentic coding tools.
Appwrite is in heavy platform-maturation mode. The most recent month brought database relationships graduating to GA with a 12-18x speed-up, BigInt column support, persistent-WebSocket Realtime, programmatic environment-variable management, Rust 1.83 as a first-class function runtime, and Bun/Deno added as Sites build runtimes. Alongside the runtime work, two threads expand the platform's reach: a new Appwrite plugin for Codex with bundled MCP server and agent skills, and CLI improvements (multi-file config, deployment retention) aimed at infra teams running Appwrite at real scale.
Appwrite is doing the work to move from 'BaaS for hobbyists' into a credible Firebase and Supabase competitor for production teams. Two strategic vectors are visible: backend primitives are catching up (relationships GA, BigInt, Realtime overhaul, Rust runtime), and agentic developer tools (Codex plugin, docs MCP) are being treated as a first-class distribution surface rather than an afterthought.
Expect more agent-tooling investment — likely first-class plugins for Cursor or Claude Code, plus deeper MCP coverage of project resources — and continued runtime breadth, probably an edge-functions story to catch up to Cloudflare and Vercel.
Weaviate is rebuilding around agent memory and MCP, not just vector storage.
Weaviate's recent feed is anchored by two strategic releases: the 1.37 release with a built-in MCP Server, Diversity Search, and Query Profiling, and Engram — a managed memory service for agents. Surrounding work makes the AI-native database real on more clouds (Shared Cloud GA on AWS US-East and Europe) and surfaces (C# managed client, hybrid-search tokenization improvements). Engineering blogs lean into RAG quality and multimodal embeddings.
The product is rotating from 'vector database' positioning toward 'memory and retrieval substrate for AI agents.' The combination of MCP server in core, Engram as a managed offering, and dogfooding inside Claude Code suggests agent memory is the next category Weaviate intends to own — distinct from raw vector storage, where Pinecone and Pgvector continue to crowd the market.
Expect Engram to expand integrations beyond Claude Code (Cursor, Cline, custom agent frameworks) and a clearer pricing surface for memory-as-a-service. The MCP server in 1.37 should evolve from preview to GA with curated tool catalogs.
See more alternatives to Appwrite →
See more alternatives to Weaviate →