Compare / Best of / Backends, databases and auth

Best backends for AI-built apps

Matt Turley, Continuum. Updated 2026-11-05.

We sell Continuum Supabase Security Review, so we say where the other options fit better. Links to other companies go to their own sites and carry no affiliate codes.

The short answer

Best backends for AI-built apps

No single backend is best for everyone. Appwrite suits teams wanting an open-source backend with a hosted option. Convex suits developers who want a reactive backend where queries update live. Firebase suits teams already building on Google Cloud who accept usage-based billing. Neon suits developers who want plain Postgres with scale-to-zero and branching-style workflows and usage-based billing. One more is covered below. The list is alphabetical and is not a ranking.

How we picked and ordered these

This covers the databases, backend platforms and sign-in services that AI app builders wire up. We only feature a tool when a page owned by the vendor backs our description of it.

We do not rank them. Each entry says what the sources report, where it falls short, and who it suits, so you can match one to your own situation. Where a competitor of ours is the better fit, we say so.

We read each source on 2026-11-05. Prices and limits change often, so confirm on the vendor's own page before you buy. A figure marked "one source only" was not matched by a second publisher.

At a glance

At a glance. Alphabetical order, not a ranking. Prices are as reported in the cited sources.
At a glance. Alphabetical order, not a ranking. Prices are as reported in the cited sources.
ToolWhat it isConfirmed priceSuits
AppwriteOpen-source backend platformFree $0 [1]; Pro $25 per month [2]Teams wanting an open-source backend with a hosted option
ConvexReactive backend and databaseStarter Pay for usage [3]; Professional $25 per developer per month [3]Developers who want a reactive backend where queries update live
FirebaseGoogle backend platform with NoSQL databasesSpark $0 [4]; Blaze Pay as you go [4]Teams already building on Google Cloud who accept usage-based billing
NeonServerless PostgresFree $0 [5]; Launch $0.106 per CU-hour [5]Developers who want plain Postgres with scale-to-zero and branching-style workflows and usage-based billing
SupabasePostgres backend platform with auth, storage and auto-generated APIPro $25 per month [6]Teams that want a Postgres database queried directly from client code and are willing to write and review RLS policies
Continuum Supabase Security Review (ours)Human Supabase security reviewSupabase Security Review Quoted on the page [7]A team running on Supabase that wants a person to read its policies and keys before launch

The backends, one by one

Appwrite

Appwrite offers a hosted backend with databases, auth, storage and functions on Free and Pro plans.[2]

What the sources say:

  • Pro adds organization roles, email support and daily backups kept for 7 days.[2]

Limits and things to check:

  • Appwrite's docs state the Free plan allows one organization and 2 projects.[1]
  • A paid Appwrite Start plan sits between Free and Pro and is live only in India, per Appwrite's blog.[8]

Pricing as reported for Appwrite:

  • Free: $0 [1]
  • Pro: $25 per month [2]

Plan limits are longer than fit here and some sources disagree on them, so read the limits on the vendor pricing page.

Suits teams wanting an open-source backend with a hosted option. That is our reading of the facts above, not something a source says.

Convex

Convex is a backend platform with a built-in database and server functions, priced per developer with usage allowances.[3]

Limits and things to check:

  • The plans page lists Professional at $25 per developer per month.[3]
  • Convex limits docs state limits are applied per team unless stated otherwise.[9]
  • Starter developer allowance is inconsistent across sources (limits doc shows 1 to 6).[9]

Pricing as reported for Convex:

  • Starter: Pay for usage (1,000,000 function calls per month included; overage $2.2 per 1,000,000; 0.5 GB database storage per search summary) [3]
  • Professional: $25 per developer per month [3]

Plan limits are longer than fit here and some sources disagree on them, so read the limits on the vendor pricing page.

Suits developers who want a reactive backend where queries update live. That is our reading of the facts above, not something a source says.

Firebase

Firebase is Google's app backend platform with a no-cost Spark plan and a pay-as-you-go Blaze plan.[4]

