I agree with all of these points. I really enjoy using Supabase, but it does feel like 95% of the effort is on releasing new features. The mentioned migrations

I agree with all of these points. I really enjoy using Supabase, but it does feel like 95% of the effort is on releasing new features. The mentioned migrations for example, don't work if your database is not very simple (e.g. triggers typically won't work because the dependency order is wrong, custom types are not supported, etc.), and this has been the case for some time. The documentation for the most basic functionality is also quite poor and requires digging through the TS source for detail. For example, here's the JS lib auth signInWithPassword function: Log in an existing user with an email and password or phone and password. Requires either an email and password or a phone number and password. Parameters: credentials (required) SignInWithPasswordCredentials [no link to what this is] And an example is given: const { data, error } = await supabase.auth.signInWithPassword({ email: 'example@email.com', password: 'example-password', }) That's all. There is no explanation of what data/error might return, error conditions, whether it can throw, etc. Looking at the source, the are a variety of additional parameters (user meta data, captchaTokens ) that are not mentioned at all. The site has various articles, howtos, videos etc. that explain different bits of functionality, but the core reference is incomplete and it's a pain to dig through blog posts to discover basic functionality. To be clear, I think it's a great product, and the open source aspect and great communication from the team is a big plus, but I do think more time could be spent getting the basic product right before chasing 100s of new features.