← Back to home
Comparison · DevOps

Appwrite vs Supabase

A side-by-side editorial comparison of Appwrite and Supabase — release velocity, themes, recent moves, and the top alternatives to consider.

Appwrite vs Supabase: at a glance

FeatureAppwriteSupabase
SectorDevOpsInfra & APIs, DevOps
Velocity score6.30.0
Sparks · 30d10
Top themesprojects-api, infrastructure-as-code, self-hosted, clisecure-defaults, breaking-changes, row-level-security, postgrest
Last editorial update2h ago5h ago
WebsiteVisit →

What is Appwrite?

Appwrite is making project setup something you write down instead of click through.

Appwrite shipped a Projects API that exposes every project setting — auth methods, OAuth providers, SMTP, labels — through the Server SDKs, and made CLI column updates non-destructive so required, default, size, min/max, enum, and relationship onDelete changes apply in place instead of dropping data. On the self-hosted side, 1.9.6 repaired the upgrade problems reported in 1.9.5, which itself carried a Presences API, BigInt columns, a Rust function runtime, and Bun and Deno build runtimes. Dev key creation is paused ahead of a 1 September deprecation, and paused free projects now get deleted after 90 days.

Read the full Appwrite trajectory →

What is Supabase?

Supabase is closing its most-exploited default: tables stop being public unless you say so.

The last month is dominated by tightening defaults rather than adding surface. New tables in the public schema will no longer be auto-exposed to the Data and GraphQL APIs, pg_graphql stops being enabled by default, and the OAuth token endpoint is being corrected to return 200 per OAuth 2.1. Alongside that, custom OAuth/OIDC providers landed for Auth and an RLS Tester entered preview.

Read the full Supabase trajectory →

Appwrite vs Supabase: editorial side-by-side

A
Appwrite
DEVOPS
6.3

Appwrite is making project setup something you write down instead of click through.

◆ Current state

Appwrite shipped a Projects API that exposes every project setting — auth methods, OAuth providers, SMTP, labels — through the Server SDKs, and made CLI column updates non-destructive so required, default, size, min/max, enum, and relationship onDelete changes apply in place instead of dropping data. On the self-hosted side, 1.9.6 repaired the upgrade problems reported in 1.9.5, which itself carried a Presences API, BigInt columns, a Rust function runtime, and Bun and Deno build runtimes. Dev key creation is paused ahead of a 1 September deprecation, and paused free projects now get deleted after 90 days.

◆ Where it's heading

The direction is infrastructure-as-code applied to a backend platform: configuration in SDK calls, schema migrations that preserve data, and self-hosted releases that repair their own upgrade path. Read together with the dev key deprecation and the free-tier reclamation, Appwrite is also tightening the operational edges — the console becomes one interface onto a project rather than the only one.

◆ Prediction

The natural follow-on is declarative project definitions checked into a repository, since the Projects API plus non-destructive schema changes supply both halves. Expect the dev key deprecation to land with a documented replacement before September.

Supabase logo
Supabase
INFRA · APISDEVOPS
0.0

Supabase is closing its most-exploited default: tables stop being public unless you say so.

◆ Current state

The last month is dominated by tightening defaults rather than adding surface. New tables in the public schema will no longer be auto-exposed to the Data and GraphQL APIs, pg_graphql stops being enabled by default, and the OAuth token endpoint is being corrected to return 200 per OAuth 2.1. Alongside that, custom OAuth/OIDC providers landed for Auth and an RLS Tester entered preview.

◆ Where it's heading

Supabase is paying down the security cost of its own convenience. Auto-exposing every public-schema table made the product fast to start with and easy to misconfigure; the fix is explicit Postgres grants, staged over six months from new projects in April to all existing projects on October 30. The RLS Tester is the same theme from the other side — the auto-exposure default only worked if row-level security was correct, and until now there was no way to check.

◆ Prediction

Expect the remaining rollout dates to hold and more of the developer experience to be rebuilt around explicit grants, with the RLS Tester graduating from preview as it becomes the tool people need to verify the new model. The October cutover for existing projects is the moment where this stops being an announcement and starts breaking things.

Appwrite alternatives

Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Tap any card for the full editorial trajectory or compare directly with Appwrite.

See all Appwrite alternatives →

Supabase alternatives

Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Tap any card for the full editorial trajectory or compare directly with Supabase.

See all Supabase alternatives →

Recent activity from Appwrite and Supabase

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoAppwriteNon-destructive column updates and renames in the Appwrite CLI
  2. 8d agoAppwriteAnnouncing Appwrite 1.9.6 for self-hosted deployments
  3. 8d agoAppwriteAnnouncing the Projects API: Configure your project with Server SDKs
  4. 9d agoAppwritePausing the creation of new dev keys
  5. 1mo agoAppwriteAnnouncing Appwrite 1.9.5 for self-hosted deployments
  6. 1mo agoAppwritePaused free projects are deleted after 90 days
  7. 2mo agoSupabaseDeprecation Notice: Dropping Support for Node.js 20
  8. 2mo agoSupabaseDeveloper Update - May 2026
  9. 3mo agoSupabaseBreaking Change: OAuth token endpoint will return HTTP 200 instead of 201
  10. 3mo agoSupabaseBreaking Change: Tables not exposed to Data and GraphQL API automatically
  11. 3mo agoSupabaseFragment of the no-auto-expose announcement
  12. 3mo agoSupabaseFeature Preview: RLS Tester

Frequently asked questions

What is the difference between Appwrite and Supabase?

They serve adjacent needs but don't currently overlap on shipped themes. Appwrite is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Appwrite better than Supabase?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Appwrite is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.

What are the best alternatives to Appwrite?

Top Appwrite alternatives in DevOps are ranked by recent ship velocity. Browse the "Appwrite alternatives" section above for the current picks, or visit /alternatives/appwrite for the full list with editorial commentary on each.

What are the best alternatives to Supabase?

Top Supabase alternatives in DevOps are ranked by recent ship velocity. Browse the "Supabase alternatives" section above for the current picks, or visit /alternatives/supabase for the full list with editorial commentary on each.