Supabase VPS hosting.

Order a VPS, open the Apps tab in your panel and choose Supabase. Coolify deploys the full stack (Postgres, Auth, REST API, Realtime, Storage and Studio) and shows the credentials in the panel. You keep full root access over SSH, so you can still adjust the Docker Compose setup or the Postgres config whenever you need to. Read the one-click apps guide

• No manual Docker Compose session needed
• Studio login and API keys appear in the panel
• With ZapX Pass, the ZapX AI Agent can prepare the install from a chat prompt

Supabase starts several services at once, and the Coolify panel itself needs about 2 GB RAM. For development and hobby projects an entry package from 4 GB RAM is a workable start. For production with real traffic, Realtime and Storage, plan more RAM and vCores. You can move to a bigger package later or set vCores, RAM and NVMe storage yourself in the configurator.

• Dev and hobby projects: entry package from 4 GB RAM
• Production: more RAM for Postgres and Realtime
• Custom configuration with up to 2 TB NVMe storage

The Supabase software is open source under the Apache 2.0 license, so there is no license fee. You only pay for the VPS: a fixed monthly price for the package you choose, no matter how many rows, requests or users your project has. The current prices for every package are shown in the pricing section above. Cancel anytime, effective at the end of your term.

• No usage-based billing on rows or requests
• No auto-pausing of idle projects
• Flexible terms, cancel anytime

Yes. Point a subdomain such as supabase.yourdomain.com to your VPS IP with an A record, then set it as the domain of the Supabase service in Coolify. Coolify's proxy requests a Let's Encrypt certificate, so Studio and the API run over HTTPS. Update the site URL in the Auth settings so login links and OAuth redirects use the new domain. How to set DNS records

Yes. Export the database from your Cloud project with pg_dump or the Supabase CLI, restore it into the Postgres instance on your VPS and copy your Storage files bucket by bucket. Afterwards point your app to the new API URL and keys. Test Auth redirects and Row Level Security policies on the new instance before you switch production traffic.

• Database: pg_dump and restore
• Storage: copy files per bucket
• App: swap the API URL, anon key and service key

The core stays the same: Postgres, Auth, Storage, Realtime, Studio and the auto-generated APIs. Some platform features are Cloud-only, such as database branching, managed point-in-time recovery, the Management API and multiple projects in one Studio. Edge Functions can run self-hosted, but you deploy and operate them yourself. In return you get full control, a fixed price and your data on your own server.

You do, with Coolify doing much of the work. Updates run through Coolify: check the new image versions, take a Backup first, then redeploy the service. Keep secrets such as the JWT secret and service key private and only expose the ports you need. Back up the database with pg_dump on a schedule and keep a copy off the server. Snapshots, manual Backups and restore of the whole VPS come with ZapX Pass. Learn more about Backups

• Back up before every update
• Keep a database dump outside the VPS

ZAP-Hosting runs VPS locations in Europe and America. Pick the one closest to your app's users and your other services, because that keeps API and Realtime round trips short. Many North American projects start with Ashburn, Dallas or Los Angeles. You choose the location when you order your VPS.