Supabase

What do you like best about the product?

What I like best about Supabase is how easy it is to use from day one. The UI is clean and intuitive, so it's easy to manage databases, authentication, storage, and other services without feeling overwhelmed. It integrates well with modern frameworks and tools, making development smooth. Performance has been reliable for my use cases, and the pricing offers good value, especially considering how many features are included. The documentation and onboarding experience are excellent, so getting started is straightforward, and the community support is helpful whenever you run into issues. I also like that Supabase is actively adding AI-related capabilities and keeping up with modern development trends, which makes it feel like a platform that's continuously improving.

What do you dislike about the product?

One thing I dislike is that some advanced features can take a bit of time to understand if you're new to backend development. While the documentation is good, there are still moments where you have to dig through guides or community discussions to find specific answers. The platform is improving quickly, but a few areas of the dashboard could be more intuitive, and some newer features could benefit from more detailed documentation and examples.

What problems is the product solving and how is that benefiting you?

Supabase simplifies backend development by providing a managed database, authentication, storage, and APIs in one platform. Instead of spending time setting up and maintaining backend infrastructure, I can focus on building the actual application. It has reduced development time, made prototyping much faster, and simplified deployment. Having everything integrated in a single platform also makes projects easier to manage and maintain.

What do you like best about the product?

I started building an investor portal, and Claude recommended Supabase to use as my storage bucket.

What do you dislike about the product?

So far, I don’t have any complaints. It’s been easy to use, and it communicates well with Vercel.

What problems is the product solving and how is that benefiting you?

I’m building an investor portal from scratch, and it’s essentially functioning as a backend-as-a-service platform.

What do you like best about the product?

What I like most is how quickly I was able to get started. I was building an SEO rank tracker and needed a PostgreSQL database without spending time managing servers. Setting up the database, creating tables, and connecting it to n8n was straightforward.

What do you dislike about the product?

The biggest challenge for me was understanding some of the security settings, especially Row Level Security. It is a powerful feature, but there is definitely a learning curve if you are new to it. I had to spend some time reading the documentation and trying different approaches before I got it right.

What problems is the product solving and how is that benefiting you?

Supabase solved the problem of setting up and managing a database for my project. I was building an SEO rank tracker that collects keyword rankings on a schedule, and I needed a reliable place to store and query that data. Instead of spending time configuring a database server, I was able to create the database, connect it to n8n, and start collecting data quickly.

It also made reporting much easier. Since the data is stored in PostgreSQL, I could connect it directly to Looker Studio and build dashboards without exporting CSV files or writing complex scripts. That let me spend more time improving the project instead of managing the infrastructure.

What do you like best about the product?

What I appreciate most is how quickly I could go from an idea to a working backend without having to set up a separate auth service, database, and API layer. I built a sales management platform for my team almost entirely on Supabase—Postgres, auth, and the auto-generated APIs saved me from writing a ton of boilerplate. The dashboard is genuinely usable, too; I can jump in and check or edit table data directly while debugging, without needing a separate DB client.

Row-level security took a bit to wrap my head around at first, but once it clicked, it made role-based access (managers vs. executives, in my case) much simpler than writing all that logic manually on the backend. And the fact that it works so well with Next.js and Vercel made deployment painless. I didn’t have to think about infrastructure at all, which mattered a lot since I was building and shipping features solo, pretty much daily.

What do you dislike about the product?

The biggest issue I ran into was with caching behavior in Next.js. I hit a really frustrating bug where internal fetch() calls inside my API route handlers were being cached by Next.js, so I’d get stale data back from my Supabase queries even after the underlying data had changed. It took me quite a while to track down the root cause, and I ultimately had to manually pass a no-cache override to my Supabase client just to force fresh reads.

This isn’t really Supabase’s fault directly, but clearer documentation around this interaction—or a built-in flag to help prevent it—would’ve saved me hours.

What problems is the product solving and how is that benefiting you?

It's basically solved the "I need a backend but don't have time to build one" problem for me. I'm building a sales management platform for my team and Supabase gives me database, auth, and APIs all in one place instead of me stitching together separate services. That's saved me a ton of dev time, which matters a lot since I'm shipping features almost daily while also managing my actual sales team day-to-day. It basically let me be a one-person backend team without needing to be a backend expert.

What do you like best about the product?

