Supabase on GCP - Developer Guide

Welcome to the Meetrix Supabase developer guide for Google Cloud Platform! Supabase bundles a PostgreSQL database, Auth, Storage, Realtime, Edge Functions, and the Studio dashboard into a single self-hosted backend, the open-source alternative to Firebase without the per-document billing. With the Meetrix pre-configured GCP image, the whole stack is installed and wired together the moment the VM boots.

This guide walks you through finding the product on GCP Marketplace, configuring the deployment, reserving a static IP, pointing DNS at your server, and signing in to Studio to start building.

Supabase on GCP Marketplace by Meetrix - Deploy the Open-Source Firebase Alternative in Minutes

Deploy Supabase on Google Cloud in minutes with Meetrix's pre-configured GCP Marketplace listing. Get Postgres, Auth, Storage, and Realtime running on your own infrastructure, with no Firebase-style usage billing.

By Shalomi Umeshika • Meetrix.io

Launch the Product

Step 1: Find the Product

1. Log in to your Google account.
2. Go directly to the product page: Supabase: Open-Source Firebase Alternative with PostgreSQL
3. You can also browse all Meetrix products at the Meetrix Solutions Page.
4. You will see the product listing page. Click Get started.

Step 2: Accept the Agreements

1. Confirm your GCP project is selected.
2. Tick the box under Terms and agreements to accept the Google Cloud Marketplace and Meetrix Pte Ltd terms of service.
3. Click AGREE.

Free Trial

This product includes a 5-day free trial with up to USD 50.00 in licence fee credits. To activate it, tick I accept the solution trial Terms and Conditions on the launch screen before proceeding.

Step 3: Configure the Deployment

You will see the deployment configuration form, with Terraform and Command-Line deployment tabs. Fill in the fields across the following sections:

General

• Deployment name - A unique name for this deployment (e.g. supabase-1).
• Deployment Service Account - Use an existing service account with the config.agent, compute.admin, and iam.serviceAccountUser roles, or create a new one.
• Zone - Select the GCP zone closest to your users (e.g. us-central1-a).
• Machine type - Default e2-medium (2 vCPU, 4 GB RAM) works for early development. Scale up if you expect heavier query load or a larger Postgres database.

Boot Disk

Keep the default persistent disk settings unless you expect a large database or heavy Storage usage, in which case increase the disk size accordingly.

Networking

• Network / Subnetwork - Leave as default unless you have a custom VPC.
• External IP - Leave as Ephemeral for now. You will reserve a static IP before pointing DNS at the server.
• Allow SSH (TCP port 22) - Enabled by default. Restrict the source IP range if you want to limit SSH access to specific IPs.

Application Settings

• Domain name - The domain for your Supabase instance (e.g. backend.yourdomain.com). Point your DNS A record to the instance IP before or shortly after deploying.
• Admin email - Used for SSL certificate registration via Let's Encrypt.
• Dashboard username / password - Credentials that protect the Studio dashboard behind HTTP Basic Auth, separate from any Supabase Auth users you create later.

Once the fields are filled in, follow the on-screen instructions in your chosen tab (Terraform or Command-Line deployment) to deploy, and wait a few minutes for the deployment to complete.

Reserve a Static IP

1. Open the VM instance created by the deployment and note the External IP under Network interfaces - it is marked (Ephemeral).
2. In the GCP console, go to VPC network → IP addresses, find that same address, and click Reserve Static Address (or promote it directly from the VM instance details page).
3. Copy the reserved external IP - you will use it for your A record.

Point DNS to the Server

1. Add an A record pointing your chosen domain (e.g. backend.yourdomain.com) to the reserved static IP.
2. Wait for DNS propagation before proceeding (typically a few minutes to 1 hour).

SSH into the Server

1. Go to the VM instance page in the GCP console.
2. Click SSH to open a browser-based terminal and authorize access.

Access Supabase

Once DNS has propagated and the instance has issued its SSL certificate, open your domain in the browser. You will be prompted to sign in with the dashboard username and password you set during deployment.

After signing in, you land on the Studio home screen for your default project, showing table and function counts, security and performance checks, and any slow queries.

Manage the Server

Check Running Containers

sudo docker ps

Shut Down the VM

To stop the VM without deleting it, go to Compute Engine → VM Instances in the GCP console, select your instance, and click Stop.

Delete the Deployment

To fully remove the deployment and stop all billing:

1. Go to Solution deployments in the GCP console.
2. Find your Supabase deployment.
3. Click Delete to remove all associated resources.

Troubleshoot

Check the Service Logs

Supabase runs on Docker. Find the running containers and check their logs:

sudo docker ps
sudo docker logs <container_id>

Instance Storage Full

Check disk usage on the server:

df -h

If the root volume is between 90-100%, resize the persistent disk in the GCP console and reboot the instance.

Conclusion

The Meetrix Supabase developer guide helps you get a self-hosted backend running on GCP without a weekend lost to Docker Compose files and certificate renewals. Reserve a static IP, point your domain at it, sign in to Studio, and you have a real PostgreSQL-backed alternative to Firebase running on infrastructure you control.

Technical Support

If you run into any issues, our support team is here to help. Reach out to us at support@meetrix.io and we will respond within 12 hours.