I've relied on Supabase quite a bit over the last couple of years, but I haven't seriously compared it with other backend options. For a new website, how does Supabase compare with alternatives like Firebase, a managed PostgreSQL database, SQLite, or Cloudflare D1? What are the main trade-offs, and would you recommend exploring a different solution before starting?
4 Answers
If the site only needs a small, lightweight database, SQLite can be perfectly adequate and easy to operate. Cloudflare D1 is another option worth considering for relatively simple applications, especially if the rest of the project already runs on Cloudflare. The important question is whether you need built-in authentication, realtime updates, storage, or easy scaling.
Supabase is essentially PostgreSQL plus a convenient set of extras, including authentication, APIs, storage, and realtime features. If you already like its workflow, there may not be a strong reason to switch. A different option makes more sense if you need a specific feature, want tighter control over hosting, or are trying to reduce platform dependencies.
One drawback some people run into with hosted free tiers is inactivity-based pausing. That can be annoying for a low-traffic project because the first request after a quiet period may be delayed. Self-hosting SQLite or PostgreSQL avoids that particular behavior, but puts maintenance and backups on you.
For a lot of projects, plain PostgreSQL is the simplest choice. You can run it on a VPS or use a managed database service, and you avoid being tied to a larger backend platform. The trade-off is that you have to handle authentication, backups, updates, scaling, and other services yourself.
That’s how I see it too: the database itself is familiar PostgreSQL, while Supabase mainly saves time by bundling the surrounding services.