A backend-as-a-service (BaaS) platform is more than a hosted database — it’s the whole package: authentication, serverless functions, file storage, and realtime sync, wired together so a small team can ship an app without standing up its own infrastructure. That’s a different question than “which hosted database should I use,” which is why this comparison deliberately sets aside Supabase (already covered on this site as a database-as-a-service option alongside PlanetScale and Neon) and instead looks at three platforms built around the full backend: Google’s Firebase, the open-source Appwrite, and the Hasura-powered Nhost.
At a Glance
| Platform | Database Model | Free Tier | Entry Paid Plan | Self-Hostable? |
|---|---|---|---|---|
| Firebase | Firestore (NoSQL) + Realtime Database | Spark: 50K MAU auth, 1GB Firestore storage, no credit card required | Blaze: pay-as-you-go, Spark limits included free | No — Google Cloud only |
| Appwrite | Document/NoSQL (with Postgres option) | Free org plan, resources freeze (not deleted) at limits | Pro (usage-based, extra charges past limits) | Yes — open source, self-hostable |
| Nhost | Dedicated PostgreSQL instance | Starter: free, 1GB DB, 1GB storage, 1 active project | Pro: from $25/month + $15 compute credit | Partially — open components, managed platform is primary |
Short Verdict
Firebase is still the most mature and battle-tested option, with the deepest mobile SDKs and the largest free-tier ceiling for auth (50,000 monthly active users). Appwrite is the best fit if you want an open-source, self-hostable backend you can run on your own infrastructure without changing your application code. Nhost is the strongest choice if your app’s data model is fundamentally relational and you want a real dedicated Postgres instance plus Hasura’s instant GraphQL layer, rather than a NoSQL document store.
Firebase: The Mature Default
Firebase runs on two plans: Spark, a genuinely free tier with no payment method required, and Blaze, pay-as-you-go pricing that keeps Spark’s free quotas and bills only for usage above them (plus up to $300 in free credit for eligible accounts). The free quotas are generous for early-stage apps: authentication is free up to 50,000 monthly active users via Identity Platform, Firestore gives 1 GiB storage with 20,000 writes and 50,000 reads per day, and Hosting includes 10GB storage with 360MB/day transfer. Cloud Functions, notably, requires the Blaze plan — it isn’t available on Spark at all. Firebase’s core services are Authentication, Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Hosting, all tied into the Google Cloud ecosystem (and billed at Google Cloud rates once you exceed free quotas).
Appwrite: Open Source, Self-Hostable
Appwrite’s core differentiator is that it’s fully open source, with its source code on GitHub, and designed to be self-hosted on your own servers in addition to the managed Appwrite Cloud. Its free organization plan is “100% free” with no time limit, though hitting a resource limit freezes the project (making the console read-only) rather than deleting data, until you upgrade or the billing cycle resets. The Pro plan removes that freeze and adds overage billing with 75%/100% usage alerts and an optional budget cap. Every plan includes the “full Appwrite platform toolkit” — Auth, Databases, Storage, Functions, and Realtime are bundled rather than priced as separate add-ons, alongside additional products like Messaging and Sites. Appwrite also offers dedicated database compute tiers for teams that need guaranteed resources.
Nhost: Postgres-First, Hasura-Powered
Nhost’s defining choice is using a real, dedicated PostgreSQL instance per project rather than a shared NoSQL document store, paired with the Hasura GraphQL Engine for instant realtime GraphQL subscriptions and event triggers, role-based authorization, and auto-generated APIs. Plans run Starter (free forever, 1 GB database, 1 GB storage, 5 GB egress, one active project that pauses after a week of inactivity), Pro (from $25/month, includes $15 in compute credit, 10 GB database and 50 GB storage included, automated backups and point-in-time recovery starting at $100), Team (from $599/month), and custom Enterprise. Authentication supports unlimited users on every plan, including social OAuth, email/password, magic links, and 2FA, with advanced security features reserved for Enterprise. Functions execution is billed per GB-hour past the included allotment.
Feature Comparison
| Capability | Firebase | Appwrite | Nhost |
|---|---|---|---|
| Auth free tier | 50K MAU | Unlimited on Free (subject to other project limits) | Unlimited users on all plans |
| Database type | NoSQL document (Firestore) + Realtime DB | Document/NoSQL, with a managed Postgres option | Dedicated PostgreSQL |
| GraphQL support | No native GraphQL layer | No native GraphQL layer | Yes — Hasura GraphQL Engine built in |
| Serverless functions | Cloud Functions (Blaze plan only) | Included on all plans | Included, billed per GB-hour past quota |
| Self-hosting | Not possible | Fully supported, open source | Core components open, managed platform is primary path |
Pros and Cons
- Firebase pros: mature SDKs for every mobile/web platform, huge community, generous auth free tier.
- Firebase cons: Cloud Functions requires the paid Blaze plan; NoSQL data modeling can be awkward for relational data; vendor lock-in to Google Cloud.
- Appwrite pros: genuinely self-hostable with no feature gating between cloud and self-hosted; generous free org plan with no hard deletion on limits.
- Appwrite cons: smaller mobile SDK maturity than Firebase; dedicated database compute tiers get expensive fast ($999–$4,099/month).
- Nhost pros: real relational database with proper SQL, built-in GraphQL via Hasura, unlimited auth users even on the free tier.
- Nhost cons: free project pauses after a week of inactivity; Team plan jumps steeply from Pro ($25 to $599/month).
Who Each Platform Fits Best
Firebase fits mobile-first teams that want the most mature, widely documented backend with minimal setup. Appwrite fits teams with data-residency or compliance requirements who need to self-host, or anyone who wants to avoid cloud vendor lock-in entirely. Nhost fits teams whose data is naturally relational and who want GraphQL out of the box without hand-building a Hasura deployment themselves.
Bottom Line
The real decision here isn’t “which BaaS is best” in the abstract — it’s whether your data is relational, whether you need to self-host, and how much you value Firebase’s maturity against newer, more open alternatives. Firebase remains the safest default for mobile apps with NoSQL-friendly data. Appwrite is the right call when self-hosting or open-source licensing is a requirement, not a preference. Nhost is the right call when you want Postgres and GraphQL without assembling the stack yourself.
FAQ
Can I use Firebase Cloud Functions on the free Spark plan?
No — according to Firebase’s own pricing page, Cloud Functions requires the pay-as-you-go Blaze plan, though Blaze still includes a free monthly quota (2 million invocations) before charges apply.
Is Appwrite’s free plan time-limited?
No, Appwrite describes free organizations as “100% free” indefinitely; hitting a resource limit freezes the project rather than deleting it or cutting off the trial.
Does Nhost’s free tier expire?
The project itself doesn’t expire, but it pauses after one week without activity and needs to be manually resumed.
Which of these includes built-in GraphQL?
Only Nhost, via the bundled Hasura GraphQL Engine with realtime subscriptions and event triggers; Firebase and Appwrite don’t ship a native GraphQL layer.
