Supabase

What do you like best about the product?

I like Supabase because it is easy to use and helps me build applications faster. I like that it provides database, authentication, storage, and APIs in one place. It is simple and good for small and large projects.

What do you dislike about the product?

I dislike that Supabase can be a little difficult for beginners when working with advanced database features. Sometimes the documentation is not very clear, and I need to spend more time to understand some things.

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

Supabase helps me solve backend problems like database, login, storage, and APIs. It gives many things in one place, so I can build my projects faster and with less code. It also saves my time and makes backend development easier.

What do you like best about the product?

What I like most about Supabase is how quickly it lets you go from an idea to production. The generous free tier and intuitive onboarding make it easy to spin up a fully featured PostgreSQL backend in just a few minutes, which delivers great ROI for both prototypes and apps that need to scale.

The dashboard UI/UX is excellent. The table view and built-in SQL editor keep database management straightforward, and the AI assistant inside the SQL editor saves me a lot of time when I’m drafting more complex queries.

I also lean heavily on its native integrations, from seamless Auth and Storage to Edge Functions and pgvector for AI embeddings. Real-time subscriptions and direct Postgres queries feel fast and rock-solid in day-to-day use.

What do you dislike about the product?

While Supabase is fantastic overall, I’ve run into a few minor pain points.

Project pausing on the free tier: Free projects automatically pause after about a week of inactivity, and the wake-up time can take a minute or two. That’s a bit frustrating when I’m developing intermittently.

Row-Level Security (RLS) learning curve: Writing and debugging more complex RLS policies directly in SQL has a steep learning curve, especially for developers coming from traditional backend ORMs. It’s also easy to get policies wrong in ways that can negatively affect query performance.

Local development and migrations: The CLI works, but keeping local migrations fully in sync with what’s in the cloud dashboard can feel a little clunky compared to dedicated ORM migration tools (like Prisma).

Support: On the free and lower-tier plans, support is largely community-driven (forums/Discord), which can be slower when you’re troubleshooting edge cases.

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

Before Supabase, spinning up a new project meant stitching together several disconnected services: running a standalone PostgreSQL database, integrating third-party auth (like Auth0 or Firebase), configuring S3 buckets for storage, and writing a lot of boilerplate REST APIs.

How it benefits me:
Accelerated time-to-market: Supabase bundles Auth, Database, Storage, and auto-generated APIs in one unified platform. That consolidation cuts my backend development time from weeks to just a couple of hours.
Unified AI stack: Built-in pgvector removes the need for a separate vector database (like Pinecone) for AI/RAG workflows. Being able to store embeddings right alongside relational data in Postgres significantly reduces architectural complexity.
No vendor lock-in: Unlike proprietary BaaS solutions (like Firebase), Supabase is open-source and built on standard PostgreSQL. I still get modern developer conveniences without giving up the ability to export data or run raw SQL queries.
Cost efficiency: Rather than paying for 3–4 separate microservices, everything is consolidated, which translates into huge ROI and lower monthly infrastructure bills.

What do you like best about the product?

Getting a real Postgres database up and running, with auth and auto-generated APIs, takes minutes instead of days. I don’t have to stitch together separate services for login, storage, and the database—it’s all managed in one dashboard, and the realtime subscriptions work right out of the box.

What do you dislike about the product?

Edge Functions can have noticeable cold start delays, which is annoying for anything latency-sensitive. Documentation is solid for the basics but thins out fast once you're doing more advanced Postgres work like custom triggers or row-level security edge cases.

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

We used to spend early project time just wiring up auth, a database, and storage separately before writing any real features. Now that setup takes an afternoon, and the auto-generated APIs mean less boilerplate backend code — we get to the actual product work much faster.

What do you like best about the product?

I love how Supabase helps us store large data in simpler tables and views in normalized tables, making it easier to query complex tables and information or make data requests directly from the app. Its easy-to-use nature is a big plus, and I appreciate how easily it can be integrated with Claude. The UI that lets us view the schema and data directly is incredibly helpful, enabling us to see, cross-verify entries, and find anomalies. The Claude integration allows us to push migrations directly to the database and keep track of them.

What do you dislike about the product?

