Database for Astro: what 27 makers' products chose
Among 27 makers' products built with Astro that we know the database of, Supabase leads: 7 of them (26%). Next come ClickHouse (5) and Neon (4).
Where the data lives: a whole backend platform (database, auth and storage in one project), a managed database you reach from your own code, or the raw engine on your own server. Postgres is the default unless you have a reason to pick otherwise; analytics and graph databases sit next to it for workloads it handles poorly, not instead of it. How your code talks to it is its own decision (Database Access & ORMs).
What makers on Astro chose
| Option | Astro products | All makers | Free for | At 10,000 users |
|---|---|---|---|---|
| 7 (26%) | 45% | ~500 users | $25/moPro | |
| 5 (19%) | 4% | — | — | |
| 4 (15%) | 8% | None | $22/moLaunch | |
| 3 (11%) | 15% | ~2,000 users | $9.66/moBlaze (pay as you go) | |
| 3 (11%) | 2% | None | $7.40/moPostgres PS-5 (single node) | |
| 3 (11%) | 10% | ~500 users | $58/moAtlas Dedicated M10 | |
| 2 (7%) | 8% | — | — | |
| 2 (7%) | 2% | ~13,000 users | — | |
| 1 (4%) | 1% | — | — | |
| 1 (4%) | 0% | — | — |
Live makers' products with a source for both: that they're built with Astro, and what they use for database. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for; plans for personal use only, like a non-commercial hobby tier, don't count.
Which to pick, by situation
- You want the database, auth and file storage in one project, and plain SQL you can take elsewhere
Supabase 7 here - Your traffic is bursty or you run many preview deploys, and idle hours shouldn't cost much
Neon 4 here - You already run your own server and want a flat monthly cost
PostgreSQL 2 here
Supabase
Backend platform7 Astro products here (26%). Free up to about 500 users. About $25 a month at 10,000 users (Pro).
llms.txtMCPCLIIn Bolt, Lovable, Rork, v0Best forPostgres plus auth, storage and realtime in one project.
Trade-offAuth, storage and database in one vendor makes leaving harder later, and free projects pause after a week without activity.
“I use Supabase for database management, authentication provider, and as a backend with its edge functions feature. It helped me get started quickly and scale when more resources are needed.”
- One project covers Postgres, auth, storage and realtime, so a solo founder ships without stitching vendors or hiring a backend team. 4 sources
- It is real Postgres with SQL, row-level security and pgvector rather than a proprietary store. 4 sources
- Row-level security policies are hard to get right, so many apps end up exposing data publicly. 4 sources
- Reliability has been shaky for some, and it is not really built for self-hosting in practice. 1 source
Status page: 25+ incidents in the last 90 days, 6 major (its own page, 2026-10-19).
“Auth, Postgres, and row level security in one place. Chinilla needed user accounts, project storage, Stripe subscription gating, and per-row access control. Supabase gave me all of that with a real Postgres database underneath, not some proprietary query language. Migrations, RLS policies, and the JS client just work. Went from zero to full auth + data layer in a weekend”
DatabaseMaker says so · source ↗“I use Supabase for database management, authentication provider, and as a backend with its edge functions feature. It helped me get started quickly and scale when more resources are needed.”
DatabaseMaker says so · source ↗“The heartbeat of our backend. Auth, DB, and storage — fast, open-source, and smooth like butter.”
DatabaseMaker says so · source ↗“Helps power authentication and real-time data layers.”
AuthenticationDatabaseMaker says so · source ↗“We choose Supabase as our backend which is open-source just like Flowmodor!”
DatabaseMaker says so · source ↗“With Supabase, I didn't need to reinvent the wheel. After researching different authentication standards, it became clear to me that this was the best and safest option for my customers.”
DatabaseMaker says so · source ↗“It's open source, widely used, offered the integrations and features we needed, and it's priced reasonably.”
DatabaseMaker says so · source ↗
ClickHouse
Analytics (OLAP)5 Astro products here (19%).
llms.txtMCPIn LovableBest forFast aggregate queries over billions of rows of events, logs or metrics, self-hosted or on ClickHouse Cloud.
Trade-offBuilt for bulk inserts and scans, not frequent row updates or transactions; runs next to your main database, not instead of it.
“ClickHouse backs Basedash Warehouse, every team's centralized warehouse in Basedash. It's incredibly fast for complex queries and scales to any size we need.”
Status page: 15 incidents in the last 90 days, 1 major (its own page, 2026-10-19).
“ClickHouse backs Basedash Warehouse, every team's centralized warehouse in Basedash. It's incredibly fast for complex queries and scales to any size we need.”
DatabaseMaker says so · source ↗“ClickHouse saves us tons of gigabytes on disk space and delivers incredible performance. Without it, we wouldn’t be able to manage such a large volume of data efficiently. However, we’re still explore everything ClickHouse has to offer.”
DatabaseMaker says so · source ↗“Monitoring for its end-to-end payment solutions and real-time merchant dashboards.”
DatabaseMaker says so +1 · source ↗“Chosen for analytics due to its blazing-fast query performance.”
DatabaseMaker says so · source ↗
Neon
Managed database4 Astro products here (15%). About $22 a month at 10,000 users (Launch).
llms.txtMCPCLIIn v0Best forServerless Postgres that scales to zero, with a branch per preview deploy.
Trade-offCold starts after idle periods add latency to the first query, and heavy always-on workloads can cost more than a fixed server.
“Plug and play postgress database for out project, we have used it both for production and for staging environments with their branches feature.”
- Postgres scales to zero when idle, so early products and staging databases cost almost nothing until traffic arrives. 2 sources
- Branching copies the production database in seconds, so migrations and preview environments are tested against real data. 4 sources
- Separating compute from storage costs latency and performance compared with Postgres on local NVMe. 2 sources
- Parts of the stack, like autoscaling and some tooling, are not supported or openly licensed for self-hosting. 2 sources
“Plug and play postgress database for out project, we have used it both for production and for staging environments with their branches feature.”
DatabaseMaker says so · source ↗“Branching makes it easy to test schema changes safely which is great for moving fast without breaking things”
DatabaseMaker says so · source ↗“Saturn runs all company data on Neon serverless Postgres with Drizzle ORM. 130K+ EDINET documents, instant branching for dev/prod. Perfect for serverless-first architecture on Cloudflare Workers.”
DatabaseMaker says so · source ↗“The Postgres behind every account, subscription, and generation log. Branching makes schema changes painless. Serverless driver lets the Next.js routes talk to the DB without connection-pool drama. The free tier got EmailTemple from prototype to live with one config change.”
DatabaseMaker says so · source ↗
Firebase
Backend platform3 Astro products here (11%). Free up to about 2,000 users. About $9.66 a month at 10,000 users (Blaze (pay as you go)).
llms.txtIn Lovable, RorkBest forMobile apps that need offline sync and client-side SDKs.
Trade-offA document store without SQL joins; hard to migrate off.
“for real-time sync, secure authentication, and reliable cross-device performance at scale.”
- Auth, Firestore, Cloud Functions and hosting wire up in minutes, the fastest path to a working backend for a solo developer. 2 sources
- Real-time sync across devices, with offline caching that remains stronger than most all-in-one rivals. 2 sources
- A server-side change made the iOS SDK crash apps everywhere, exposing the risk of a closed SDK you cannot control. 4 sources
- It feels neglected and bolted onto Google Cloud, and it cannot be self-hosted, so leaving means a full migration. 3 sources
“for real-time sync, secure authentication, and reliable cross-device performance at scale.”
DatabaseMaker says so · source ↗“We are using Firebase for user authentication / login and also for analytics and in-app notifications.”
DatabaseMaker says so · source ↗“- Firebase Auth with ID tokens integrates seamlessly with our Cloudflare Worker proxy — JWT verification via Google's public JWKS is straightforward and well-documented - Firestore's REST API makes it easy to check user plans and track usage counts from edge workers without a heavy SDK - Generous free tier (Spark plan) covers auth + Firestore for early-stage products without upfront cost - Google-backed reliability and scale — no worry about the platform disappearing unlike smaller alternatives like Altogic or Rowy - Battle-tested Auth SDKs for web/mobile with Google, Apple, and email sign-in out of the box”
DatabaseMaker says so · source ↗
PlanetScale
Managed database3 Astro products here (11%). About $7.40 a month at 10,000 users (Postgres PS-5 (single node)).
llms.txtBest forApps that expect heavy scale and want zero-downtime schema changes.
Trade-offNo free tier.
“If you want really fast and reliable database technology this is the way to go. Not only does it allow us to have super fast performance of our service, their analytics help us make it even better.”
- Database branching, deploy requests and zero-downtime schema changes let teams change data models as fast as code. 2 sources
- It stays fast and reliable from launch to billions of rows, often with a single engineer running it. 3 sources
- Newer features like Neki sharding and TIN search are proprietary and cloud-only, raising vendor lock-in worries. 4 sources
- Dropping the free tier forced hobby projects to move elsewhere and cost it goodwill with indie developers. 2 sources
Status page: 5 incidents in the last 90 days, 4 major (its own page, 2026-10-19).
“If you want really fast and reliable database technology this is the way to go. Not only does it allow us to have super fast performance of our service, their analytics help us make it even better.”
DatabaseMaker says so +1 · source ↗“Absolutely GOATED database provider. Massively improved our performance just by migrating last year.”
DatabaseMaker says so · source ↗“PlanetScale gives Banger reliable, scalable database infrastructure, so we can focus on building the customer email workflows our users need.”
DatabaseMaker says so · source ↗
MongoDB
Managed database3 Astro products here (11%). Free up to about 500 users. About $58 a month at 10,000 users (Atlas Dedicated M10).
llms.txtBest forDocument-shaped data and teams already fluent in Mongo.
Trade-offNo joins or schema by default, so relational data and migrations take discipline you'd get for free in Postgres.
“Our Tech Stack Node.js and express MongoDB Nginx Reactjs Nextjs Digitalocean”
- The flexible document model lets fast-changing products evolve their data without rigid migrations. 4 sources
- Atlas starts on a free tier and handles scaling, backups and monitoring, so there is little database to manage. 4 sources
- Its history of unsafe defaults and lost writes left a lasting reputation that still keeps many developers away. 4 sources
- Anything beyond simple reads and writes is hard, and aggregation pipelines feel primitive next to SQL, which costs more over time. 2 sources
Status page: 13 incidents in the last 90 days, 5 major (its own page, 2026-10-19).
“Our Tech Stack Node.js and express MongoDB Nginx Reactjs Nextjs Digitalocean”
DatabaseMaker says so +1 · source ↗“Flexible document database built for modern apps.”
DatabaseMaker says so · source ↗Also chosen, and not seen yet
Fewer Astro products here: PostgreSQL (2), Tinybird (2), DuckDB (1), Aiven (1).
Real options for database not seen among these Astro products yet: Convex, Turso.
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on Astro.
- Firebase → Supabase 297 pull requests · how they moved
- Supabase → Neon 170 pull requests · how they moved
- Supabase → Firebase 113 pull requests · how they moved
- MongoDB → Supabase 75 pull requests · how they moved
- Neon → Supabase 63 pull requests · how they moved
- PostgreSQL → Neon 41 pull requests · how they moved
Getting database right
Pick a managed Postgres unless you have a reason not to. Turn on backups before your first real user, and use the provider's connection pooler from serverless functions.
- Never restoring a backup until the day you need one — the first bad migration or stray DELETE is a bad time to learn the backup is missing or too old.
- Opening a fresh database connection in every serverless function call, which runs Postgres out of connections under modest traffic; use the provider's connection pooler.
- Changing the schema by hand in the production console instead of through migrations, so local, preview and production databases quietly drift apart.
The rest of the Astro stack
What makers' Astro products chose for their other decisions, the most common pick for each:
- Hosting: Vercel 49 of 112
- Transactional Email: Resend 44 of 84
- Web Analytics: Cloudflare Web Analytics 18 of 47
- Payments: Stripe 22 of 34
- LLM API: OpenAI API 17 of 27
- Product Analytics: PostHog 13 of 14
- Authentication: Clerk 8 of 12
- Speech-to-Text & Text-to-Speech: ElevenLabs 7 of 12
Questions
What do most Astro apps use for database?
Among 27 makers' products built with Astro that we know the database of, Supabase leads: 7 of them (26%). Next come ClickHouse (5) and Neon (4).
What does database cost for an Astro app with 10,000 users?
On our usage model at 10,000 users, Supabase comes to about $25 a month (Pro); Neon comes to about $22 a month (Launch); Firebase comes to about $9.66 a month (Blaze (pay as you go)); PlanetScale comes to about $7.40 a month (Postgres PS-5 (single node)). Prices are from each vendor's pricing page.
Which database option stays free longest for an Astro app?
Tinybird: on our usage model its cheapest plan stays free up to about 13,000 users.
How this is counted: a product is on Astro when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its database. How evidence is collected.