Appwrite vs Tigris
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.
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 Appwrite →
See more alternatives to Tigris →