Directus vs Tigris
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.
Tigris turns its object store into agent infrastructure with Agent Kit, agent-shell, and durable global streams.
Tigris's release stream is a sustained product-marketing push around AI-agent storage primitives. Agent Kit landed as a TypeScript SDK exposing bucket forks, workspaces, checkpoints, and event coordination. agent-shell put a virtual bash environment with persistent storage in front of those primitives. Durable global streams via S2 Lite extended the object store into a streaming substrate suitable for per-agent reasoning traces. Around the launches, case studies and tutorials (Basic Memory, the $10 self-updating knowledge base) make the pitch concrete.
Tigris is staking a position that the right substrate for AI agents is not a database, vector store, or queue — it is a globally-distributed, fork-able object store. Each blog and SDK in this batch reinforces that thesis from a different angle: storage as message queue, fork-per-agent sandboxing, storage-protected agent containment, streams for reasoning traces. The competitive map being drawn includes R2, S3 Express, Backblaze, and the agent-runtime vendors (Modal, E2B), not other databases.
Expect a managed Vector or Lance-index surface on top of buckets to compete more directly with Turbopuffer and Pinecone, and a Python counterpart to the @tigrisdata/agent-shell TypeScript runtime to widen the agent-developer surface area.
See more alternatives to Directus →
See more alternatives to Tigris →