Supabase Self-Hosted Fork: Envoy Replaces Kong as API Gateway in Docker Compose

A new pull request for Supabase's open-source platform introduces a significant architectural shift for self-hosted deployments. The proposal adds Envoy as an optional, drop-in replacement for the Kong API gateway within the official Docker Compose setup. This move directly addresses a growing divergence between the self-hosted and managed Supabase cloud environments, where Envoy is already the standard.

The change is framed as a response to concerns over Kong's long-term viability in its open-source form and the operational gap it creates. The PR adds a new `docker-compose.envoy.yml` override file. By running a specific two-file Docker Compose command, users can disable the Kong service and spin up an `api-gw` service using the official `envoyproxy/envoy` image instead, effectively aligning the local stack with Supabase's production infrastructure.

This technical fork signals internal pressure to consolidate tooling and reduce maintenance overhead across deployment models. For the open-source community, it offers a path to a more consistent and potentially more sustainable gateway layer. The opt-in nature suggests a cautious, phased transition, allowing users to test the Envoy integration before a potential future deprecation of Kong in the self-hosted toolkit.