Supabase Updates: Compute, Agent-Ready Workflows, and Scaling Infrastructure

What changed?

Supabase announced several new infrastructure features across development and production environments. These include an alpha runtime for running Supabase locally without Docker, support for keeping desired database schemas in Git repositories, the private alpha release of Supabase Compute for running containers and workloads alongside the database, and the introduction of Multigres for highly available Postgres. Supabase also acquired Turso to support its scale-out database ambitions. Edge functions remain available, though some workloads now have dedicated compute options.

Why does it matter to an everyday developer?

These updates lower operational friction in both local development and production. Local development is simplified by removing the Docker dependency, which can speed up setup and reduce compatibility issues. Storing database schema state in Git enables declarative workflows, letting developers—and AI agents—read, modify, or fork schemas alongside application code, making collaboration and rollback clearer. Supabase Compute integrates data storage and compute, so developers can manage application logic and database proximity without configuring and stitching together separate services. Multigres and the Turso acquisition indicate a future focus on highly available, scalable Postgres—useful for both small and large-scale applications.

What can the developer do now?

• Request access to private alphas for Supabase Compute and Multigres to experiment with running compute workloads beside their databases.
• Adopt the new Dockerless local runtime to simplify local Supabase setup and reduce environment configuration.