Supabase (YC S20) raises $80M Series B
I like the approach Supabase takes in being a light abstraction over Postgres and using OSS.<p>Even in light of the following critiques, I feel like its one of the simplest ways for an <i>experienced</i> developer to start a new project, and it&#x27;s now my go to over spinning up a database, Firebase, ORMs, and other database abstractions.<p>My main critiques are:<p>- As others have said, default security is way too permissive. They should lock everything down by default. At some point, this is going to cause major problems for some company that decides to build off Supabase.<p>- Although they have row-level security, RBAC is completely missing. It&#x27;s not hard to implement yourself through stored procedures and triggers (they have an example repo to copy from), but I don&#x27;t see a lot of junior devs doing this.<p>- Stored procedures are more likely to be utilized in the Supabase paradigm, but I haven&#x27;t felt like they have done much to address the inherent weakness and common critiques of using sprocs instead of application level functions.<p>- Escape hatches are missing in their fork of GoTrue (why did they fork it in the first place - now there are two competing versions?). It&#x27;s still not clear to me how to add data to the JWT or get access to the JWT through their SDK.<p>- Slow dashboard with rendering problems. It doesn&#x27;t render correctly on my Fedora laptop. And the slow speed becomes pretty annoying almost right away.<p>- I have experienced data loss when using their SQL editor. So now I copy all the SQL I write to a local file or just do everything through DBeaver.<p>- Lack of backups on the free tier. They should give this away for free up to a storage limit. Backups are a critical part of development and I don&#x27;t have full trust in Supabase given that I&#x27;ve already experienced data loss through their UI.<p>- Misleading marketing. They make implicit claims all over the place on what they offer but then have disclaimers on their code bases about certain features not being production ready.<p>They clearly have work ahead of them, but I&#x27;m optimistic about the potential for Supabase and I look forward to the improvements!