hey everyone, supabase ceo here. The team is extremely excited about this release.
This one has been a long-time coming. It's one of our most requested features. We spent a long time getting the Developer Experience right - we investigated several approaches (Containers, Isolates, WASM), and eventually landed with Deno.
Big shout-out to the Deno team. Their open source and DX-focused philosophy made it an obvious choice in the end. We've wrapped their open-source runtime to make the Supabase experience as integrated as possible, from the local CLI development, to realtime logs on the Dashboard. Edge Functions are still Experimental, so make sure you send your feedback to make the experience even better.
We'll have a few of the team in the discussion ready to answer any questions.
I have a feeling you may not be able to talk about this, and thats okay. That said, I'm asking anyway.
Did you consider working with CloudFlare? I feel like Supabase is the perfect fill for the "holes" that CloudFlare has in their services, that you guys fill. They don't have two crucial things currently: Persistent Data Store that's accessible outside of its platform, and an Authentication product. They otherwise have everything else and more. Seems like it would have been a very mutual relationship.
Any insights on this one by chance?
I'm loving Supabase, and the only gateway to adoption on my side is the lack of SOC 2 compliance, which I understand is coming. However I don't want to give up best in class services for things like CDN, Storage, Workers etc. I'm kind of an "all in" platform person. I don't want variance in vendors, I want one vendor with variance, if that makes sense.
Don't per se mean I wouldn't use Supabase still, of course! I love the product where I have been able to test it out, and once SOC 2 compliance lands that will clear the final adoption hurdle for me anyway
we're working closely with Cloudflare and really love their products.
We did consider Cloudflare Workers - ultimately it came down to the open source philosophy of the Deno runtime.
It's incredibly important to us that everything in Supabase has "escape hatches" - you can choose to host wherever you want to. I'm certain that Workers will get there eventually, but it's not there yet. We're still big fans and will be doing other neat things with them in the future (also we'll revisit Workers if the runtime becomes an open source).
> lack of SOC 2 compliance
We've chosen the auditor - I believe SOC2 Type I will be around 4 months away (next Launch Week)
> It's incredibly important to us that everything in Supabase has "escape hatches" - you can choose to host wherever you want to
I'm rooting for you guys, not only your tech stack is very solid, but commitment to letting your users self-host if they want to is laudable.
But here's something I don't understand about your offering. Taking a look at the pricing page https://supabase.com/pricing there is only one pricing tier above free but below the scary-looking "contact us for a quote". The idea is that you get a reasonable baseline included and pay for extra storage and bandwidth. Cool.
But it comes with a number of fixed limits that I find puzzling, like 100k monthly active users. On edge functions, they can run 1000 hours (per month?), invoked 2 million times, and there's a limit of 100 functions in total. The customer can't pay a little more to have the limits raised a little further like they could with storage and bandwidth, they need to migrate to the enterprise plan. So I must ask: why is that?
I almost don't care because I'm the kind of person that likes to run their own servers but, I want to support you guys.
You guys are killing it with these product updates, I feel like I'm hearing about them once every few weeks, and I'm not even actively following you. My team is on Firebase right now and I have some mixed feelings about it; will definitely keep you on my radar.
Congratulations on launching this oft requested feature!
Any timelines for support for Functions over QUIC/HTTP3 and raw UDP/TCP?
Cloudflare Workers, the closest thing to Deno Deploy, announced intention to support raw TCP a few months back (while "HTTP3" has been supported for quite a long time now).
Re: Database Functions:
I really like the dual nature of Cloudflare's database offerings:
Durable Objects (run functions close to data) as an option for apps that need that kind of strong consistency guarantees.
KV (move read-only data close to functions) as an option for apps that can tolerate race but desire speed.
> Any timelines for support for Functions over QUIC/HTTP3 and raw UDP/TCP?
I'll ask the Deno team. I'm curious what your use-case is for these (especially UDP)?
> Cloudflare's database offerings
DO and KV are both incredible products. I think we'll tackle these a little differently since our "base" is Postgres. We are announcing more "edge-like" products tomorrow which will lay the groundwork
Have you used Workers KV? In my experience, it's not just eventually consistent but also delayed - often by 10 seconds at least - the data is not updated even for the same client, unless they implement their own caching.
I very much like the idea of automagic edge compute but would like to see the analytics. I am skeptical of the edgey claims, even for cloudflare. Where are the nodes? How do they each tend to respond? I want a map with every node being lit up in real time. I want to be able to test nodes by location etc.
This one has been a long-time coming. It's one of our most requested features. We spent a long time getting the Developer Experience right - we investigated several approaches (Containers, Isolates, WASM), and eventually landed with Deno.
Big shout-out to the Deno team. Their open source and DX-focused philosophy made it an obvious choice in the end. We've wrapped their open-source runtime to make the Supabase experience as integrated as possible, from the local CLI development, to realtime logs on the Dashboard. Edge Functions are still Experimental, so make sure you send your feedback to make the experience even better.
We'll have a few of the team in the discussion ready to answer any questions.