![Bhagvendra S.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Bhagvendra S.") BS Bhagvendra S. Junior Backend Developer Small-Business (50 or fewer emp.) 8/14/2026 "A Genuine Postgres Backend That Saved Real Setup Time" 4/5 What do you like best about Supabase? What stood out most to me was having access to a real Postgres database rather than a stripped-down abstraction layer. When I needed it, I could write actual SQL, but for day-to-day work the auto-generated APIs and the dashboard covered most of what I was doing, without forcing me to build a backend from scratch. Authentication was also up and running within minutes, which used to take me a full day or more with other approaches. The dashboard made it easy to inspect tables, run queries, and adjust settings without constantly dropping into raw SQL. That was genuinely helpful when I wanted to move quickly while still keeping clear visibility into what was happening in the database. Having realtime updates and file storage in the same platform also meant I wasn’t stitching together three or four separate services just to get a basic app off the ground. Integrating Supabase into my existing stack was fairly painless. It connected well with the frontend frameworks I was using at the time, and I didn’t need to write much glue code to get everything talking to each other properly. Performance held up well for the size of projects I was running: queries stayed responsive, and I didn’t notice any meaningful slowdown as data grew. On pricing, the free tier was generous enough to prototype and validate an idea before committing any money, and the paid tier felt reasonable for what it included once a project needed to move toward production. It gave me confidence that the platform could grow with a project without costs jumping unpredictably early on. I also experimented a bit with AI-assisted schema work, and Supabase handled that reasonably safely. It didn’t feel like a bolt-on feature, but more like something that had been considered as part of the core workflow. Documentation was another strong point. Most issues I ran into had clear explanations and working code examples for the framework I was using, so I rarely stayed stuck for long. Review collected by and hosted on G2.com. What do you dislike about Supabase? Row level security took me longer to feel confident with than I expected. The concept made sense on paper, but writing policies correctly on the first try wasn’t always intuitive. When a policy was misconfigured, it could quietly block requests, and it sometimes took a while to trace the problem back to the real cause. The documentation also felt uneven—some sections were solid, but for certain edge cases I ended up piecing together answers from GitHub issues or community discussions instead of relying on official docs. Support options felt limited once my questions went beyond the basics. There wasn’t any live chat, so anything more involved meant waiting for a ticket response, which slowed things down when I needed a quick answer. I also ran into occasional cold starts on the free tier, especially if a project had been idle for a while, which was a minor but noticeable friction point during testing. Pricing seemed reasonable early on, but I found costs could rise faster than expected once usage increased—particularly around storage and egress. Because of that, keeping an eye on spending became necessary rather than optional. Review collected by and hosted on G2.com. What problems is Supabase solving and how is that benefiting you? Before Supabase, setting up even a basic backend meant provisioning a server, configuring a database, and building authentication from scratch—work that routinely consumed the first several days of any new project before I could even get to the application logic. Supabase streamlined that entire process into something I can have running in minutes: a secure relational database with authentication already working. As a result, I can shift my focus almost immediately to building the product itself instead of spending time on infrastructure. It also addressed the hassle of juggling multiple separate services for things like file storage and realtime updates. Having those capabilities built into the same platform as the database means fewer moving parts to manage and fewer integration points that can break. For smaller projects and prototypes in particular, this lets me go from an idea to something functional in a single sitting, rather than losing the first few days to setup work. That makes it much easier to validate ideas quickly before committing more time or budget. Review collected by and hosted on G2.com. Show More Current UserValidated ReviewerIncentivizedSource: G2 invite See what 190 reviewers think of Supabase 4.6 out of 5 · Verified reviews from real users [ Read all reviews ](https://www.g2.com/products/supabase-supabase/reviews)