---
title: "Superapp Cloud"
description: "Add managed authentication, data, storage, and APIs without infrastructure setup."
---
Superapp Cloud is the managed backend built into Superapp. It supports app features that need accounts, shared data, synchronization, file storage, or trusted server-side work without requiring you to deploy and maintain the infrastructure yourself.

## The default backend on Superapp Web

Web projects use Superapp Cloud as their standard backend path. You describe the product behavior and data rules in the same workspace where you build the app; Superapp handles the managed cloud setup behind that experience.

## Why AI works better with Superapp Cloud

Superapp Cloud is a closed, managed system with a backend structure the Superapp AI already understands. The AI knows how authentication, data, storage, permissions, and server-side operations fit together, so it can make coordinated changes instead of guessing how a custom environment is configured.

-   The available services and supported patterns are known in advance.
-   Configuration stays consistent between the app and its backend.
-   Schema and access-rule changes can be planned together.
-   There are fewer custom settings, versions, and external modifications to diagnose.

:::tip
For the most reliable AI building experience, use Superapp Cloud. Self-hosted Supabase is intended for teams that need direct infrastructure control and are comfortable owning the additional configuration.
:::

## What it provides

-   **Authentication:** accounts and sessions for identifying app users.
-   **Database:** durable records that can synchronize between devices.
-   **Storage:** uploaded images, documents, audio, and other user files.
-   **Access rules:** control over who may read or change each kind of data.
-   **Server-side work:** trusted logic for integrations, private keys, and incoming events.

## Model the product before the tables

Explain what each person creates, what must persist, and who can see or change it. Superapp can translate those product rules into a data model and protected operations.

```
Add accounts and shared training plans.

Coaches create and edit plans for athletes assigned to them.
Athletes can read their own plans and mark workouts complete, but cannot edit the plan itself.
Keep progress synchronized across iPhone and Mac.
```

## Make access explicit

Treat data as private unless the product requires sharing. Define ownership for every record, check permissions on the backend, and test with two separate accounts. Hiding a button in the interface does not prevent an unauthorized request.

## Using Superapp for Mac

Mac projects can use Superapp Cloud for the managed experience or connect to a self-hosted Supabase project. Choose self-hosting when you need direct infrastructure ownership, custom operations, or an environment already managed by your team.

### Choose Superapp Cloud

_Managed_

Best AI results and the shortest path from product requirements to a working backend.

### Choose Supabase

_Self-hosted_

Best when your team wants to operate the database and backend environment directly.

## Move an existing project to self-hosted Supabase

An existing Superapp Cloud project may already depend on managed authentication, database tables, access policies, storage, and server-side logic. Moving only the app's connection details can separate it from those services or expose data incorrectly.

This migration is therefore handled by the Superapp team on request. Contact [support@superappp.com](mailto:support@superappp.com) from the email associated with your account. Include the project name and why you want to self-host, but do not send passwords, service-role keys, or other private credentials by email.

:::tip
Connecting a new Mac project to Supabase and migrating an existing Superapp Cloud project are different workflows. Use the normal connection flow only for a new project or when the Superapp team instructs you to do so.
:::

## Work carefully with live data

Separate development and production data, test schema and permission changes before release, and back up important records before destructive operations. Use server-side secrets for privileged integrations and never ship them inside the app.

:::note
A local-only app may not need Superapp Cloud at all. Read [Do you need a backend?](/backend) before adding accounts or shared infrastructure to an early prototype.
:::