---
title: Deploy Supabase with AI
url: "/guides/supabase/"
canonical_url: https://docs.blossom88.com/guides/supabase/
markdown_url: https://docs.blossom88.com/guides/supabase.md
summary: Deploy Supabase with AI on Blossom. Self-host a PostgreSQL backend with authentication,
  data APIs, Realtime, private file storage, and functions.
categories:
- deployment
- backend
---

# Deploy Supabase with AI

[Supabase](https://supabase.com/) is an open-source backend built around
PostgreSQL. It gives your app authentication, database APIs, Realtime,
file storage, and functions, with a dashboard for managing them.

Run your own Supabase backend on Blossom and connect it to your web or
mobile app.




[Install the Blossom CLI and skill](/learn/getting-started/install/)
on your agent's machine and choose a Blossom Cloud Location when you log in.
You can also use
[Blossom BYOC (bring your own cloud)](/learn/getting-started/choose-your-cloud/#blossom-byoc).

## Ask Your Agent


> **Ask your AI agent:** Deploy Supabase on Blossom and help me connect my app.

> Follow this guide: https://docs.blossom88.com/guides/supabase/



Your agent checks the current
[Supabase self-hosting requirements](https://supabase.com/docs/guides/self-hosting/docker),
selects compatible maintained images, and saves its configuration with your
App. Our tested recipe used **nine native Blossom Services**, each with its
own image and allocation.

| Part | Purpose |
|---|---|
| Supabase PostgreSQL | Keeps your database, users, policies, and file metadata |
| Auth | Provides user accounts and sign-in |
| Data API | Exposes PostgreSQL through an API |
| Realtime | Sends live database updates to your app |
| Storage API | Manages uploaded files and access policies |
| Functions | Runs your deployed backend code |
| Gateway | Routes API requests and protects Studio |
| Studio | Provides the administration dashboard |
| Database metadata | Lets Studio inspect and manage PostgreSQL |

Supabase needs its compatible PostgreSQL image, extensions, roles, and
initialization scripts. Use a private
[Persistent Service](/docs/apps/persistent-services/) for that database;
a standard managed PostgreSQL connection is not a drop-in replacement for
the full stack.

Blossom manages these as individual resources across App and Persistent
Capacity, with private connections between them. The platform can place and
replace components independently; supported application tiers can scale
separately. This recipe keeps its Volume-backed Services as singletons.

The agent keeps database passwords, signing keys, and dashboard credentials
stable across deployments. Keep the database and internal services private.
The gateway exposes your application's APIs; Studio requires a separate
administrator login.

## Connect Your App

> **Ask your AI agent:** Connect my app to Supabase. Add sign-in, a table where each user sees their own records, and private file uploads.

> Follow this guide: https://docs.blossom88.com/guides/supabase/



Use the generated HTTPS endpoint and the public client key in your app.
Keep the privileged server key in backend configuration. Your agent enables
row-level security and checks access as two different users.

Configure your email provider before enabling public signups, confirmation
messages, or password resets. You can start with administrator-created test
users while setting up your app.

![A Next.js client showing saved notes, private files, and a live connection to Supabase on Blossom.](/assets/images/guides/supabase/backend-client.png)

Supabase Studio gives you a dashboard for the same backend:

![Supabase Studio displaying the notes table and its row-level security policy.](/assets/images/guides/supabase/studio-notes.png)

<details class="optional-reading" markdown="1">
<summary>Commands behind the deployment</summary>

Your agent uses current CLI help and the selected Supabase release's
configuration. Use the IDs returned by Blossom in these examples.

### Create the App and Environment

    blossom profile:show
    blossom app:create --data '{"app":{"name":"supabase"}}'
    blossom environment:create --data environment.yml

The agent prepares environment.yml with your App ID, a prebuilt gateway
image, and public access for SDK requests. It protects Studio through the
gateway's dashboard authentication.

### Configure Native Services

The selected upstream release provides the matching images, SQL scripts,
gateway routes, and service settings. The agent adapts those to Blossom's
private Service names and each image's supported startup command.

    blossom service:create --data postgres.yml
    blossom service:create --data auth.yml
    blossom service:create --data rest.yml
    blossom service:create --data realtime.yml
    blossom service:create --data storage.yml
    blossom service:create --data functions.yml
    blossom service:create --data meta.yml
    blossom service:create --data studio.yml
    blossom service:create --data gateway.yml

Each service.yml selects its own image. PostgreSQL, uploaded objects, and
saved Studio snippets use Persistent Volumes. Keep function source in your
saved deployment configuration so it is included in every release.

Run each Volume-backed Service as one Container. This recipe does not
configure PostgreSQL failover or distributed file storage. Additional
replicas require a deployment designed for those components.

The agent configures the gateway's upstream address family to match the
application listeners. It checks real REST and Storage responses through
the gateway, including when an upstream image has no shell for a command
health check. Network-dependent processes wait for their database before
starting.

### Deploy and Connect

    blossom env_var:push --environment environment-100 --file .env.production
    blossom environment:deploy --id environment-100 --follow
    blossom environment:show --id environment-100
    blossom logs --environment environment-100 --process web

Keep credentials in the private environment file. After Blossom assigns the
HTTPS URL, the agent applies it to the gateway, Auth, Studio, and Storage
settings, with your application's URL as the sign-in redirect destination.

Optional components such as image transformations, log analytics, or a
connection pooler have their own upstream requirements. Add them when your
app needs them.

</details>

## What Will It Cost?

With the cheapest eligible Hetzner CX sizes, the tested allocations work out
to **about $48/month including Blossom BYOC management** for the steady
footprint. Keeping a full replacement App fleet ready raises the estimate
to **about $66/month**.

| Example | Hetzner | Blossom BYOC | Total per month |
|---|---:|---:|---:|
| Steady footprint, On demand | $27.67 | $20.00 | $47.67 |
| With a full replacement App fleet | $36.17 | $30.00 | $66.17 |

These are ideal CX price estimates for an otherwise empty Location, not
measurements of what every customer will use. Cost optimization can move
eligible App capacity onto cheaper sizes; it is separate from how much
capacity you reserve for deployments.

<details class="optional-reading" markdown="1">
<summary>How the estimate is calculated</summary>

Checked November 19, 2026. USD before tax, credits, backups, email, extra
transfer, and other usage. Container reservations come from the successful
Supabase test, without reducing their CPU or memory allocations. Server
prices exclude IPv4, which is listed separately.

| Infrastructure | Steady footprint | With replacement room |
|---|---|---|
| App Server | CX33: 4 vCPU / 8 GB, $9.99 | CX43: 8 vCPU / 16 GB, $18.49 |
| PostgreSQL Persistent Server | CX23: 2 vCPU / 4 GB, $6.49 | Same |
| Shared Persistent Server for Studio and Storage | CX23: 2 vCPU / 4 GB, $6.49 | Same |
| Three IPv4 addresses | $1.80 | $1.80 |
| Three Volumes, 60 GiB total | $2.90 | $2.90 |

Blossom BYOC charges $5 per 2 vCPU / 4 GB of running App or Persistent
Capacity. That is four units for the steady footprint and six with the
larger App Server. Provider Volumes have no additional Blossom BYOC storage
management fee. The replacement room is for the six App Services; it does
not create database or file-store replicas.

The On demand figure excludes temporary deployment capacity and its idle
retention. Existing spare capacity can lower the additional cost of adding
Supabase to an Account. Ask your agent for the current plan before deploying.

Sources: [Hetzner CX prices](https://www.hetzner.com/cloud/cost-optimized/),
[Volumes](https://www.hetzner.com/cloud/block-storage/), and
[Blossom BYOC rates](https://blossom88.com/pricing/details?offering=blossom_byoc).

</details>

## Keep Your Data Through Updates

> **Ask your AI agent:** Update my Supabase app, then check that I can still sign in and read my saved records and uploaded files.

> Follow this guide: https://docs.blossom88.com/guides/supabase/



The agent preserves the existing Volumes and secrets, follows the selected
release's upgrade instructions, and checks your app afterward. Database
and file access can pause while their single Containers are replaced.

## What You Get

Your own Supabase backend with HTTPS APIs, authentication, PostgreSQL,
Realtime, private files, functions, and a password-protected Studio.
Your database and uploaded files persist across app updates.
