> Source: https://meetrix.io/store/supabase/
> Markdown copy of that page. Cite the URL above, not this file.

[Store](https://meetrix.io/store/)  Supabase

Open-source Firebase alternative

# Self-hosted Supabase on AWS and Google Cloud

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.

 [Launch on AWS](https://aws.amazon.com/marketplace/pp/prodview-qg3lale77sic4)[ Launch on Google Cloud](https://console.cloud.google.com/marketplace/product/meetrix-public/supabase-firebase-alternative)

-   Ready in 5-10 minutes
-   Studio over HTTPS
-   No usage-based billing

![Supabase deployed on Google Cloud by Meetrix](https://meetrix.io/assets/store/supabase/supabase.webp)

## What is Supabase?

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.

-   ### PostgreSQL

    A real Postgres database with SQL, joins and extensions such as pgvector.

-   ### Auth

    User sign-up, sign-in and access rules built in.

-   ### Storage

    File storage buckets managed alongside your data.

-   ### Realtime

    Subscribe to database changes from your app.

-   ### Instant APIs

    REST and GraphQL APIs generated from your schema.

-   ### Studio

    A browser dashboard for tables, users, storage and edge functions.

## What's in the Meetrix Supabase image

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.

-   The open-source Supabase stack running in Docker
-   Studio behind HTTP Basic Auth with the credentials you choose
-   A reverse proxy with a Let's Encrypt certificate for your domain
-   Automatic SSL on AWS when the domain is hosted on Route 53
-   A deployment template for your own AWS account or GCP project
-   Email support from Meetrix at support@meetrix.io

## How to set up self-hosted Supabase

1.  ### Launch the server

    Subscribe on AWS Marketplace or Google Cloud Marketplace, enter your domain, admin email and dashboard username and password, and deploy.

2.  ### Give it a fixed address

    Supabase needs a real domain for SSL. Point a DNS A record at the server; on Google Cloud, reserve a static external IP first.

3.  ### Sign in to Studio

    Open your domain (the DashboardUrl on AWS) and sign in with the dashboard username and password you set at deployment.

4.  ### Start building

    Create tables, set up Auth and storage buckets, and connect your app or any Postgres client to the database.

## Choose your cloud

### Supabase on AWS

An AMI on AWS Marketplace, launched into your own AWS account with a CloudFormation stack.

Deploys with

CloudFormation

Recommended size

t3.medium

Ready in

5-10 minutes

#### Setup guides

-   [**Developer guide** Launch, DNS, Studio, SSL](https://meetrix.io/blogs/supabase-developer-guide/)
-   [**Self-host Supabase on AWS** Self-hosted vs Supabase Cloud](https://meetrix.io/blogs/self-host-supabase-aws-meetrix/)
-   [**Video walkthrough** Watch the deployment on YouTube](https://www.youtube.com/watch?v=FNNX7mPdw4k)

 [Launch on AWS](https://aws.amazon.com/marketplace/pp/prodview-qg3lale77sic4)

### Supabase on Google Cloud

The same backend stack as a Google Cloud Marketplace image, deployed into your own GCP project.

Deploys with

Terraform or gcloud CLI

Recommended size

e2-medium

Free trial

5 days, up to USD 50 licence credit

#### Setup guides

-   [**Developer guide** Static IP, DNS, Studio sign-in](https://meetrix.io/blogs/supabase-gcp-developer-guide/)
-   [**Supabase on Google Cloud Marketplace** Who it suits and how it compares](https://meetrix.io/blogs/supabase-firebase-alternative-gcp/)

 [Launch on Google Cloud](https://console.cloud.google.com/marketplace/product/meetrix-public/supabase-firebase-alternative)

## Supabase by Meetrix vs Firebase vs Supabase 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 →](https://meetrix.io/blogs/supabase-vs-firebase/)

## Video: deploy Supabase on AWS

## Supabase FAQ

What is Supabase?

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.

Is this the same as Supabase Cloud?

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.

Is Supabase Studio included?

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.

Can I connect to the Postgres database directly?

Yes. It is standard PostgreSQL, so you can use any Postgres client, run your own migrations and add extensions.

Do I need a domain?

Yes. Supabase needs a real domain for SSL to issue correctly; an IP address on its own will not work. On Google Cloud, reserve a static IP so the DNS record keeps working after a restart.

Can I migrate from Supabase Cloud or Firebase?

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.

Which machine size should I choose?

t3.medium 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.

How do I upgrade?

Deploy a fresh instance with the newer image and migrate your database. Back up your PostgreSQL data before removing the old instance.

## Supabase guides and articles

### [Supabase vs Firebase: Self-Hosting Supabase on Google Cloud](https://meetrix.io/blogs/supabase-vs-firebase/)

Postgres vs Firestore, real pricing, and what self-hosting Supabase gives up.

### [How to Migrate from Supabase Cloud to Self-Hosted](https://meetrix.io/blogs/migrate-supabase-cloud-to-self-hosted/)

Move your database, storage and auth settings to your own server.

### [Supabase Self-Hosting Security Best Practices](https://meetrix.io/blogs/supabase-self-hosted-security/)

Lock down a self-hosted Supabase stack before it goes to production.

## Need a hand with your Supabase server?

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](https://meetrix.io/contact-us/)