What's already configured
The one-click deployment clones Supabase's official Docker Compose stack and starts all eleven services: Postgres, the Kong API gateway, GoTrue (Auth), PostgREST, Realtime, Storage, Studio, Edge Functions (Deno), and the Logflare/Vector logging pipeline. Kong sits in front of everything and routes incoming requests to the right internal service, so your REST, GraphQL, and Auth endpoints are reachable through one gateway from the first boot. Automation also generates the JWT secret and the anon/service_role API keys your app needs to connect — you don't create these manually.
First login
Studio, Supabase's admin dashboard, is served through the same Kong gateway and protected by basic authentication using the DASHBOARD_USERNAME and DASHBOARD_PASSWORD values generated during setup.. Once inside Studio, the API settings page shows your project URL and both API keys again, so you don't need to dig through the .env file to connect a client library.
A few practical details
Storage files are written to the server's local disk through a bind mount by default, not to external object storage, so factor that into your backup plan.
Since self-hosted Supabase doesn't send telemetry back to Supabase, you won't see your project inside the Supabase Cloud dashboard — it exists only on your server. If you ever need to reset everything, note that removing containers with a volume-deleting flag wipes your Postgres data permanently.