As I'm working on an app, sometimes external collaborators from different departments need access to analyze the database. The access part seems to cause problems; it may have a reliable option, but it needs more information. In the beginning, the UI took a bit of time to know how it could be leveraged and used properly.

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

I use Supabase to store large data in simpler tables and easily query complex information. Its UI lets us view schema and data directly for cross-verifying entries. The Claude integration helps push database migrations and track them efficiently.

What do you like best about the product?

Easy to use, well integrated with the main AI LLMs, and offered at a very good price. I used Claude and chatGPT connectors and it was fast and easy, works great

What do you dislike about the product?

It’s difficult to use if you don’t have some technical experience.

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

Free, fast and easy database for AI projects with a lot of vibe coding tools

What do you like best about the product?

What I like most about Supabase is that it makes setting up a backend much easier, especially for smaller projects. I like that I can manage the database, authentication, and other backend features in one place instead of setting up everything separately. It saves me a lot of time when I’m working on student projects.

What do you dislike about the product?

The main thing I dislike is that it can take some time to understand all the features when you are new to it. Some of the documentation and setup steps can feel a little confusing at first. I also had to spend some time figuring out how different parts of the backend work together, but once I understood the basics, it became easier to use.

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

Supabase helps me avoid spending too much time setting up backend features from scratch. For my student projects, I can use it for things like storing data and handling user login without having to build all of that myself. This lets me focus more on the actual project and get a working version ready faster.

What do you like best about the product?

What I like most about Supabase is that it gives me most of the backend pieces I need in one place. Setting up a database, authentication, storage, and APIs is pretty straightforward, and I don't have to manage each services separately.

What do you dislike about the product?

The main thing I dislike is that some parts can take a little time to understand when you're getting started. There are quite a few features and setting, so it can feel a bit overwhelming at first, especially when you haven't used supabase before.

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

Supabase saves me time putting the backend services I need in one place. I can set up a database. authentication, storage, and APIs without having to build everything from scratch. This makes it easier to get a project up and running and spend more time working on the actual application.

What do you like best about the product?

What I like most about Supabase is how easy it makes backend development. The database, authentication, storage, and APIs are all in one place, so I can build and manage a project without setting up everything from scratch. It saves a lot of time and keeps things simple.

What do you dislike about the product?

The main thing I dislike is that it can feel a little confusing when you’re just getting started, especially with some of the database and authentication settings. The pricing can also become a concern as a project grows. But overall, I think the pros outweigh the cons.

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

Supabase saves me a lot of time by handling the backend basics like database, authentication, storage, and APIs in one place. I don’t have to build everything from scratch, so I can focus more on the actual product. It makes development faster and easier to manage, especially for smaller projects and quick prototypes.

What do you like best about the product?

What I like about Supabase is how quickly I can get a complete backend up and running without spending too much time on setup or infrastructure. The UI/UX is truly hats off—it's so easy to understand and use that the initial application setup and connecting everything was quick.

Integrations are another strong point, because it works well with the PostgreSQL ecosystem and common frontend frameworks. Performance feels fast and fits what I need for a POC-level application. It’s also been reliable for me; I haven’t noticed any downtime or lost time while using it.

I used the Free Tier plan, and it was surprisingly great. The onboarding process was smooth, and the docs are available when you need them. AI/Intelligence is like the cherry on the cake for Supabase, I would say.

What do you dislike about the product?

Supabase isn’t very stakeholder-friendly. For a POC-level application, it seems fine and generally accepted, but then we’re advised to move to other options like RDS hosting. From what I’ve seen and tested, large and complex queries can be a pain and sometimes perform poorly.

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

Supabase solves the problem of building and maintaining separate backend services by combining authentication, SQL files, APIs, and real-time features in one platform. This cuts down a huge chunk of backend setup and integration work, so I can move from a prototype to a working application much faster, while still keeping the flexibility of PostgreSQL.

What do you like best about the product?

I like how Supabase gives you a lot out of the box, especially the database, authentication, and APIs. It’s quick to set up and makes building and connecting a backend to a project much easier.

What do you dislike about the product?

The free tier is great for getting started, but costs can add up as usage and database requirements grow. Some advanced features also take a bit of time to understand when you're new to Supabase.

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

Supabase removes a lot of the backend setup work, especially for databases, authentication, and APIs. It lets me build and test projects faster without managing as much infrastructure myself.