What the sources say:

  • Firebase offers two pricing plans: the no-cost Spark plan and the pay-as-you-go Blaze plan.[4]

Limits and things to check:

  • Paid Google Cloud products such as Pub/Sub, Cloud Run, or BigQuery streaming for Analytics are not available to projects on the Spark plan.[4]
  • Firestore free quota listed by one third-party guide: 50,000 reads, 20,000 writes and 20,000 deletes per day, and 1 GiB stored data.[10] One source only.
  • The same guide lists overage at $0.03 per 100,000 reads and $0.09 per 100,000 writes and notes rates vary by region.[10] One source only.

Pricing as reported for Firebase:

  • Spark: $0 (No payment method required for most features; a product that exceeds its quota is cut off rather than billed, per third-party summary) [4]
  • Blaze: Pay as you go (Keeps the same free quotas and bills for usage above them; unlocks paid Google Cloud products) [4]

Suits teams already building on Google Cloud who accept usage-based billing. That is our reading of the facts above, not something a source says.

Neon

Neon provides serverless Postgres with usage-based pricing across Free, Launch and Scale plans.[5]

Limits and things to check:

  • Hitting any Free monthly limit (100 CU-hours, 0.5 GB storage, 5 GB egress) suspends compute until the next billing month, and upgrading to Launch or Scale resumes it immediately.[5]
  • Free plan autoscaling goes up to 2 CU; Launch and Scale go up to 16 CU.[5]
  • Storage is $0.35 per GB-month on both paid plans, per search summary.[5]

Pricing as reported for Neon:

  • Free: $0 [5]
  • Launch: $0.106 per CU-hour [5]
  • Scale: $0.222 per CU-hour (Usage-based, autoscaling up to 16 CU, storage $0.35 per GB-month; SOC 2 and HIPAA features sit on this plan) [5]

Plan limits are longer than fit here and some sources disagree on them, so read the limits on the vendor pricing page.

Suits developers who want plain Postgres with scale-to-zero and branching-style workflows and usage-based billing. That is our reading of the facts above, not something a source says.

Supabase

Supabase hosts Postgres databases and exposes them through a Data API, with Row Level Security policies controlling which rows each role can read or write.[11]

What the sources say:

  • The fix given for that lint is to run 'alter table ... enable row level security' and then add policies defining who may access rows.[12]
  • Once RLS is enabled with no policies, no data is accessible through the API to the anon role until policies are added.[13]
  • Supabase sends daily emails about exposed tables that lack RLS and provides a Security Advisor in the dashboard.[14]
  • The hardening guide suggests an event trigger that enables RLS automatically on new tables, and describes options such as disabling the Data API or exposing a custom schema instead of public.[14]
  • Supabase documents publishable keys (sb_publishable_...) for client-side code and secret keys (sb_secret_...) for servers and Edge Functions; the legacy anon and service_role keys are being retired by the end of 2026.[15]
  • Policies should target the anon and authenticated roles.[15]

Limits and things to check:

  • The database linter rule 0013 (RLS disabled in public) is rated ERROR and states that without RLS on a public table, anyone with the project URL can create, read, update and delete rows in it.[12] One source only.
  • Any table created in the public schema is accessible through the Supabase Data API, and the Securing your API guide recommends enabling RLS on tables, views and functions there.[11]
  • Tables created in the dashboard Table Editor have RLS enabled by default; tables created through raw SQL or the SQL Editor need RLS enabled manually.[13]
  • The service_role key has the BYPASSRLS attribute, so RLS policies never apply to it.[15]
  • A Free-plan Supabase project is paused after one week of inactivity, per third-party summaries.[16]

Pricing as reported for Supabase:

  • Free: $0 [16] One source only, so confirm it on the vendor page.
  • Pro: $25 per month [6]

Plan limits are longer than fit here and some sources disagree on them, so read the limits on the vendor pricing page.

