Supabase

What do you like best about the product?

I really enjoy that Supabase is free, and even with the free tier, I can do a lot. When I need more features, they're available at a reasonable price. The performance is really good. Supabase integrates well with my Git repositories and works really well with cloud services. I also appreciate the stability, the ease of use of the UI, and using the SQL query editor. Overall, these features make my experience with Supabase quite positive.

What do you dislike about the product?

Sometimes it's little slow

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

Supabase solves my problem of storing and accessing around 10,000 MCQs, making them easily accessible instead of being stuck on my local computer.

What do you like best about the product?

I appreciate that Supabase provides a ready-to-use backend along with the database, so I don't have to deal with authentication or API development at all. I like how it helps me develop projects pretty fast and covers almost everything related to the backend on the go. It's pretty convenient for my personal projects.

What do you dislike about the product?

I think the initial user interaction wasn't very smooth for me. Since I know how backend systems work under the hood, it was hard to understand how and where Supabase is handling everything. I wasn't sure if my infrastructure was safe or what additional steps I needed to take. Grasping exactly what Supabase covers was initially challenging, and I found the setup to be moderate to hard.

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

Supabase provides a ready-to-use backend with authentication and API development handled, making project development faster and covering most backend needs.

What do you like best about the product?

Supabase combines a managed PostgreSQL database, authentication, file storage, APIs, and security policies in one platform. This allowed us to build RentFlow without operating separate infrastructure for each backend function.

PostgreSQL provides a strong relational foundation for managing properties, units, landlords, tenants, leases, maintenance records, vendors, payments, expenses, and portfolio reporting. Supabase Authentication supports our passwordless magic-link login flow, while private Storage buckets help us protect documents and inspection evidence.

Row Level Security is another important strength. It allows access rules to be enforced close to the data, which is essential for separating landlord, tenant, team-member, and administrative information.

What do you dislike about the product?

Authentication configuration requires careful attention when an application uses Production domains and multiple Preview deployments. Redirect URLs, site URLs, email links, and environment variables must all agree. A small mismatch can send users to the wrong environment or cause login problems.

Row Level Security is powerful, but it has a learning curve. Policies must be designed and tested carefully because an incorrect rule can either block legitimate access or expose more data than intended.

Database migrations and environment consistency also require discipline. Developers need a clear process for applying schema changes to Preview and Production and verifying that policies, functions, and storage settings remain synchronized.

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

Supabase provides the primary backend for RentFlow. It stores relational product data, manages user authentication, enforces data-access rules, and protects uploaded files.

Using one managed platform for these capabilities has reduced infrastructure work and allowed more time to be spent on product development. PostgreSQL also gives us the flexibility to build advanced portfolio reports and operational features without moving data between unrelated services.

What do you like best about the product?

Honestly, the best thing for me is how easy it is to get started. I can set up a proper database, authentication, storage, and even real time features in around 10 minutes. I don’t have to spend hours setting up servers or messing around with complicated configurations. Most of it just works, so I can spend more time actually building the product instead of getting stuck on backend setup.

What do you dislike about the product?

The main thing that bothers me is the pricing once you start scaling. The free tier is honestly pretty good for getting started, but once your project starts growing and you need more resources, the cost can go up pretty quickly. The dashboard can also feel a little clunky at times, and some of the advanced features still seem like they need a bit more work compared to more mature platforms. Nothing that would stop me from using it, but these are definitely things I’ve noticed.

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

It saves me from having to build and manage the whole backend myself. Earlier, whenever I started a Django project, I had to spend quite a bit of time setting up things like authentication, the database, storage, etc. With Supabase, I can get a Postgres database, auth, and storage running pretty quickly. It does a lot of what I’d normally set up with Django, but with much less initial work. So instead of spending most of my time on backend setup, I can get straight into building the actual product.

What do you like best about the product?

Supabase completely streamlines full-stack development by removing the friction of setting up and managing backend infrastructure. As a designer, the auto-generated REST and GraphQL APIs, paired with real-time database subscriptions, let me prototype and test dynamic, data-driven interfaces instantly without waiting on backend dependencies. The built-in authentication and Row Level Security (RLS) make handling user roles and data access straightforward, while the clean, developer-friendly dashboard UI simplifies managing tables and storage policies.

What do you dislike about the product?

Supabase does make it easier to get a backend up and running, but working with more complex database schemas and handling migrations can still be difficult. I also find that leaning heavily on Supabase-specific features, such as Row Level Security, can lead to vendor lock-in. On top of that, pricing can climb fast when usage increases or when there are sudden spikes in connections.

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

As a designer working on full-stack projects, I often struggled with setting up complex backend infrastructure and handling user authentication. Supabase addressed this by offering instant, auto-generated APIs, built-in Row Level Security, and an intuitive dashboard UI. With those pieces in place, I can avoid a lot of backend overhead and focus on rapidly prototyping, testing dynamic UI interfaces, and shipping new features much faster.

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