Part 6 — Two instances

Part 6 of 7 — Self-hosting Supabase: a learning journey Supabase's free tier gives you two active projects. I was already using both. Adding a second instance to the self-hosted cluster was not about needing more capacity, it was about understanding isolation. When Supabase runs two projects on the same infrastructure, how does it keep them separate? This post answers that question by actually doing it. What isolation means here When I say the two projects are isolated, I mean: Network isolation. Each project has its own Docker overlay network. In the compose file you write internal: as the network name, but when you deploy with docker stack deploy ... project1 , Swarm automatically prefixes it with the stack name. The network becomes project1_internal at runtime. Services in project1 cannot reach services in project2 at the network layer, even though both compose files define a network called internal . Data isolation. Each project has its own Postgres container with its own volume. T