A local Supabase project per agent, with or without Docker

Supabase CLI v2.119.0 introduces an experimental local development engine that allows multiple isolated Supabase projects to run simultaneously across Git worktrees, giving coding agents separate databases, services, ports, and credentials without manual coordination. Projects can start only the services they need, reducing startup times, download sizes, and idle memory use substantially, while a native runtime enables all 13 Supabase services to run as local processes without Docker on supported Linux and Apple Silicon macOS systems. Docker remains the default and is recommended for multiple projects on one laptop, whereas the native runtime is aimed at individual sandbox or CI environments. Remote branches created for pull requests now inherit relevant project configuration and deployed Edge Functions while excluding secrets and production data by default, reducing median readiness time from 102 seconds to 21 seconds. Users can enable the experimental stack through an environment variable or configuration setting, while branch performance improvements are already available to all projects.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.