What self-hosting actually changes
The pieces are the same as the hosted product; the operating is yours. That is a good trade when the data cannot leave a region, and a poor one when nobody on the team wants to run Postgres.
Where it earns its keep
The database is the workload
Performance VPS puts the same tier on NVMe, which is where an fsync-bound database spends its day.
Private by default
Put the app and the database on a private network and close the public port entirely.
No row or request quota
The machine is the limit. A noisy analytics table does not change the invoice.
Give it NVMe if it is doing real work
The whole stack starts on a shared-vCPU tier, but Postgres rewards fast storage more than almost anything else you can install. Performance VPS is the same size on NVMe with EPYC cores.
From order to a working Supabase
Pick Supabase as the image
Performance VPS if the database is the point.
Point a hostname at it
The API and Studio both answer on it, over TLS.
Collect your keys
Generated on first boot and shown in your dashboard.
Point your app at it
Swap the URL and the anon key; the client library is unchanged.
Straight answers before you deploy
The same open-source components, run by you. Features that are part of their hosted platform rather than the open stack are not included.
You do. We keep the machine patched and take nightly backups; rolling the stack forward is a decision about your data, so it stays with you.
Ready when you are.
Configure a server now. Your account is created right before payment, with the configuration saved.