Edge Functions are built on the Deno runtime today, but importantly, we operate our own infrastructure and don't depend on Deno's hosted services. While Deno is winding down active development over the next year, the Deno team has committed to contributing bug and security fixes until then. And we'll continue our work with the Deno team to incorporate critical improvements to the Edge Function runtime during this transition.
Our next-generation offering, Compute (https://supabase.com/compute), is already in an advanced stage of development and will support Deno as well as other runtimes like Node.js and Bun. We'll provide a seamless migration path from Edge Functions to Compute. Our goal is to make Compute available for new workloads and existing Edge Functions well before Deno's support window closes.
Existing Edge Functions will continue to be supported, and there's no need to migrate today, and no need to stop writing them. Longer term, Compute will give you more flexibility in choosing your runtime, and we expect it to become the recommended path for new workloads.
We don't have a public timeline to share yet, but we'll provide updates as soon as we do.
yup — we see Turso/SQLite as complementary to Postgres for specific use cases. The blog post doesn't mention it yet, but this will power our smallest instance — "Spark" https://x.com/saltcod/status/2106078176464036044
^ this is exactly the plan. An appropriate stack for each part of your journey.
The blog post captures it really well:
> As agents build more software, we believe database demand will outpace the world’s current capacity to support them. So we need infrastructure that can scale to meet this growth and is suited to how we build with agents.
> Agents should be able to create a database as easily as creating a file, with just as little concern about cost. For smaller workloads, that shouldn’t require provisioning a dedicated machine every time. Databases should be cheap to create, available on demand, and have a clear path to production when needed.
> SQLite is well suited to these small, on-demand workloads. Postgres is what you want as your application scales. We want builders to have the same developer experience from prototyping to production.
Edge Functions are built on the Deno runtime today, but importantly, we operate our own infrastructure and don't depend on Deno's hosted services. While Deno is winding down active development over the next year, the Deno team has committed to contributing bug and security fixes until then. And we'll continue our work with the Deno team to incorporate critical improvements to the Edge Function runtime during this transition.
Our next-generation offering, Compute (https://supabase.com/compute), is already in an advanced stage of development and will support Deno as well as other runtimes like Node.js and Bun. We'll provide a seamless migration path from Edge Functions to Compute. Our goal is to make Compute available for new workloads and existing Edge Functions well before Deno's support window closes.
Existing Edge Functions will continue to be supported, and there's no need to migrate today, and no need to stop writing them. Longer term, Compute will give you more flexibility in choosing your runtime, and we expect it to become the recommended path for new workloads.
We don't have a public timeline to share yet, but we'll provide updates as soon as we do.
reply