Platform

Instances, plans, usage, domains, backups, branching, team, SSH and moving in or out.

20 pages · start with Instances

  1. 01InstancesAn 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.
  2. 02ProjectsEach SupaHost project is a full Supabase project with its own database, Auth, Storage, URL and keys. Creating projects, naming rules, the project tabs and deleting a project.
  3. 03Plans and limitsSupaHost's Builder, Pro, Business and Enterprise plans side by side: server size, included projects, shared quotas, backups, branching, SSH and measured capacity.
  4. 04Free trial and billingHow SupaHost's 7-day free trial works, the 3-project trial limit, activating your plan early, monthly or annual billing, invoices and billing emails.
  5. 05Usage, quotas and add-onsHow SupaHost measures database size, file storage and egress across your projects, how quota alerts work, what add-ons cost, and how overage is billed.
  6. 06RegionsThe nine regions you can run a SupaHost instance in, how to choose one, where your data and backups are stored, and why the region can't be changed later.
  7. 07Custom domainsServe a SupaHost project from your own domain such as api.example.com, with automatic Let's Encrypt HTTPS. DNS records, Cloudflare settings, domain states and OAuth callbacks.
  8. 08BackupsHow SupaHost backs up your project databases every day, how long backups are kept on each plan, where they're stored, and why Storage files need their own export.
  9. 09Point-in-time recoveryRestore a SupaHost project's database to any second inside your plan's window (7 days on Pro, 14 on Business). How PITR works, choosing the right moment, and what it doesn't cover.
  10. 10Restoring a projectHow to restore one SupaHost project from a daily backup or a point in time, what happens step by step, how long the project is offline, and what to check afterwards.
  11. 11Exporting your dataDownload a pg_dump of any SupaHost project's database and a .tar.gz of all its Storage files from the Backups tab, and restore them into Postgres or another Supabase.
  12. 12BranchingCreate a branch of a SupaHost project, with or without its data, users and files, to test migrations safely. What's copied, what isn't, and how to ship changes without a merge.
  13. 13Team membersInvite teammates to your SupaHost instance. What invited members can see, which actions stay with the owner, and how to give teammates' tools safe access.
  14. 14Access tokensCreate, scope and revoke SupaHost access tokens for the MCP server and AI coding agents. Project or instance scope, read-only tokens and narrowing access with URL parameters.
  15. 15SSH access and direct PostgresOn Business and Enterprise, SSH into your SupaHost instance as a restricted user to run psql, read service logs and open a tunnel for direct Postgres connections from pg_dump, ORMs and GUI tools.
  16. 16Monitoring, health checks and alertsHow SupaHost checks your instance every minute, when downtime and usage alert emails are sent, how to set notification preferences, and how disks grow automatically.
  17. 17Importing from Supabase CloudCopy a Supabase Cloud project into SupaHost in one step: database, Auth users with passwords, RLS policies, roles, Storage buckets and files. Requirements and what to redo afterwards.
  18. 18Moving off SupaHostEverything you need to take a project from SupaHost to Supabase Cloud, a self-hosted Supabase or plain Postgres: database dump, Storage files, functions, cron jobs, settings and the switch-over.
  19. 19Changing plansUpgrade or downgrade a SupaHost instance between Builder, Pro and Business. What changes, the minute or two of downtime while the VM resizes, and what to check before you switch.
  20. 20Limits referenceEvery SupaHost limit in one place: plan quotas, project names, database connections, Data API rows, Storage file size, Auth settings, Realtime, Edge Functions, cron, backups and SSH.