supabase /

Supabase

Live map
View repository
Snapshotmaster · 9be60ca

The self-hosted request plane: one gateway routes auth, REST, realtime, and storage traffic around PostgreSQL.

Click a building or route
Choose a path

Issue a session token through Auth, send it back through REST, and let PostgreSQL enforce the role and policies.

System map8 components · 10 connections
130%
Supabase backend city architectureEvery public request enters through Envoy; follow sign-in and database access together, then compare the storage upload path.HTTP/WS request + apik…signup/login/callback/…users, identities, ses…resource path + filter…translated SQL under a…Envoy APIGatewayAuth / GoTrueApplicationClientPostgRESTObject FilesStorage APIPostgreSQLRealtime
Connections
BuildingsEntryServiceComputeStorageRuntimeToolingExternal

Terms, in plain English

API gatewayA public reverse proxy that authenticates, rewrites, and routes requests to internal services.

How to study this repo

  1. 1
    Read routes before containers

    Start with Envoy's path table so each public URL has a clear internal destination.

  2. 2
    Make PostgreSQL central

    Trace the separate Auth, REST, Realtime, and Storage database roles and what each stores or reads.

  3. 3
    Separate bytes from metadata

    Follow one upload to see why object content and authorization metadata live in different systems.