SupabaseKong kong/kong:3.9.1 https://hub.docker.com/r/kong/kong bridge bash false --entrypoint=/bin/bash /home/kong/kong-entrypoint.sh http://[IP]:[PORT:8000] Kong is the API gateway used by the official self-hosted Supabase Docker stack. It routes Studio, Auth, REST, GraphQL, Realtime, Storage, and Edge Functions through a single public endpoint. https://github.com/supabase/supabase/issues https://github.com/Kong/kong https://supabase.com/docs/guides/self-hosting/docker https://raw.githubusercontent.com/raccommode/Raccommode-Unraid-Community-Apps/main/templates/supabase-kong.xml https://raw.githubusercontent.com/supabase/supabase/master/packages/common/assets/images/supabase-logo-icon.png Network:Proxy:Management Tools This template runs only the Kong gateway container from the official Supabase Docker Compose stack. It requires the Supabase kong.yml and kong-entrypoint.sh files from supabase/docker/volumes/api mounted below. It does not install Studio, Auth, PostgREST, Realtime, Storage, Edge Runtime, Postgres Meta, or Postgres. Put all Supabase containers on the same custom Docker network and make sure the service hostnames used inside kong.yml, such as studio, auth, rest, realtime, storage, functions, and meta, resolve to the matching containers. Generate new Supabase keys before first use; never keep the example keys. Apache-2.0 8000 8443 /mnt/user/appdata/supabase-kong/kong.yml /mnt/user/appdata/supabase-kong/kong-entrypoint.sh off /usr/local/kong/kong.yml LAST,A,CNAME 1 request-transformer,cors,key-auth,acl,basic-auth,request-termination,ip-restriction,post-function 160k 64 160k /dev/stdout combined supabase