Directus vs Weaviate
Side-by-side trajectory, velocity, and editorial themes.
Directus is on a steady weekly cadence with AI tooling deepening on every release.
Directus is shipping weekly point releases on the 11.17.x line, each carrying a mix of small UI features, AI-related additions, and dependency hygiene. The recent stretch added a /ai/object structured-generation endpoint, an asset cache-revalidation header (ASSETS_CACHE_REVALIDATE), background data imports with timeout and concurrency controls, a Tabs group interface that absorbs a previously-extension feature, and comparison-modal improvements (timezone-aware datetime, modified-only view). UI work in 11.17.0 also shrunk the app to 90% and converted px to rem — flagged as a potential breaking change for extensions with hardcoded pixel values.
Two parallel arcs: (1) AI Assistant continues to grow — image/PDF upload, multi-provider model refresh (Anthropic, Google, OpenAI), an Anthropic tool-search adapter for context efficiency, and now a structured-object endpoint for inline experiences; (2) the app shell is being modernized — rem-based sizing, native replacements for previously third-party UI primitives (reka, native Tabs), and migration of @directus/visual-editing into the monorepo. Bug-fix volume is high but consistent — typical of a project absorbing a wide community contribution stream.
Expect continued weekly 11.17.x cuts focused on the AI surface (more inline AI-aware components, more structured-output use cases) and the in-progress monorepo consolidation. The 90%-UI shrink will likely require an extensions-side migration cycle before a major version cut.
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 Directus →
See more alternatives to Weaviate →