Suits teams that want a Postgres database queried directly from client code and are willing to write and review RLS policies. That is our reading of the facts above, not something a source says.

How to choose a backend

Start from your situation, not from the list:

  • For teams wanting an open-source backend with a hosted option, start with Appwrite.
  • For developers who want a reactive backend where queries update live, start with Convex.
  • For teams already building on Google Cloud who accept usage-based billing, start with Firebase.
  • For developers who want plain Postgres with scale-to-zero and branching-style workflows and usage-based billing, start with Neon.
  • For teams that want a Postgres database queried directly from client code and are willing to write and review RLS policies, start with Supabase.

Open the vendor pricing page for your shortlist before you decide, since plans change.

Where Continuum fits

We make Continuum Supabase Security Review. Weigh what we say here with that in mind. The tools above are the better choice when you want software you run yourself; ours is the better choice when you want a person to do or read the work.

Continuum Supabase Security Review (ours)

A human review of a Supabase app covering row level security policies, key exposure, storage rules, auth config and service-role usage.[7]

What our own page says:

  • It returns ranked findings with corrected SQL and a proof for each, in 48 hours.[7]

Limits and things to check:

  • It is a manual review of one app, not a continuous monitor.[7]

Pricing as reported for Continuum Supabase Security Review:

  • Supabase Security Review: Quoted on the page (48 hour turnaround) [7]

Suits a team running on Supabase that wants a person to read its policies and keys before launch.

Details on Continuum Supabase Security Review.

Running on Supabase?

Row level security and key handling are where most AI-built Supabase apps leak. A person can read yours. See the Supabase Security Review
Book a call →See all services and prices →
FAQ

Straight answers

Which of these have a free plan?
Appwrite, Firebase, Neon and Supabase have a free plan or free tier according to the sources we read. Limits differ, so check each one.
Is this list a ranking?
No. It is alphabetical. Which backend fits depends on your team, your budget and the problem you are solving.
When were these sources read?
All sources on this page were read on 2026-11-05. Prices and limits change, so confirm on the vendor page before you buy.
Keep reading
Best auth providers for AI-built appsbest authentication provider for ai built appsSupabase vs Firebasesupabase vs firebaseSupabase vs Appwritesupabase vs appwriteAll comparisonsBest of lists, head to heads and alternatives across every area we cover.
Sources
  1. 1. Appwrite Free plan docs, Appwrite, 2026-11-05: Appwrite's own page
  2. 2. Appwrite pricing, Appwrite, 2026-11-05: Appwrite's own page
  3. 3. Convex plans, Convex, 2026-11-05: Convex's own page
  4. 4. Firebase pricing plans, Google Firebase, 2026-11-05: Firebase's own page
  5. 5. Neon Pricing Plans, Neon, 2026-11-05: Neon's own page
  6. 6. Supabase pricing (markdown), Supabase, 2026-11-05: Supabase's own page
  7. 7. Continuum Supabase Security Review on uxcontinuum.com, Continuum, 2026-11-05: Continuum Supabase Security Review's own page
  8. 8. Introducing Appwrite Start, Appwrite, 2026-11-05: Appwrite's own page
  9. 9. Convex limits, Convex, 2026-11-05: Convex's own page
  10. 10. Firebase Pricing 2026: Plans, Costs and Free Limits, Activepieces, 2026-11-05: third-party page
  11. 11. Securing your API, Supabase, 2026-11-05: Supabase's own page
  12. 12. Splinter lint 0013 rls disabled in public, Supabase (GitHub Pages, splinter project), 2026-11-05: third-party page
  13. 13. Row Level Security, Supabase, 2026-11-05: Supabase's own page
  14. 14. Hardening the Data API, Supabase, 2026-11-05: Supabase's own page
  15. 15. Understanding API keys, Supabase, 2026-11-05: Supabase's own page
  16. 16. Supabase Pricing: 2026 Guide, Jetadmin, 2026-11-05: third-party page
Best backends for AI-built apps | Continuum