I like the ease of use with Codex and Claude to operate Supabase. It's also great that Codex and Claude can connect to Supabase and control it. The setup was easy, which made things smoother for us.

What do you dislike about the product?

I think Supabase could be improved for multi-user environments and the emails sent from it could be more flexible.

What problems is the product solving and how is that benefiting you?

I use Supabase for connecting a database to an app. It offers a hosted database for multiple users and security, and the initial setup is easy.

What do you like best about the product?

Easy to use and learn. Even someone who does not have full knowledge of back-end coding can use and implement it. Creating projects and using it as a backend is super fun.

What do you dislike about the product?

Nothing as such, but there few features like branching and point in time recovery is still evolving with it.

What problems is the product solving and how is that benefiting you?

With Supabase, there it no need to set up and maintain a separate backend infrasture for early stage projects and internal tools. It basically cut development time and build a great backend infra.

What do you like best about the product?

It's free tier cannot be beaten, and it's super easy to integrate with any site you create. Absolutely the best platform to store data that you collect from your site.

What do you dislike about the product?

Honestly, there's very little I can complain about Supabase. Maybe the only thing is that for people who aren't very tech savvy or know how to code in SQL or have done something like this before, I can see it being a bit challenging.

What problems is the product solving and how is that benefiting you?

Allows me to store data the way I want it through Supabase, and it can store large amounts of data without spending an exorbitant amount of money.

What do you like best about the product?

The thing that stands out most is how much it speeds up the early stages of building a product. Getting a Postgres database, authentication, and auto-generated APIs running takes minutes instead of days, which matters a lot when you're validating an idea or working with a small team. The dashboard is clean and doesn't get in the way — I can browse tables, write SQL, and manage users without switching between five different tools.
I also appreciate that it's built on standard Postgres rather than some proprietary database layer. That means I'm not locked into Supabase-specific quirks, and I can fall back on regular SQL knowledge and tooling if I ever need to. Row-level security policies took a bit to learn, but once they clicked, they gave me a level of control that felt more solid than rolling my own auth checks in application code.
Real-time subscriptions and the storage bucket for files have also just worked reliably without much configuration, which isn't something I take for granted after using other backend-as-a-service tools.

What do you dislike about the product?

The documentation can feel inconsistent: some features are explained clearly, while others are covered more lightly or seem a bit out of date. I’ve also run into occasional slow query performance as my data grew, and I ended up needing to add manual indexing that wasn’t obvious upfront. The local development setup can be finicky compared with simply using the cloud dashboard, which has made getting started locally more frustrating than expected. Support response times have varied as well, and it seems to depend on the plan tier.

What problems is the product solving and how is that benefiting you?

It solves the problem of needing a full backend without having to hire a dedicated backend team early on. As a small team working on new startup ideas, we don’t have the time to set up and maintain our own database, auth system, and API layer from scratch for every project. Supabase covers those basics out of the box, which means we can go from an idea to a working prototype much faster.

The biggest benefit for us has been iteration speed. When we’re testing whether an idea has traction, we can stand up a real backend in an afternoon instead of spending a week getting the fundamentals in place. It also helps keep our infrastructure costs low in the early stages, since we’re not paying for a bunch of separate services—or dedicating engineering time—just to keep the essentials running.

What do you like best about the product?

Easy to implement and use for non technical marketers

What do you dislike about the product?

To this day (MVP phase) I still didn’t find anything to dislike about it

What problems is the product solving and how is that benefiting you?

Database for the MVP i’m building without a technical co-founder

What do you like best about the product?

I like the fact that Supabase is a SQL-based database, which makes it easy for me to query. The UI/UX is very simple, which I appreciate. They have lots of integrations with different products, which adds to its utility for me. Supabase is open source and free, with a very good free tier, which allows me to use it for most of my client apps without additional costs. It's quite easy to use, particularly since it integrates directly with FlutterFlow, and the initial setup was straightforward because it was just an API token-based integration.

What do you dislike about the product?

I think Supabase should focus more on the analytics part where I can query the data and create analytical dashboards then and there. This would increase the utility.

What problems is the product solving and how is that benefiting you?

I use Supabase for my app's relational database structure, and I find it easy to query as it’s SQL-based. It integrates well with Flutterflow, is open-source and free, and its simple UI/UX enhances my workflow.