Supabase

What do you like best about the product?

It simplifies full-stack development by providing open source Backend-as-a-Service. Excellent documentation makes it easy to implement and integrate with the application. Strong row level security and seamless integration with Next.js make it an ideal choice for full-stack development.

What do you dislike about the product?

For huge projects, more advanced analytics tools would be a big improvement so deeper monitoring can be done. That said, overall it’s an excellent platform for application development. The free tier is generous, but costs can rise quickly as projects scale , especially for database compute, storage, bandwidth, and Edge Functions. More predictable pricing and clearer cost visibility would make Supabase even more appealing for growing applications.

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

Managing backend infrastructure used to be one of my biggest challenges, and Supabase has largely solved that for me. Rather than spending time setting up databases, authentication, file storage, APIs, real-time messaging, and server infrastructure as separate pieces, I can access all of these capabilities in one platform. As a result, I’m able to focus more on building product features instead of getting stuck in backend boilerplate.

What do you like best about the product?

I use Supabase as the backend for the SmartFarm cloud SaaS platform, and I find it incredibly beneficial for managing the PostgreSQL database, user authentication, real-time data sync, file storage, and REST APIs. It significantly accelerates development by eliminating the need to build custom backend infrastructure. The seamless integration with React and Vite allows me to focus on developing features rather than infrastructure. I especially appreciate the managed PostgreSQL database, built-in authentication, real-time capabilities, and auto-generated REST APIs, which bring everything into a single platform. The PostgreSQL foundation provides the flexibility of SQL, while the real-time features and automatic APIs speed up development. Built-in authentication saves considerable development time with user registration, password reset, login, and session management. Real-time capabilities are great for dashboards and monitoring, and auto-generated REST APIs eliminate back-end API development work, accelerating front-end development. The initial setup was easy, allowing me to connect my React and Vite applications and start using the PostgreSQL database and APIs quickly.

What do you dislike about the product?

Overall, my experience with Supabase is positive. But, I'd like to see more advanced monitoring and performance analytics, and more visual tools for analyzing complex databases and APIs. It already offers an excellent balance of simplicity, but some things can add more value. For monitoring, I'd like to see centralized dashboards that provide real-time insights into database health, API request volume, etc. For performance analytics, I'd like to see the identification of slow SQL queries and inefficient database operations. In visual management, I'd like to see drag-and-drop relationship editing.

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

Supabase accelerates development by managing the backend infrastructure, real-time updates, and seamless integration with React and Vite. It simplifies user authentication and provides automatic REST APIs, saving time and focusing on business solutions rather than backend management, making data-driven app development easier.

What do you like best about the product?

Supabase gives you a full, production-ready PostgreSQL database.

What do you dislike about the product?

This is Supabase's biggest weakness for mobile developers.

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

Because it is open-source, you can host Supabase on your own infrastructure using Docker. If you ever need to migrate, your data is in a standard Postgres database, making export simple.

What do you like best about the product?

It’s very good for creating a database, and its security is also strong and reliable.

What do you dislike about the product?

It’s too expensive, and the databases get paused if the user doesn’t open them for up to a month. After that, the user has to resume them.

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

It’s very easy to connect endpoints using an API key and authorization keys, and to link the software to a database.

What do you like best about the product?

I like how Supabase makes decoding easy. The ability to create rules and tables just by typing some lines of code is a super feature. The coding aspect and features are very smooth, especially for SQL creations like tables and queries. I enjoy using it to store data because it's very accurate. The feature where you can copy and paste into the query section is great; it saves me from having to type everything manually. This has been especially helpful during large projects. Supabase's setup is super user-friendly, there’s no stress, and the language used is understandable. It's the first database product I use, and I'm enjoying it without any thought of switching. The initial setup was very easy, and that's why I enjoy using it.

What do you dislike about the product?

I feel like there should be an AI assistant that can easily create a code for you to paste on your query section without thinking about the code to type. It should have the ability to create code for the SQL query section, maybe for creation of tables, rows, and columns. I don't want to think of a code to type myself.

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

I use Supabase to store user data accurately, eliminating the need for users to log in multiple times. The coding features make it easy to create tables with minimal typing, boosting efficiency in managing large projects.

What do you like best about the product?

I started using Supabase four months ago and my experience has been peaceful. I appreciate that when I was using Google Sheets, it failed due to API calls, but with Supabase to maintain my database for my agents, I haven’t experienced any failures with API calls or PostgreSQL queries. I like that Supabase is easy to use and makes importing and exporting my previous databases simple. The AI support is fantastic for running queries without needing to know SQL. Switching my data from Google Sheets to Supabase was quick, taking just 2-3 minutes. Even the free version of Supabase provides good features and AI support, allowing users to try and test the platform.

What do you dislike about the product?

As of now i dont know but surely when i will dislike any feature i will surely let them know

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

I have no failures with Supabase for API calls or Postgres queries like I did with Google Sheets. Importing, exporting, and AI chat for queries make it easy, even for non-experts.

What do you like best about the product?

I appreciate how Supabase allows for a persistent database and makes SQL queries very easy. The ease of connection and the visibility of the database are fantastic, helping me understand how efficient or complicated it is. I like how easily it's integrated; having never used a database before, it made the process simple and taught me a lot. The integration is almost automatic, and the secure features are helpful. From start to finish, Supabase walked me through the process, making the initial setup very easy. It's well-made, and I've enjoyed learning and using it for my projects.

What do you dislike about the product?

