Appwrite vs Supabase
Side-by-side trajectory, velocity, and editorial themes.
Appwrite broadens from Firebase alternative to full app platform, adding realtime primitives and agent tooling.
Appwrite is shipping across its whole surface at once: a new first-class Presences API for realtime status, runtime breadth (Dart, Flutter, Bun, Deno), Git deployment triggers with branch and path filters, faster parallel Storage uploads, Auth email policies, and an Appwrite plugin now in the official Claude marketplace. Database work is maturing too, with relationships hitting GA and BigInt columns added.
The platform is filling in primitives that push it past a backend-as-a-service toolkit toward an application platform. Presences targets multiplayer and live-collaboration apps; runtime and deployment controls court serious teams and monorepos; the Claude marketplace listing plants a flag in agent-native development. The throughline is reducing the reasons a team would reach outside Appwrite.
Expect continued realtime and collaboration primitives building on Presences, plus deeper agent/MCP tooling now that the plugin is in the official marketplace.
Supabase is reversing its biggest security default - public-schema tables no longer auto-exposed via PostgREST.
The headline shipping move is a deliberate change to Supabase's security posture: new projects can opt out of automatic Data API and GraphQL exposure for public-schema tables, with broader defaults flipping in May. Around it: an OAuth 2.1 compliance fix, an RLS Tester preview to make policy verification possible from the UI, and a steady drumbeat of platform improvements summarized in the monthly developer update.
Supabase is rebuilding the security defaults that made it fast to start with but easy to misconfigure. Combine the no-auto-expose change with the RLS Tester preview and the direction is clear: the platform is moving from convention-based exposure to explicit, testable access control. The OAuth compliance fix and developer updates suggest steady investment in standards conformance rather than new product surface this window.
Expect the no-auto-expose default to apply to existing projects (with a long opt-out runway), and the RLS Tester to graduate from preview into the dashboard as a first-class panel. Continued breaking-change drumbeat tied to OAuth/OIDC compliance is likely.
See more alternatives to Appwrite →
See more alternatives to Supabase →