Supabase
SupabaseReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
41 reviews
from
External reviews are not included in the AWS star rating for the product.
Postgres + RLS and Phone OTP Made Shipping Our Expo App Fast
What do you like best about the product?
Honestly, the biggest thing for us is Postgres as the source of truth, with RLS doing most of the auth work. We ship a React Native app on Expo, and instead of building a separate API layer plus auth middleware, row-level security policies handle about 90% of access control directly in the database. When we add a new table, we write the policy once and the client can query it via the JS SDK—no controllers, no DTOs, and no glue code.
Phone OTP auth was the other huge win. We’re India-first and phone-first, and Supabase Auth ships with phone OTP out of the box. You plug in an SMS provider and you’re basically done. It probably saved us around two weeks of building and maintaining our own auth flow.
The dashboard SQL editor sounds boring, but I use it 10x a day. When something looks off in prod, I open the editor, run a query, and fix a row. No SSH tunnel and no separate admin panel. Saved queries and history are genuinely useful when you’re debugging the same data shapes over and over.
Edge Functions in Deno have been great for webhook handlers and cron jobs. supabase functions serve gives you real local-to-prod parity, so the dev loop stays fast. And the local CLI stack (Postgres + Studio in Docker) means we never have to touch prod data while testing schema changes.
Pricing is the kicker: Postgres + auth + storage + edge functions on the Pro plan costs less than Firebase alone would for our usage.
Phone OTP auth was the other huge win. We’re India-first and phone-first, and Supabase Auth ships with phone OTP out of the box. You plug in an SMS provider and you’re basically done. It probably saved us around two weeks of building and maintaining our own auth flow.
The dashboard SQL editor sounds boring, but I use it 10x a day. When something looks off in prod, I open the editor, run a query, and fix a row. No SSH tunnel and no separate admin panel. Saved queries and history are genuinely useful when you’re debugging the same data shapes over and over.
Edge Functions in Deno have been great for webhook handlers and cron jobs. supabase functions serve gives you real local-to-prod parity, so the dev loop stays fast. And the local CLI stack (Postgres + Studio in Docker) means we never have to touch prod data while testing schema changes.
Pricing is the kicker: Postgres + auth + storage + edge functions on the Pro plan costs less than Firebase alone would for our usage.
What do you dislike about the product?
After running this in production, I’ve hit a few real pain points.
Cold starts on Edge Functions are noticeable. The first invocation after idle can take 800ms–1.5s, which is rough for user-facing endpoints. We’ve ended up keeping functions warm with a cron, but that feels more like a workaround than a real solution. The dashboard performance also drops once a table gets past a few hundred thousand rows. On our largest table, opening the table editor is sluggish enough that I usually switch to the SQL editor instead.
Support on the free/Pro tier is limited to community Discord and GitHub Discussions. That’s fine for general questions, but it’s slow when you run into something blocking in prod. Paid support is gated behind the Team plan, which is a steep jump from Pro. We’ve had a couple of incidents where I would’ve happily paid per incident for a direct response.
The Supabase AI assistant in Studio is hit-or-miss. For SQL, it’s decent for simple queries, but it hallucinates surprisingly often on schema-aware questions, suggesting columns or joins that don’t exist in our schema. In practice, Cursor + the Supabase MCP has been more useful day to day than the in-dashboard assistant.
The migrations workflow has rough edges too. The db diff sometimes generates noisy diffs that include things you didn’t change (like default value reformats or trigger reorderings), so you end up hand-editing migration files more than you should.
Cold starts on Edge Functions are noticeable. The first invocation after idle can take 800ms–1.5s, which is rough for user-facing endpoints. We’ve ended up keeping functions warm with a cron, but that feels more like a workaround than a real solution. The dashboard performance also drops once a table gets past a few hundred thousand rows. On our largest table, opening the table editor is sluggish enough that I usually switch to the SQL editor instead.
Support on the free/Pro tier is limited to community Discord and GitHub Discussions. That’s fine for general questions, but it’s slow when you run into something blocking in prod. Paid support is gated behind the Team plan, which is a steep jump from Pro. We’ve had a couple of incidents where I would’ve happily paid per incident for a direct response.
The Supabase AI assistant in Studio is hit-or-miss. For SQL, it’s decent for simple queries, but it hallucinates surprisingly often on schema-aware questions, suggesting columns or joins that don’t exist in our schema. In practice, Cursor + the Supabase MCP has been more useful day to day than the in-dashboard assistant.
The migrations workflow has rough edges too. The db diff sometimes generates noisy diffs that include things you didn’t change (like default value reformats or trigger reorderings), so you end up hand-editing migration files more than you should.
What problems is the product solving and how is that benefiting you?
We needed a backend stack for our React Native app that didn’t require us to run our own infrastructure. Supabase replaced what would have been a Node/Express API, Auth0, S3, a managed Postgres host, and a job runner—all consolidated into a single platform with one CLI and one dashboard.
The Postgres ecosystem integration is a big part of why this works for us. We can stick with standard pg tooling, standard migrations, and standard SQL—there’s no proprietary query language to learn. And when we need Postgres extensions like pgvector, pg_cron, or PostGIS, they’re essentially a click away. On the client side, the Expo/React Native SDK plugs in cleanly: auth, realtime subscriptions, and storage uploads all work without us having to build and maintain a wrapper layer.
The practical payoff is speed. As a small team, we can ship features at a pace that would otherwise require a dedicated backend engineer. A feature that needs a new table, an auth-gated endpoint, file storage, and a webhook handler used to mean a week of glue code; with Supabase, it’s more like an afternoon. That time saved goes straight back into product work, which is what matters most at our stage.
The Postgres ecosystem integration is a big part of why this works for us. We can stick with standard pg tooling, standard migrations, and standard SQL—there’s no proprietary query language to learn. And when we need Postgres extensions like pgvector, pg_cron, or PostGIS, they’re essentially a click away. On the client side, the Expo/React Native SDK plugs in cleanly: auth, realtime subscriptions, and storage uploads all work without us having to build and maintain a wrapper layer.
The practical payoff is speed. As a small team, we can ship features at a pace that would otherwise require a dedicated backend engineer. A feature that needs a new table, an auth-gated endpoint, file storage, and a webhook handler used to mean a week of glue code; with Supabase, it’s more like an afternoon. That time saved goes straight back into product work, which is what matters most at our stage.
Perfect Remote DB for My React Native Mobile App
What do you like best about the product?
Remote DB for my mobile app on react native
What do you dislike about the product?
So far I have nothing to dislike. Or IDK.
What problems is the product solving and how is that benefiting you?
I have fast PostgreSQL database for my maps app, that needs to be super fast
Effortless Database Management with Great UI
What do you like best about the product?
I use Supabase for hosting databases for tools. I appreciate that it allows a very simple and easy way to spin up a database, which is easy to access from code and apps. It also offers a good UI and front end to manage those databases. I like the free tier and the ease of use of Supabase. The initial setup is incredibly easy.
What do you dislike about the product?
I wish there were more ways to sign in. Google Auth would be nice.
What problems is the product solving and how is that benefiting you?
I find Supabase offers a simple way to spin up databases, making them easy to access from code and apps, with a good UI to manage them.
Best Friend Every Developer Needs
What do you like best about the product?
I like Supabase Auth. All you need to do is add the passkeys, enable the SSO toggle, and you're done. It's really easy, fast, and straightforward to configure. It's also very easy to integrate with providers like Google and GitHub. It's free for young developers, and offers one-click onboarding. All projects are listed on the dashboard, and they have an AI that analyzes the database and finds security vulnerabilities.
What do you dislike about the product?
Supabase and run a query manually, which I find difficult. It also makes me nervous — I'm always worried about accidentally deleting my database, especially since I'm using Supabase in my product, Lync.life. On top of that, I find it a little slow sometimes.
What problems is the product solving and how is that benefiting you?
he fact that it's free is a huge plus, especially when you're building something from scratch and don't want to worry about costs piling up. It's simple enough that I didn't have to spend days figuring things out — I could just get started. The MCP support is a nice touch too, it fits right into my workflow without any friction. What really gives me peace of mind is the built-in AI that catches and fixes database mistakes — that kind of safety net means a lot when you're dealing with real data. I'm actually running it on my live project right now with large database connections, and honestly, it just works. No drama, no surprises.
Simple to Use, Powerful Ecosystem That Just Works
What do you like best about the product?
Simple to use, powerful ecosystem that does more than the sum of it's parts
What do you dislike about the product?
Can feel intimidating to begin with, but picking hairs at this point...
What problems is the product solving and how is that benefiting you?
It's a central place to orchestrate, store and analyse data, it integrates seamlessly, and scales with your growth
Very Easy to Use—A Huge Help for Setting Up Websites
What do you like best about the product?
Very easy to use and navigate, it helped me a ton when setting up websites
What do you dislike about the product?
Nothing that I dislike, to improve I would say the 7 days hold however I know it's required so not really a point to mentioned
What problems is the product solving and how is that benefiting you?
The problem is solving it's saving the data from the websites I've build - it's benefitting me by not having to pay a ton of money and making things easy for me
All-in-One Postgres Backend That Helps You Ship Fast
What do you like best about the product?
What I like most about Supabase is how it brings so many backend essentials into one place. You get a full Postgres database along with Auth, Storage, Realtime, auto-generated REST APIs, Edge Functions, and vector support, which means you don’t have to stitch together a bunch of separate services just to get a product off the ground. That’s a big win when you want to move fast while still building on top of Postgres.
What do you dislike about the product?
Supabase has quotas across many areas, but once you exceed those limits you can still run into overages for things like storage, realtime, and Edge Function invocations. Compute is billed separately per project server. The spend cap can help reduce surprises from unexpected usage, but it doesn’t apply to every billing category, including compute.
What problems is the product solving and how is that benefiting you?
This benefits me because it lets me build and ship much faster. I spend less time on backend plumbing and less time maintaining custom infrastructure, while still keeping the flexibility of SQL and Postgres as the app grows. It’s especially useful for MVPs and products where I want to move quickly, without giving up too much control over data and permissions.
Convenient, Scalable Solution That Helps Startups Move Fast
What do you like best about the product?
It’s a very convenient solution for a startup that wants to move fast while still building a solid, scalable digital product.
What do you dislike about the product?
I have nothing to complain about, is a very special solution.
What problems is the product solving and how is that benefiting you?
is our database, where we store all the most important information with dozens of tables about our users. It is, in fact, the foundation of our company.
Total simplicity for your projects
What do you like best about the product?
Simplicity in project management, friendly in every way.
What do you dislike about the product?
after almost 2 years of using it, I don't see any low points for now.
What problems is the product solving and how is that benefiting you?
High-level database that is very simple to connect to any project.
Open Source Flexibility with Easy Setup
What do you like best about the product?
I like Supabase because it is open source and has great documentation. The beautiful UI and user experience really stand out to me.
What do you dislike about the product?
So far nothing
What problems is the product solving and how is that benefiting you?
I switched to Supabase from Firebase, and it's been really good. The initial setup was easy.
showing 1 - 10