Yes. Supabase is open source: its main repository, including Studio, is under the Apache 2.0 licence, and the other services it runs are open source too. Running it on your own server costs nothing beyond the server. Supabase's own hosted platform has free and paid plans; with ServerAvatar you host it yourself.

How do I sign in to Supabase Studio?

Open your domain and enter the username supabase and the password the panel showed when it created the application. This is HTTP basic authentication in the Kong gateway, as in Supabase's self-hosting guide. Self-hosted Studio has no separate accounts, so anyone with that password has full access to the project. Your app's own users sign up through Auth, not through Studio.

How do I connect my app to Supabase?

Use https://your-domain as the project URL and the anon key from Project Settings > API Keys in Studio, with supabase-js or another client library. Turn on row level security and add policies to every table the anon key may reach, and keep the service_role key on your server, because it bypasses row level security. If your front end runs on another address, add it to GOTRUE_URI_ALLOW_LIST in the app's Compose File in the panel and click Save and apply, so sign-in can redirect back to it.

How much RAM does Supabase need?

Supabase's self-hosting guide gives 4 GB of RAM and 2 CPU cores as the minimum for running all its services, and recommends 8 GB and 4 cores or more. The recipe gives each container its own memory limit: Kong takes the application limit (at least 1 GB, which you can raise under Memory limit), Studio, Realtime and Edge Functions 1 GB each, Storage and imgproxy 512 MB each, Auth, PostgREST and postgres-meta 256 MB each, and PostgreSQL the panel's database default. On our test servers the whole stack used about 1.0 to 1.4 GB at idle.

Do I need email (SMTP) for Supabase?

Not to get started. Email autoconfirm is on, so a user who signs up through Auth is confirmed at once and can sign in. To send real emails, such as confirmations, magic links and password resets, set GOTRUE_SMTP_HOST, GOTRUE_SMTP_PORT, GOTRUE_SMTP_USER, GOTRUE_SMTP_PASS, GOTRUE_SMTP_ADMIN_EMAIL and GOTRUE_SMTP_SENDER_NAME for the auth service in the app's Compose File in the panel, set GOTRUE_MAILER_AUTOCONFIRM to false, and click Save and apply. Phone sign-up is off, because no SMS provider is set.

What does this install leave out?

Studio's Logs pages are not available, because the optional log services (Vector and Logflare) are not installed. There is no connection pooler (Supavisor), and PostgreSQL is not reachable from outside the server: use the REST API, the client libraries or Studio's SQL editor. GraphQL at /graphql/v1 works once you enable the pg_graphql extension under Database > Extensions in Studio.

Supabase on your own server, in one click.

Build your app's backend on Supabase, with a Postgres database, user sign-in, an instant API, realtime, file storage and edge functions, on a server you own. ServerAvatar runs its ten services in Docker and sets up the keys, storage and HTTPS for you.

Postgres + Auth + Storage + Realtime
HTTPS on its own
Your server, your data

Deploy Supabase See how it installs

Section 01What is Supabase

What is Supabase?

Supabase is an open-source backend for web and mobile apps, often called the open-source alternative to Firebase. It is built around a PostgreSQL database and adds user sign-up and sign-in, an instant REST API, realtime messages, file storage and edge functions, all managed from a dashboard called Studio.

This recipe runs Supabase's official self-hosted Docker setup: ten containers behind one Kong gateway, which serves Studio at your domain and every API under paths such as /rest/v1 and /auth/v1. Your database, users and files stay in Docker volumes on your server, and your apps connect with the same client libraries as on Supabase's own platform.

Free and open source (Apache 2.0)
Database, auth, APIs, realtime, storage and functions
Built on PostgreSQL 17

Section 02Features

What you can do with Supabase

A full Postgres database
Every table is a real PostgreSQL 17 table. Create and edit tables in Studio's table editor, or write SQL in its SQL editor and save your queries as snippets.
User sign-up and sign-in
Auth signs users up and in with email and password and gives them JWT sessions. Social logins such as Google or GitHub are switched on with Auth variables in the Compose File.
An instant REST API
PostgREST turns your tables, views and functions into a REST API under /rest/v1 as soon as you create them, and row level security decides who sees which rows.
Realtime
Send messages between clients with Broadcast, show who is online with Presence, and listen to inserts, updates and deletes with Postgres Changes.
File storage
Upload files to buckets, protect them with policies like your tables, and resize images on the fly with imgproxy. An S3-compatible endpoint is included.
Edge Functions
Run your own TypeScript functions on Deno under /functions/v1. Add a folder with an index.ts file in the site folder and restart the functions container.

Section 03Requirements

What you need

A fresh Ubuntu server you can log in to as root. The installer checks all of this before it changes anything.

Supabase on Docker
Requirement	Supabase on Docker
Operating system	Ubuntu 24.04 or 26.04 LTS (x86-64)
CPU	2 cores or more
RAM	4 GB or more
Disk	40 GB or more (80 GB recommended)
Containers	Kong 3.9 gateway + Studio + Postgres 17 + 7 more services
Email	Optional: SMTP, for confirmation, magic link and password reset emails
Ports	80 and 443 open

CPU and RAM are the minimum in Supabase's self-hosting guide for running all its services; it recommends 4 cores and 8 GB or more. Disk: about 14 GB is in use once the panel and Supabase are installed on our test server; Supabase's requirements ask for 40 GB on an SSD and recommend 80 GB or more.

Section 04Install

How to install Supabase

Every step happens in the ServerAvatar panel. No terminal needed.

Pick Supabase in 1-Click Recipes
On your server, open Applications, click Create application and search for Supabase under 1-Click Recipes.
Name it and choose a domain
Give the application a name and use your own domain, or a temporary one that works right away. The panel creates a system user for it.
Create it
Click Create application. The panel starts Supabase's ten containers, turns HTTPS on and shows the secrets it generated, including the Studio password, the database password and the JWT secret that signs every session and API key. Copy them somewhere safe. The first install pulls about 8 GB of images and took 5 to 7 minutes on our test servers. The Edge Functions container also downloads a library on its first start, so the server needs outgoing internet access.
Sign in to Studio and copy your keys
Open your domain. The browser asks for a username and password: enter supabase and the password the panel shows, and Supabase Studio opens. Your anon and service_role keys are under Project Settings > API Keys (Legacy anon, service_role API keys). The anon key is safe in browser code with row level security on; the service_role key bypasses row level security, so keep it on the server side.

Section 05FAQ

Questions,answered.

Can't find the answer you're looking for? Reach out to our customer support.

Contact support

Risk free

Deploy your first appin 10 minutes.

Connect a server, pick an application and go live, with SSL and backups already in place.

Start free Plans & pricing

No credit card required
Free 4-day trial
Deploy in the next 10 minutes

Supabase on your own server, in one click.

What is Supabase?

What you can do with Supabase

A full Postgres database

User sign-up and sign-in

An instant REST API

Realtime

File storage

Edge Functions

What you need

How to install Supabase

Pick Supabase in 1-Click Recipes

Name it and choose a domain

Create it

Sign in to Studio and copy your keys