Live data from Hacker News

Supabase (YC S20) raises $80M Series B

techcrunch.com

121–130 of 130 posts

Re: Supabase (YC S20) raises $80M Series B

#121

Earlier quoted context omitted.

> If I were CEO I would shift all resources to fixing the UI and SDK I'm the CEO :) Thanks for the feedback. I would love to hear any specifics - where you got stuck and which parts of the UI/SDK we can improve. My email is in my profile. We know we have a lot more to do, and we love building based on user feedback.

Congrats, hopefully this means an iOS sdk soon? :D

definitely. We need better mobile support (beyond RN/Expo/Flutter)

Re: Supabase (YC S20) raises $80M Series B

#122
post #31

Earlier quoted context omitted.

Thin Backend ( https://thin.dev/ ) is the newest of all of those. Compared to Hasura it offers a nicer schema designer. Compared to Supabase it offers better end-to-end typesafety and a more higher level API that offers optimistic updates. Prisma is more like an ORM, so it's designed to be used by a handwritten backend.

thin.dev Realtime Bandwidth - $2 per GB yes please, sign me up !!! /s

Update: It's now 1$ per 1M Api calls :) Thanks again for the feedback.

Re: Supabase (YC S20) raises $80M Series B

#123

Earlier quoted context omitted.

> That's a similar approach to supabase. Why reinvent the wheel? Supabase is a copy of Firebase. Same question?

Supabase real time is open source while firebase is not. You cannot provide firebase as part of your services because you cannot self host it. I asked why to understand the reason for another open source implementation.

Point being you can usefully have two or more of the same type of thing, even if their only difference is the quality of the team building them. That's why the market sustains more than one car of each type.

Re: Supabase (YC S20) raises $80M Series B

#124
post #113

Earlier quoted context omitted.

Thank you for this write up - it's extremely actionable. Our team is already chatting about it internally to find some quick wins, and we'll do a deep-dive tomorrow on each of the items you've raised. Some easy ones from me: > RBAC is completely missing We are implementing something here, but we need to find the right level of abstraction for all/most use-cases. It's still unclear to us whether we should make this si…

With regards to authorization – have y'all looked any at Open Policy Agent[1]? I think it could potentially be a good fit for the Supabase stack to implement policies not just in the database but also the gateway and potentially other components as well. It'd be super cool to be able to implement custom policies in rego code that could be re-used in several parts of the stack, and tested/verified/evolved independentl…

We did evaluate OPA recently. For now, we're working with an approach that builds on top of PostgreSQL Row Level Security and functions. That may have a sufficient balance of power, performance and complexity for many of our users. For more complex use cases, OPA may indeed be a good fit and is something we can explore more in the future.

Re: Supabase (YC S20) raises $80M Series B

#126
post #117

I like the approach Supabase takes in being a light abstraction over Postgres and using OSS. Even in light of the following critiques, I feel like its one of the simplest ways for an experienced developer to start a new project, and it's now my go to over spinning up a database, Firebase, ORMs, and other database abstractions. My main critiques are: - As others have said, default security is way too permissive. They…

These are all valid critiques I feel. I would also add something that's currently a pretty glaring hole in the Supabase offering: migrations. Is far as I know there's no good current advice for how to do staged environments and migrating between them with Supabase. Most advice I've seen is to use Prisma (or similar) which means you have to accept having an ORM layer in the stack, or to use a script that really just a…

For me, this is the part where Supabase being purely a Postgres implementation is a real strength. Supabase gives you access to the underlying database directly via a standard Postgres connection, so you can use literally any tool you want for database migrations.

Downside to the direct access being that there's no pretty Web UI for it - but I think that's both a pro and con (it sometimes bothers me how much effort they put into their UI, from an purely opportunity-cost perspective).

Re: Supabase (YC S20) raises $80M Series B

#127

Congrats on the raise and success to date! When you first launched I recall seeing an advertisement for CEO position at Supabase which I thought was surprising for such an early stage startup. It looks like that never eventuated which I am pleased to see. I am curious about the backstory behind seeking an external CEO and then concluding not to?

supabase ceo here, this is news to me!

perhaps you confused it with the ex-founders role? We have a lot of ex-founders on our team - about 20% of the team are entrepreneurs

Re: Supabase (YC S20) raises $80M Series B

#129

Congrats on the raise and success to date! When you first launched I recall seeing an advertisement for CEO position at Supabase which I thought was surprising for such an early stage startup. It looks like that never eventuated which I am pleased to see. I am curious about the backstory behind seeking an external CEO and then concluding not to?

supabase ceo here, this is news to me! perhaps you confused it with the ex-founders role? We have a lot of ex-founders on our team - about 20% of the team are entrepreneurs

Thanks for the reply.

I can't remember the details but did save the link although it no longer works: https://www.linkedin.com/jobs/view/chief-executive-officer-a...

Maybe it was for a different business or something.

Anyway, best of luck for the future!

Re: Supabase (YC S20) raises $80M Series B

#130
post #115

Earlier quoted context omitted.

> I can't stress enough how there is really nothing quite like it out there at the moment For self-hosting, AppWrite serves essentially the same purpose except for that it doesn't force you to use postgres. The only major advantage of supbase at the moment is that they have a functional graphql offering and paid cloud hosting. Whoever finishes OIDC integration first will have my interest.

> doesn't force you to use postgres at supabase we consider this a feature, not a bug. We don't want to provide huge abstractions over a database, because any product that does will inevitably be slower than the database in it's raw state. This is the major difference between supabase and appwrite - and an important one at enterprise-scale. Other than that, I see a lot of developer love for Appwrite and it seems like…

This mirrors my experience. By making the opinionated choice for Postgres it is possible to use e.g functions and triggers to replace a lot of code that would normally live in the backend. It is quite common to come from ORM-land and treat the database as just a dumb tablestore with some keys. Which does not do justice to the incredible featureset of Postgres. All of that makes it possible to avoid writing a lot of boilerplate and was a huge productivity boost for me. YMMV ofc.
Post reply on HN