---
title: "Connect Supabase"
description: "Use a Supabase project you own for authentication, database, and storage."
---
Bring your own Supabase project when you need direct control of the backend, already have data there, or want to manage infrastructure in your own account. This option is available in Superapp for Mac.

:::note
Superapp's AI works best with Superapp Cloud because it is a closed, known system. In a self-hosted environment, custom policies, extensions, versions, functions, and manual changes can affect what the AI can safely understand and manage.
:::

## First identify your situation

### Connect it directly

_New Mac project_

Choose the Supabase project you control, connect it through Superapp, and define the data and access model before inviting users.

### Request a migration

_Existing Superapp Cloud project_

Contact the Superapp team. Existing cloud data and services must be moved as a coordinated migration rather than by changing a URL or key.

### 1. Create or choose a Supabase project

Use a separate project for production. Keep development data isolated while the app changes quickly.

### 2. Connect it in Superapp

Provide the project details through Superapp’s secure connection flow. Never paste service-role secrets into app code or chat.

### 3. Describe access rules

Explain who owns each record and who may read, create, update, or delete it. Verify those rules before adding real users.

### 4. Test the complete backend flow

Create two test accounts and verify sign-in, record ownership, uploads, synchronization, and permission failures before using production data.

:::note
Public app keys are different from server secrets. If you are unsure which credential a field expects, stop and confirm before sharing it.
:::

## Already using Superapp Cloud?

Do not reconnect the app manually. Email [support@superappp.com](mailto:support@superappp.com) with your Superapp account email and project name to request a move to self-hosted Supabase. The team will review the project and coordinate the appropriate migration path.