Congrats on the launch!<p>Here's our experience with Supabase at <a href="https://automark.io" rel="nofollow">https://automark.io</a> (Next.js + Supabase).<p>- First of all, Supabase let us launch fast which was amazing. Super powerful Postgres features without the pain of self-hosting (or so we thought).<p>- We started out using their hosted product for both our DB, storage, auth, and functions.<p>- Functions have a critical bug that prevent us from using in development so we decided to move to our own API servers: <a href="https://github.com/supabase/edge-runtime/issues/212">https://github.com/supabase/edge-runtime/issues/212</a><p>- Now, the connection between our API servers and the database was slow (a few hundred ms per query), so we moved to self-hosting Postgres which was pretty painful. We tried to use <a href="https://github.com/supabase/postgres">https://github.com/supabase/postgres</a>, but the documentation was very lacking and we had to make a bunch of modifications to get it to work. After we got it working, it was pretty smooth though - pretty easy to implement backups, etc.<p>- Our latest issue has been around auth where the cookie name options change. We've spent hours debugging random cookie issues deep in the auth framework (they finally released `@supabase/ssr` which is pretty decent, but we're still thinking about moving to handling auth on our side so we know and can debug the logic).<p>One thing to mention: although our requirements didn't quite fit Supabase and we ran into these issues, we weren't locked into their hosting. We were able to completely move off of it over the course of a few weeks, but continue using the self-hosted version. This is a huge benefit over something like Firebase or Amplify. We're pretty satisfied with Supabase as an open source project, but not as satisfied with Supabase hosting.
hey hn, supabase ceo here<p>we just announced GA, after ~4 years of beta. for those who don't know: supabase is a postgres hosting company. we also host other open source "backend" tools that make it easy to get started with postgres (tools like PostgREST for auto-generate APIs [0])<p>we owe a lot to the HN community. you launched us 4 years ago [1], when we were just a few developers. since then HN has been a staple in our journey, one of the best sources of product feedback [2]<p>the GA badge is mostly to signify organizational readiness. we're at a stage where we can take any profile of customer. we have a support team that works 24/7, and a success team that will help customers improve their postgres usage. we released our Index Advisor [3] yesterday, and we'll be releasing a few more products this week that helps customer with performance and security.<p>on a personal note: i read HN most days, and love going through the ShowHN's to see what devs are building. thanks for being an awesome community and my favorite place to lurk on the internet. i'll stick around to answer any questions<p>[0] PostgREST: <a href="https://postgrest.org" rel="nofollow">https://postgrest.org</a><p>[1] Launch: <a href="https://news.ycombinator.com/item?id=23319901">https://news.ycombinator.com/item?id=23319901</a><p>[2] HN journey: <a href="https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=supabase&sort=byPopularity&type=story" rel="nofollow">https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...</a><p>[3] Index Advisor: <a href="https://news.ycombinator.com/item?id=40028111">https://news.ycombinator.com/item?id=40028111</a>
Congrats Supabase folks! I wish you every success.<p>I paid $20/mo for a while because of the free tier storage cutoff (500 MB), but have since stopped. I wish you had a $5/mo tier for "small projects" folks who need a database larger than that.<p>For example, Cloudflare's Workers Paid is $5 for D1 databases up to 10GB, with 5GB included and 75¢GB after. I know this is comparing apples and oranges to some degree and that your business model may be incompatible with this use case, which is absolutely fair.
I built a toy app using this, with a front-end only app and postgrest + RBS. The app was seriously two forms behind a login. It was a huge pain.<p>RBS is "insecure by default" meaning if you don't set it up right, all users can access all data. And, because it's SQL, it's really easy to write a valid and successful configuration that doesn't work. You have to test it. And for views, you have to do some real heroics to get them to respect RBS.<p>PostGREST is very very basic and far less powerful than just writing SQL. I found it pretty frustrating to use, knowing that SQL would be far simpler.<p>Yes, I know that I could make a direct SQL connection to the database, but at that point, it would've been easier to put a Rails app on Heroku and use their offering, which is far more mature.<p>The Supabase dev environment was pretty slick and worked well, though I had to docker implode a couple times.<p>I wish them luck, but I could not figure out what the use case was for their product, given that Heroku has an awesome managed Postgres and RDS is there if you have more knowledge and want more controls. I don't see how you could make a complex app that is front-end only with Supabase as your entire back-end.
This is not a negative statement against Supabase, but heed my warning:<p>Do not build out your MVP on supabase. If you need to scale and want a MSP do it after the MVP. Detangling the lock in is not fun.<p>Everything offered by supabase is easily found elsewhere without the MSP lock in.
They seem to heavily invest in their social media presence with things like the YouTube channel, but then also use social media indicators (likes/follows/subs/etc) as a measure of success. Seems a little circular.<p>The plot of Github Stars over Time: Supabase vs. MongoDB seems particularly silly (imo).<p>Not a hater by the way, I think their YouTube channel is actually pretty good, and I think it will become increasingly common for startups/businesses to have something like this for product/brand awareness, getting users up and running, etc.<p>I think if the goal of the post was focusing on platform maturation and growth, it might have been better to focus exclusively on the plots of database/users over time, and simply link out to the various social channels.<p>Overall though still cool to see, and congratulations to the Supabase team!
Awesome, the Index Advisor sped my slowest query 4x! Is there a way to run that across all queries in pg_stat_statements at once or do I need to click on each one?
Happy Supabase user here, albeit on a tiny app I work on in my spare time. So no comment for larger or more complex orgs.<p>That being said, the Swift documentation could use some love. It’s not terrible but it’s also not great. There have been a number of times when I wanted to do something, ended up reading about it on the Supabase JS documentation, and then thought “well I assume it’s roughly the same in the Swift library.” It worked, but a pain to have to guess a lot.
I've been trying out Supabase for an MVP but while the hosted postgres part is quite nice, the C# SDK recommended (but not maintained) by Supabase falls quite short, leaving me to trace down all sorts of obscure issues that turn out to be a 2-year-old bug in the SDK that's still not fixed. It is kind of nice for a community effort but definitely not good enough at all for professional adaptation by .NET developers.<p>On paper, Supabase really has all the ingredients I should need to make my application. In practice, I still end up struggling a lot with the development model. I wish there was an easier, safer way to create RLS rules that doesn't need me knowing (to me) obscure Postgres syntax. This is especially grating since the rest of the tooling seems to try to take me away from SQL a lot by using Postgrest.
Interesting how they posted a self-host guide just a few hours before announcing this. <a href="https://www.youtube.com/watch?v=FqiQKRKsfZE" rel="nofollow">https://www.youtube.com/watch?v=FqiQKRKsfZE</a>
Perhaps expecting criticism and preemptively creating a response that shuts people down?<p>Ultimately I just see the same pattern in Supabase as in many of these "easy scaling" solutions: lock in.
I think the future is something like those platforms are offering but we're definitely not there yet.
Also it's not like I'm an old person refusing to accept new tech. I'm young and looking to create things but I recognize that these services are (currently) doing the complete opposite of giving me freedom.
I like supabase very much, but their network latency in China is too high. I have tried nodes in Singapore and Tokyo. It doesn't matter as a personal blog, but I can't consider it for business purposes. I had to host it myself on Alibaba Cloud, but I had to face many complexities. I like the simplicity of supabase. Maybe, when will they be able to host within China?
Curious to see how many of those million databases are from free users.<p>Feels like we're living in the golden age of free platform offerings.<p>Wonder when the shoe will drop.
I'm not supabase client, so I guess my wishes do not matter much, but I'm self-hosting it and the experience was not pleasant. They just gave me some huge docker-compose with barely any documentation about it and that's about it. My approach to self-hosting software is carefully learn about every service I'm going to run, disabling everything not needed for my use-case. That was not possible with supabase without significant time investments.<p>So my wish would be for supabase to provide some kind of minimal bare-bones configuration and careful documentation for their monstrous docker-compose configuration with explanations why all parameters were set to non-default values. I don't think that I need all those services if I don't use any of them except database and sometimes admin UI.<p>Also I think that I even had to edit some configs for api keys or something like that. It should not be like that, everything should be passed down via envs.<p>Right now I've set up supabase for our developers but asked them to migrate to plain postgres as soon as possible, so I could move production workloads to our standard setup.<p>My ideal setup would be one postgres instance which I can install myself from plain docker library image; one golang binary which embeds everything supabase offers turned off but with some envs to enable and that's about it.
I'm a full stack developer and still don't know what supabase does other than being a firebase replacement...<p>Like seriously are they seriously trying to sell us how difficult is to setup a simple nginx server? Not sarcastic just an old developer that hasn't get this new fad of going "serverless".
Supabase is great - I use them now and they and would be my choice for a new project today - but I have to say I am not a huge fan of how they communicated the whole auth-helpers and ssr situation, and I am not the only one with this comment by a long shot. This is, I think, a part of wider issues with their documentation; it seems like whoever's doing documentation at Supabase is intelligent but stretched thin. Particularly for Sveltekit, the documentation and examples are incomplete, there isn't any guide to migration or how to modify your code, and if you Google things or follow any links or examples you quickly end up in a web of deprecated repositories where it's unclear what to do next or replace them with. One example: <a href="https://github.com/supabase-community/auth-ui">https://github.com/supabase-community/auth-ui</a><p>If you produce a product for developers, you really need to have 1) quality, readable documentation with an introduction that noobs and pros alike can follow, 2) multiple complete, cloneable examples on how to integrate and use your product in several different libraries, 3) obvious migration guides and timelines whenever you deprecate something. Supabase lacks all three, which is extremely frustrating and means there's always a giant caveat when I recommend them. They're still the best, it's a very powerful and impressive product, and the possibility of self-hosting is amazing.
I have to say, I tried it but at that time the self hosted offering was too limited, and the good stuff, the useful stuff was behind the cloud subscription paywall.<p>The initial experience was easy to get going, but the devil was in the details.
Much of the logic should be server side also for security reasons and that wasn't possible when I tried it.<p>People like to hype things that are easy to get started with but don't go much further so the initial impression remains.<p>I think the appeal is to people who like doing frontend but don't like doing backend.