Supabase is pretty supa
Use Cases and Deployment Scope
We used Supabase to get a backend up quickly for multiple different full-stack projects in development, and continued using Supabase in production. It gave us a way to have lots of features out of the box for a postgresql database, and scalability was clear.
Pros
- Getting up and running quickly and cheaply
- Edge functions
- Flexibility with login options
- Data GUI
- Settings GUI
Cons
- The policies preventing turning off a server are nonsense
- On a lower pricing tier, reaching a usage limit can prevent setting modification to go back under that usage limit
- It's still in beta, so use in production can be problematic at times
Return on Investment
- Gave us a scalable system to reduce a client's backend costs by over 75%
- Allowed us to get a custom backend up for an internal plugin in half the time we originally expected
Usability
Alternatives Considered
MySQL and Apache CouchDB
