Is it possible to self-host Supabase inside a Hugging Face Docker Space?

[Trinai308]

Has anyone successfully deployed self-hosted Supabase onto a Hugging Face Docker Space?

Since Supabase uses docker-compose to orchestrate multiple microservices (PostgreSQL, GoTrue, PostgREST, Kong, etc.), and Hugging Face Docker Spaces typically run a single container exposed on port 7860, is there a recommended workaround or supervisor pattern to run this stack?

[StealthTensor]

While technically possible using a multi-service container approach (e.g., using supervisord or systemd inside a custom Dockerfile to manage PostgreSQL and Kong, then binding Kong to port 7860), it isn't practical or recommended for a few key reasons:

1. Architecture Complexity: Supabase relies on multiple distinct microservices that are best kept isolated via docker-compose.
2. Storage Persistence: Free Hugging Face Spaces use ephemeral storage, meaning database state will reset whenever the container restarts unless you attach paid persistent volumes.
3. Resource Limits: Running Postgres, GoTrue, Realtime, and PostgREST in a single free container easily exceeds memory limits.

Recommended Alternative: Host your database on Supabase Cloud (or a VPS/Hetzner instance running docker-compose), and host your application frontend/API on Hugging Face Spaces while connecting remotely to the database using environment variables.