Run the full Supabase stack, with PostgreSQL, Auth, Storage, Realtime and the Studio dashboard, from a pre-configured image in your own cloud account. A real Postgres backend you own, without per-document billing.
Supabase is an open-source backend platform built on PostgreSQL. It bundles a database, authentication, file storage, realtime subscriptions and auto-generated APIs into one project, which is why it is often called the open-source Firebase alternative. Unlike Firebase, the data sits in a standard relational database you can query with SQL.
A real Postgres database with SQL, joins and extensions such as pgvector.
User sign-up, sign-in and access rules built in.
File storage buckets managed alongside your data.
Subscribe to database changes from your app.
REST and GraphQL APIs generated from your schema.
A browser dashboard for tables, users, storage and edge functions.
Self-hosting Supabase by hand is a long Docker Compose file, a reverse proxy and certificates to keep renewed. The marketplace image installs and wires the whole stack when the server boots.
Subscribe on AWS Marketplace or Google Cloud Marketplace, enter your domain, admin email and dashboard username and password, and deploy.
Supabase needs a real domain for SSL. Point a DNS A record at the server; on Google Cloud, reserve a static external IP first.
Open your domain (the DashboardUrl on AWS) and sign in with the dashboard username and password you set at deployment.
Create tables, set up Auth and storage buckets, and connect your app or any Postgres client to the database.
An AMI on AWS Marketplace, launched into your own AWS account with a CloudFormation stack. You choose the volume size and an S3 bucket for daily database backups at launch.
Launch on AWS 
The same backend stack as a Google Cloud Marketplace image, deployed into your own GCP project.
Launch on Google Cloud | Supabase by Meetrix | Firebase | Supabase Cloud | |
|---|---|---|---|
| Hosting | Your AWS account or GCP project | Google's managed infrastructure, no self-host option | Supabase's managed cloud |
| Database | PostgreSQL you own | Firestore, a NoSQL document store | PostgreSQL on Supabase's infrastructure |
| Pricing model | Cloud compute only, no per-document billing | Pay per read, write and delete | Per-project subscription plus usage |
| Data residency | Any region you choose | Google's data terms apply | Limited to Supabase's regions |
Moving from Firebase means remodelling documents into relational tables. Read the full Supabase vs Firebase comparison →
Supabase is an open-source backend platform built on PostgreSQL. It bundles a database, authentication, file storage, realtime subscriptions and auto-generated APIs, and is often described as the open-source Firebase alternative.
No. It is a self-hosted deployment of the open-source Supabase stack in your own AWS account or GCP project. Your database and files stay on infrastructure you control.
Yes. Studio is served over HTTPS and protected by HTTP Basic Auth with the dashboard username and password you set at deployment, separate from any users you create in Supabase Auth.
Yes. It is standard PostgreSQL, so you can use any Postgres client, run your own migrations and add extensions. On AWS the database listens on localhost only, so you connect through an SSH tunnel.
For HTTPS, yes: SSL needs a real domain, not an IP address. On AWS you can also run Supabase on its Elastic IP over plain HTTP while you test. On Google Cloud, reserve a static IP so the DNS record keeps working after a restart.
From Supabase Cloud, a Postgres dump and restore covers most of the move. From Firebase it takes more work, because Firestore documents have to be remodelled into relational tables.
t3a.medium (2 vCPU, 4 GiB RAM) on AWS, or e2-medium (2 vCPU, 4 GB RAM) on Google Cloud for early development. Scale up for heavier query load or a larger database.
On AWS, yes. Name an S3 bucket at launch and the server uploads a full database dump to it every day at 12:00 UTC. Files uploaded to Supabase Storage are not in the dump, so protect them with EBS snapshots.
Deploy a fresh instance with the newer image and migrate your database. Back up your PostgreSQL data before removing the old instance.
Postgres vs Firestore, real pricing, and what self-hosting Supabase gives up.
Move your database, storage and auth settings to your own server.
Lock down a self-hosted Supabase stack before it goes to production.
We build and run self-hosted backends for teams every day, from Supabase Cloud migrations to backups and scaling. Tell us what you need.
Contact us