Supabase

What do you like best about the product?

I like Supabase because it makes backend development very simple for us. Everything I need, like the database, authentication, storage, and APIs, is available in one place, which saves a lot of time and effort of our team. I feel Supabase offers a good value for the price. Having the database, authentication, storage, and APIs in one platform saves development time and reduces the need for multiple services. The pricing feels reasonable for the features and convenience it provides.

What do you dislike about the product?

The learning curve can be a bit steep for beginners, especially when working with advanced database settings. Some features could also have clearer documentation and setup guidance.

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

Supabase reduces the time and effort needed to build and manage a backend. Having the database, authentication, storage, and APIs in one place helps me develop and test applications faster as compared to other applications.

What do you like best about the product?

It’s super simple to use and really well documented. All the main coding AI agents are already connected to it through its MCP, which makes it easy to get started. It streamlines everything around the DB, Auth, and Edge Functions, so I can focus more on building instead of wiring things up.

What do you dislike about the product?

I really wish there were a better, smaller plan option. For personal use, I feel like a $10 USD plan would be ideal.

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

It speeds up development across the board, makes deployments easier, and feels very secure.

What do you like best about the product?

What I like most about Supabase is how quickly I can set up a backend with database, authentication, and APIs in one place. It saves me a lot of setup time, especially when I’m building a project or testing an idea.

What do you dislike about the product?

The pricing can get a little confusing as the project grows, and some features take time to understand properly. I also feel the dashboard can be a bit overwhelming when you’re new to supabase.

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

Supabase saves me from setting up the backend from scratch. Having the database, auth, storage, and APIs in one place makes development faster and lets me focus more on building the actual features.

What do you like best about the product?

I like that underneath it's real PostgreSQL: standard SQL, extensions, and zero vendor lock-in. The REST API and realtime, autogenerated from the schema, save you a lot of backend CRUD. Additionally, authentication with Row Level Security allows access control directly in the database itself.

What do you dislike about the product?

That you can't have different databases and everything has to be in the same one. The bill is difficult to predict with variable loads because the price mixes computation, storage, transfer, and active users. The console falls short for diagnosing slow queries, and schema migrations between environments require more manual work than expected.

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

Eliminates the time of setting up and operating the backend layer. The database, authentication, storage, and functions are already resolved from the start, so the team can focus on the product and not on provisioning Postgres, managing backups, or handling updates. In general, it shortens project startup.

What do you like best about the product?

Depending on your technical knowledge, getting it set up can be a bit challenging. That said, if you have even a basic understanding of AI and MCPs, you can have an AI agent handle most of the setup for you. Performance has been good overall, and everything feels very responsive. The value is just about the same as any other database provider. The pricing matches the value, I think it is dependent on how familiar you are with the technology and your use case.

What do you dislike about the product?

At the moment I don't see any immediate dislikes about Supabase. If anything, there is some barrier to entry because it requires users to have some idea of SQL

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

Currently I am only using it as a Postgres Database. So it serves the immediate benefit of storing my website's data and users' data

What do you like best about the product?

you can spin up a working backend in a few minutes instead of setting everything up yourself.

What do you dislike about the product?

Free projects pause after a week of inactivity, which is annoying when you’re working on something on and off

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

We can start building features much faster instead of spending time on infrastructure.

What do you like best about the product?

supabase makes backend development fast with postgres sql authentication, storage, apis and real time features in one platform

What do you dislike about the product?

Pricing can become expensive as usage grows, and some advanced features require additional configuration and technical knowledge

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

It removes backend complexity, helping me build and launch features faster with less setup and maintenance

What do you like best about the product?

Supabase is one of the easiest backend platforms I’ve used for building and testing applications. I especially like that it provides a PostgreSQL database, authentication, storage, APIs, and other backend features in one place, which makes development much faster.

The UI is clean and easy to navigate, and setting up a database or managing tables is straightforward. The built-in SQL editor is also very useful for quickly creating and testing queries. Supabase integrates well with modern development frameworks, making it convenient to connect the backend with web and mobile applications.

Performance has been reliable for my projects, and the development workflow is much simpler compared with setting up a backend and database from scratch. The free tier is also useful for learning, experimenting, and building smaller projects before moving to a paid plan.

Overall, Supabase has saved me development time and made backend development much more approachable, especially when I want to focus on building the application rather than managing backend infrastructure.

What do you dislike about the product?

One area that could be improved is the learning curve for some of the more advanced features. While the basic interface is easy to use, understanding database security policies, authentication settings, and more advanced configurations can take some time for beginners. More beginner-friendly documentation, examples, and guided setup flows would make these features easier to understand. Pricing can also become a consideration as project usage and resource requirements increase.

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

Before using Supabase, setting up a backend, database, authentication, and APIs separately could take a lot of time and configuration. Supabase brings these services together in one platform, making it much easier to build and test applications quickly. It has reduced the amount of backend setup I need to manage and lets me focus more on developing the actual application. The built-in PostgreSQL database, authentication, APIs, and storage have been especially useful for speeding up development and simplifying project management.

What do you like best about the product?

I use Supabase as a backend-as-a-service to speed up development, and I really appreciate the seamless integration between the Postgres database, authentication, and real-time features. These features allow me to build secure and scalable applications efficiently, letting me focus on building the app's features without worrying about infrastructure. Supabase handles complex tasks like database management, user authentication, and real-time data syncing, which saves me so much time. I find it incredibly valuable that I can push real-time updates to connected clients without managing a complicated socket server, and securing my data is easy with authentication tied directly to database rules. The initial setup was pretty easy and straightforward, and I appreciate the CLI for managing migrations locally. I would definitely recommend Supabase to friends or colleagues, giving it a 10 out of 10.

What do you dislike about the product?

I think one thing that could be improved is the documentation for advanced use cases or complex database migrations. I also find managing very complex queries can sometimes become a bit tricky as the project scales.

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

Supabase speeds up development by handling backend tasks like database management, authentication, and real-time syncing. It allows me to focus on features instead of infrastructure, enabling the creation of secure, scalable applications effortlessly.

Recommendations to others considering the product:

I would definitely recommend Supabase to friends or colleagues, giving it a 10 out of 10.

What do you like best about the product?

I'm not a traditional developer. I run inventory operations for a property management company, and Supabase is the backend behind the internal tools I've built with AI-assisted coding. I have two production projects on it: a multi-stockroom inventory system (products, stock levels, stock movements, supply requests, and orders across four locations with about 57 users company-wide) and a second app handling property data and a company knowledge base with vector search. The fact that it's just Postgres is the best part. I can query my own data directly, row level security lets me control what each user and location can see, and features like pgvector meant I didn't need a separate service when I wanted semantic search over our SOPs. Both projects have stayed healthy with zero babysitting, and the free-to-start pricing made it easy to prove the concept before committing anything.

What do you dislike about the product?

Row level security is powerful but unforgiving when you're not a career developer. Writing the policies is easy; figuring out why a query silently returns nothing because a policy is slightly wrong takes real time. Better debugging visibility into which policy blocked a request would save me hours.

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

Our inventory tracking used to live in spreadsheets, which meant no real-time stock levels, no audit trail on movements, and no clean way for field staff to submit supply requests. Supabase gave me a real database with auth and permissions so I could replace that with an actual application, built and maintained by one person who isn't a software engineer. The benefit is live visibility across stockrooms, a movement history I can trust for loss tracking, and the ability to keep adding tools (like our internal knowledge base) on the same platform instead of buying another SaaS subscription for every problem.