How to Add OAuth2 and JWT Authentication to Your AI Agents (Step-by-Step Guide)<\/a>.<\/p>\nDevEx: local to prod with Git<\/h2>\n
Winning teams depend on reproducible environments and fast feedback loops.<\/p>\n
CLI and local parity<\/h3>\n
Nhost<\/strong> CLI spins up Postgres, the GraphQL API, authentication, storage, and functions locally with Docker, mirroring production behavior closely. Supabase<\/strong> CLI has strong local dev as well. Appwrite<\/strong> centers on its server runtime locally; it works but aligning local and cloud setups for large teams may take additional effort.<\/p>\nCI\/CD and previews<\/h3>\n
Nhost<\/strong> ties deployments to Git: schema migrations, seed data, and serverless\/functions ship on push, with preview environments for every PR. Supabase<\/strong> supports migration pipelines and automated deploys; previews vary by setup. Appwrite<\/strong> CI often relies on SDK scripts or infrastructure-as-code to synchronize environments.<\/p>\nObservability<\/h3>\n
Nhost<\/strong> centralizes logs, traces, and metrics across Postgres, the GraphQL API, storage, and functions\/containers for fast incident response. Supabase<\/strong> offers observability features with differences by plan and via external tools. Appwrite<\/strong> provides logs and metrics; depth and retention depend on your deployment and tier.<\/p>\nPricing and scaling realities<\/h2>\n
All three are cost-efficient early on. At scale, usage patterns dominate: database IO, function invocations, and especially storage egress.<\/p>\n
Free tiers and overages<\/h3>\n
Nhost<\/strong> uses transparent usage buckets across database, storage, and compute so you can forecast growth. Supabase<\/strong> has generous free tiers; watch function and realtime usage as traffic grows. Appwrite<\/strong> Cloud pricing maps to allocated resources; model spikes and autoscaling behavior for production.<\/p>\nEgress and CDN<\/h3>\n
Media-heavy products pay the most on egress across Nhost vs Supabase vs Appwrite. Nhost<\/strong> ships CDN optimizations and caching controls that reduce origin hits, but you should still budget for peak traffic and global audiences.<\/p>\nPerformance at scale<\/h3>\n
Nhost<\/strong> scales vertically and horizontally with connection pooling, read replicas, and workload isolation for functions\/containers. Supabase<\/strong> provides autoscaling Postgres and caching layers. Appwrite<\/strong> scales with resource-based tiers; ensure headroom for hotspots like event fan-out.<\/p>\nSecurity, compliance, and enterprise<\/h2>\n
Regulated teams need more than features\u2014they need auditable controls that keep pace with growth.<\/p>\n
Compliance and networking<\/h3>\n
Nhost<\/strong> offers SOC 2, automated backups, private networking and peering options, and granular access controls. Validate comparable offerings and limits on Supabase<\/strong> and Appwrite<\/strong> for your intended tier and region coverage.<\/p>\nSSO and org controls<\/h3>\n
Nhost<\/strong> supports SSO\/SAML, org-wide roles, and audit logs that span the GraphQL API and services. Ensure parity on competing plans if you need least-privilege and traceability across teams and environments.<\/p>\nFirebase alternative: where each fits<\/h2>\n
If you are seeking an open-source BaaS and a credible Firebase alternative:<\/p>\n
\n- Nhost<\/strong>: SQL-first, GraphQL API by default, real-time, and extensible with serverless plus bring-your-own containers; best when your model is relational and you want to avoid lock-in.<\/li>\n
- Supabase<\/strong>: SQL-first with REST\/RPC and optional GraphQL; excellent for teams already standardized on Postgres tooling.<\/li>\n
- Appwrite<\/strong>: General-purpose open-source BaaS with document-style collections; approachable for CRUD apps that prefer SDK-driven development.<\/li>\n<\/ul>\n
Migration and portability<\/h2>\n
Your future self will thank you for choosing a path with easy exits.<\/p>\n
Supabase to Nhost<\/h3>\n
Export Postgres schema and data, carry over your RLS policies, and turn on Nhost\u2019s auto-generated GraphQL API. Map Edge Functions to Nhost serverless functions or containers. Client apps usually need minimal changes other than pointing to the new GraphQL endpoint and auth domain.<\/p>\n
Appwrite to Nhost<\/h3>\n
Transform collections\/documents into normalized Postgres tables, reapply permissions as RLS, and swap SDK calls for GraphQL queries\/mutations plus signed URL storage flows. Background tasks move into Nhost functions or long-running containers where needed.<\/p>\n
Example stacks by use case<\/h2>\n
Copy these blueprints to accelerate delivery on Nhost.<\/p>\n
Indie SaaS<\/h3>\n\n- Data<\/strong>: Postgres tables with tenant_id columns and RLS policies<\/li>\n
- API<\/strong>: Nhost GraphQL API for CRUD and relations<\/li>\n
- Auth<\/strong>: OAuth + email\/password with role claims<\/li>\n
- Storage<\/strong>: Signed uploads for invoices and avatars<\/li>\n
- Functions<\/strong>: Webhooks for billing and metering<\/li>\n<\/ul>\n
Realtime collaboration<\/h3>\n\n- Data<\/strong>: Documents, comments, presence tables<\/li>\n
- API<\/strong>: GraphQL subscriptions for presence, cursors, and edits<\/li>\n
- Storage<\/strong>: Asset uploads with CDN delivery<\/li>\n
- Extensibility<\/strong>: Containerized OT\/CRDT service alongside GraphQL<\/li>\n<\/ul>\n
AI app<\/h3>\n\n- Data<\/strong>: pgvector for embeddings stored with content metadata<\/li>\n
- API<\/strong>: GraphQL API for search and scoped content retrieval<\/li>\n
- Auth<\/strong>: JWT claims for per-user and per-organization limits<\/li>\n
- Functions\/containers<\/strong>: LLM orchestration with secure provider calls and event-driven pipelines<\/li>\n<\/ul>\n
Decision checklist<\/h2>\n\n- Do you want a GraphQL-first<\/strong> experience with instant schema and subscriptions?<\/li>\n
- Will your data model need native Postgres<\/strong> features and extensions?<\/li>\n
- Do you require RLS-backed<\/strong> row and field security rather than app-layer checks?<\/li>\n
- Do you need extensibility<\/strong> beyond functions\u2014like bring-your-own containers?<\/li>\n
- Does your team rely on Git-based CI\/CD<\/strong>, previews, and local parity?<\/li>\n
- Are your workloads sensitive to egress<\/strong> and invocation<\/strong> costs at scale?<\/li>\n
- Do you have compliance<\/strong>, SSO\/SAML, or private networking requirements?<\/li>\n<\/ul>\n
Why Nhost?<\/strong> For teams that want a production-ready, open-source BaaS with a best-in-class GraphQL API on Postgres, secure-by-default authz, storage with CDN, serverless functions, and the option to bring your own containers, Nhost balances speed today with flexibility tomorrow.<\/p>\nGet started for free<\/strong> and ship your next release with less infrastructure, more product.<\/p>\nFrequently Asked Questions<\/h2>\nIs Nhost a Firebase alternative and open-source BaaS?<\/h3>\n
Yes. Nhost is a managed, open-source\u2013based stack built on Postgres with an instant GraphQL API, authentication, storage, and functions. It is a strong Firebase alternative when you want SQL and GraphQL at the core instead of a proprietary document store.<\/p>\n
Does Nhost support REST if my team isn\u2019t ready for GraphQL?<\/h3>\n
Yes. You can expose REST endpoints derived from predefined GraphQL operations, retaining the same authentication and RLS guarantees while your team adopts GraphQL at its own pace.<\/p>\n
How hard is it to migrate from Supabase to Nhost?<\/h3>\n
Typically straightforward. Export your Postgres schema and data, carry over RLS policies, enable Nhost\u2019s auto-generated GraphQL API, and port Edge Functions to Nhost serverless functions or containers. Client updates are usually limited to endpoints and auth domains.<\/p>\n
What about bring-your-own containers\u2014why does it matter?<\/h3>\n
It lets you run any language or runtime\u2014such as a Python ML service or a Go event processor\u2014right next to your GraphQL API and database without standing up separate infrastructure. This reduces latency, complexity, and operational overhead.<\/p>\n
How do pricing dynamics differ at scale?<\/h3>\n
All three platforms meter storage, egress, and compute. On Nhost, the main levers are database\/storage usage and function\/container compute. Regardless of provider, you should model media egress and function invocations early to avoid surprises.<\/p>\n","protected":false},"excerpt":{"rendered":"
If your team wants to move from day 1 to 10,000 users without pausing to babysit infrastructure, the choice of backend matters. This comparison looks …<\/p>\n","protected":false},"author":2,"featured_media":9,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[11,13,10,9,12],"class_list":["post-8","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-comparisons","tag-firebase-alternative","tag-graphql-api","tag-nhost-vs-appwrite","tag-nhost-vs-supabase","tag-open-source-baas"],"_links":{"self":[{"href":"https:\/\/blogs.aithor.ca\/nhost\/wp-json\/wp\/v2\/posts\/8","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.aithor.ca\/nhost\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.aithor.ca\/nhost\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.aithor.ca\/nhost\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.aithor.ca\/nhost\/wp-json\/wp\/v2\/comments?post=8"}],"version-history":[{"count":0,"href":"https:\/\/blogs.aithor.ca\/nhost\/wp-json\/wp\/v2\/posts\/8\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.aithor.ca\/nhost\/wp-json\/wp\/v2\/media\/9"}],"wp:attachment":[{"href":"https:\/\/blogs.aithor.ca\/nhost\/wp-json\/wp\/v2\/media?parent=8"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.aithor.ca\/nhost\/wp-json\/wp\/v2\/categories?post=8"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.aithor.ca\/nhost\/wp-json\/wp\/v2\/tags?post=8"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}