I think the free version, when it turns off by itself, kinda dampens it. You know, because sometimes I wanna take a break, but I don't wanna have to pay for a subscription. It makes you feel less than important about it. Nothing crazy.

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

Supabase gives me a persistent database with easy SQL queries and simple integration. It's user-friendly, helping me understand database workings from scratch. However, the free version shutting down by itself can be inconvenient when taking breaks.

What do you like best about the product?

The Data APIs are especially useful in parts of the product where the client can work directly with well-defined data. Supabase generates REST and GraphQL APIs over the exposed schema, which eliminates a lot of repetitive backend code for lists, user settings, and other straightforward CRUD operations. The key decision isn’t whether an API can be generated; it’s which tables and functions should be exposed in the first place. Since April 2026, new tables are no longer exposed automatically through the Data APIs and GraphQL, so we now have to make that choice explicitly. That feels like a healthier default because it pushes the team to think about the public surface area, rather than treating the entire schema as client-ready. Row Level Security is where the platform becomes both more powerful and more dangerous. We use RLS policies to enforce rules such as users only reading records from their organization, tenant administrators managing shared resources, and individuals updating only their own profiles. When the policies are designed properly, authorization stays close to the data and applies consistently whether the request comes from the frontend, REST, GraphQL, or a Realtime subscription. The documentation has been another positive point. There are specific references for C#, PostgreSQL guides, security, Storage, Auth, Branching, Edge Functions, CLI and troubleshooting.

What do you dislike about the product?

RLS is a major advantage, but it’s not something I’d ever let someone improvise in the final hour of a sprint. A poorly designed policy can lock out legitimate users, and an even worse one can quietly expose records that should never cross tenant boundaries.

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

A collaboration feature we built for a client needed organizations, projects, private documents, real-time comments, and distinct permissions for administrators, members, and external users. In our first pass, we pushed almost all authorization into ASP.NET Core controllers, and we quickly started duplicating the same rules across the API and the frontend. We then reorganized our schema in Supabase Postgres, added foreign keys and constraints around organization membership, and moved the baseline read/write rules into Row Level Security. Transactional logic and domain-level decisions stayed in our .NET service with EF Core, where they were easier to test and keep aligned with the rest of the application. Private documents went into Supabase Storage with signed URLs, comments used Realtime to keep the interface updated, and an Edge Function handled only one job: validating an external webhook before forwarding it to our backend. The initial migration worked locally, but a Preview Branch with seeded data exposed a gap. Invited users didn’t yet have an active membership record, so the new policy blocked them entirely. We introduced an intermediate membership state, fixed the tests, and reviewed the migration diff before merging. After release, Unified Logs helped us trace a request that authenticated correctly but failed at RLS, which the frontend surfaced as a generic loading error. Overall, Supabase reduced the infrastructure we had to build, gave us a shared layer for authentication, data, files, and real-time updates, and made authorization more consistent across clients—without forcing us to move our domain model or critical business processes out of our .NET architecture.

What do you like best about the product?

What I like best about Supabase is how it provides a complete backend platform with PostgreSQL, authentication, storage, real-time APIs, and edge functions in a single, developer-friendly solution. The setup is straightforward, the documentation is excellent, and the dashboard makes it easy to manage databases, users, and application resources. I also appreciate its open-source approach, seamless integrations, and strong developer experience, which significantly reduce backend development time. Overall, Supabase enables rapid application development, simplifies infrastructure management, and allows developers to focus more on building features rather than backend boilerplate.

What do you dislike about the product?

One area where Supabase could improve is offering more advanced monitoring, performance analytics, and database optimization tools for large-scale production applications. While the platform is easy to use and feature-rich, managing complex projects with multiple services can occasionally require additional configuration and careful resource planning. I'd also like to see more granular access controls, expanded observability features, and richer debugging tools for serverless functions and real-time applications. Overall, the experience has been very positive, but enhanced monitoring, deeper customization, and improved enterprise management capabilities would make Supabase even more powerful.

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

Supabase solves the challenge of building and managing application backends by providing a fully integrated platform with PostgreSQL databases, authentication, storage, real-time APIs, and serverless functions. Instead of configuring and maintaining multiple backend services separately, developers can manage everything from a single platform with minimal setup. This significantly reduces development time, simplifies infrastructure management, and accelerates application delivery. As a result, it has improved productivity, streamlined backend development, reduced operational overhead, and allowed me to focus more on building application features rather than backend infrastructure.

What do you like best about the product?

The best thing I like about this Supabase platform is how quickly we can set up our back-end side of an application or rather than separately configuring a database and authentication along with storage and APIs. This platform also brings most of these core pieces into a single ecosystem and its foundation is a big advantage for us because it feels more flexible and familiar compared with no code style backend tools. The dashboard is also very helpful for managing tables and running SQL, and configuring authentication without constantly switching between multiple services.

What do you dislike about the product?

Some areas can feel slightly technical for beginners at the beginning, especially when dealing with role-level security and database policies and other production-level configurations. The platform is easy to start with but using it properly in a secure and scalable way requires some understanding of PostgreSQL and backend architecture. Also, the project becomes more complex when the documentation examples are important because some small configuration mistakes can affect the authentication or API access as well.

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

This platform helped us by reducing the time required to build and manage the back end of web or even mobile applications, especially it is very useful for our startup, solo builders and teams building MVPs or even modern web pages. I also like how useful their internal tools and SAS product for AI-based applications are, where our team want to move fast without even spending too much time or infrastructure setup, which overall reduced our dependency on multiple backend tools because many core services are available in a single platform.