Instances
An instance is your own cloud VM running the Supabase stack for all of your projects. What runs on it, the Instance page, software updates and how termination works.
An instance is the server your projects run on. Every SupaHost customer gets their own cloud VM, not shared with any other customer, running the open-source Supabase stack. You pay one flat monthly price for the instance, and your plan decides how big the VM is and how much database, file storage and egress your projects share.
One instance holds many projects. Each project behaves like a normal Supabase project with its own database, Auth, Storage, URL and keys. See Projects for what lives inside a project.
What runs on an instance
Some services are shared by every project on the instance, and some run once per project.
| Runs once per instance | Runs per project |
|---|---|
| One Postgres 17 server (each project gets its own database on it) | Auth (GoTrue) |
| Realtime (one service, one tenant per project) | Data API (PostgREST) |
| postgres-meta (used by Studio and the MCP server) | Storage API |
| Caddy, which handles HTTPS and routes requests to the right project | Edge Functions, only once the project has a function |
| A login gate for Studio | Studio, only while someone is using it |
Studio starts the first time you open it, which takes about 20 seconds, and stops after 30 minutes without use. That's why the first open of the day can feel slow: see Studio takes a while to open.
Sharing one Postgres server means the projects on an instance also share its connection limit (400 connections in total) and its CPU and memory. If one project runs a heavy query, the others can feel it. More on that in Connections and timeouts.
Server sizes
| Plan | VM | Starting disk |
|---|---|---|
| Builder | 2 shared vCPU, 4 GB RAM | 50 GB |
| Pro | Dedicated 2 vCPU, 8 GB RAM | 100 GB |
| Business | Dedicated 4 vCPU, 16 GB RAM | 200 GB |
| Enterprise | Custom | 400 GB |
The VM runs Ubuntu 24.04 LTS as a Shielded VM (secure boot and a virtual TPM) with deletion protection and a static IP address. The disk grows on its own as it fills, without a restart; see Monitoring, health checks and alerts. To move to a bigger VM, change plan: Changing plans.
Addresses
Each instance has its own hostname under supahost.space. For an instance called acme:
| What | Address |
|---|---|
| Instance | https://acme.supahost.space |
| A project's API | https://app-one.acme.supahost.space |
| A project's Studio | https://app-one.studio.acme.supahost.space (opened from the dashboard) |
The instance address answers with a small JSON status, which is handy for a quick check or an external uptime monitor:
curl https://acme.supahost.space
# {"instance":"acme","status":"ok"}
The Instance page
Open Dashboard → Instance in the sidebar. It shows:
- URL, Region, Plan, number of Projects and the Created date.
- "Postgres 17 · one database per project".
- Pausing: Never. Instances and projects don't pause when they're idle. See Do SupaHost projects pause when inactive?.
- A Software updates card with the version of each component.
- A "Live metrics" card. CPU, memory and disk charts are marked coming soon.
Software updates
SupaHost ships the Supabase components as numbered releases. At the time of writing the current release is 2026.11.02, with Postgres 17.6.1.136, Auth v2.197.0, PostgREST v14.18, Realtime v2.148.3, Storage v1.89.12 and Edge Runtime v1.78.1. The Software updates card always shows what your instance runs now.
You have two ways to take an update:
- Upgrade now. SupaHost takes a disk snapshot of the instance first, then rolls out the new release.
- Automatic upgrades. Turn them on and pick a maintenance window: Sundays, Saturdays, Wednesdays or any day, between 03:00-05:00 UTC. Updates then happen inside that window.
If automatic upgrades are off, the owner gets one email per release saying an upgrade is available, and another when an upgrade finishes. Services can be interrupted briefly while new versions start, so choose a window when your traffic is low.
Terminating an instance
At the bottom of the Instance page, Terminate asks you to type the instance name to confirm. This sends a termination request to SupaHost by email; it doesn't delete anything on the spot. Before you request it, take exports of every project you want to keep, as described in Moving off SupaHost.