Cloud Overview

Swarmz Cloud is a fully managed backend that ships with every project. Flip on the Cloud tab in the project editor and you get a Postgres database, an auth system, file storage, server-side edge functions, and realtime subscriptions — provisioned automatically and presented as Swarmz primitives. The agent has direct access to all of it, so you can describe schemas and policies in chat and it writes the migrations and queries to match.

Under the hood, Cloud is built on Supabase. You don't need to know that to use it — the Cloud tab, the agent tools, and the supabase JS client in your project handle everything. But if you outgrow the managed setup, you can also bring your own Supabase project.

What you get

Every Cloud-enabled project includes:

Each primitive has its own page — Database, Authentication, Storage, Edge Functions, and Realtime — that walks through what the agent can do and how to call it from your app.

Two modes

Swarmz Cloud runs in one of two modes per project. Pick whichever fits.

Whitelabel Swarmz Cloud (default)

We provision a managed Postgres project on your behalf when you enable the Cloud tab. You never see Supabase, never sign in to a separate dashboard, and never paste credentials. The project is created in our org via the Management API, the connection details are stored against your project, and the agent talks to it directly through supabase-proxy for SQL, schema, and admin operations.

This is the default for new projects. Use it when you want zero setup and a single billing relationship with Swarmz.

Bring-Your-Own Supabase

If you already have a Supabase project — production data, custom extensions, a paid plan — you can connect it via OAuth instead. From Settings → Integrations → Supabase, click Connect, authorize through Supabase, then pick the organization and project to link.

After linking, the agent can read your schema, write migrations, configure auth, and deploy edge functions to your project. Your Supabase plan and billing stay with Supabase; only the Swarmz agent activity counts against your Swarmz plan.

When to use Cloud vs. roll your own

Use Cloud when you want:

• A backend wired up in seconds with no separate signups
• The agent to write migrations, RLS policies, and queries that match your real schema
• Auth, storage, edge functions, and realtime under one roof
• Live preview to talk to a real database, not a mock

Roll your own when you need:

• A backend that lives somewhere we don't manage (a self-hosted Postgres, a different cloud)
• Tight coupling to an existing system that pre-dates Swarmz
• A stack we don't yet integrate with (use a regular HTTP integration instead)

The trade-off with Whitelabel Cloud is that you don't directly own the underlying Supabase project. If you ever want to take the data and run, you can export the database via the Cloud tab or eject to a BYO Supabase setup — your code keeps working because the supabase JS client is the same on both sides.

Pricing

Cloud usage rolls into your Swarmz plan's allowance for now. Free, Pro, and Business plans all include Cloud at no extra cost — see Plans for the credit allotments.

Heavy users may hit per-resource caps:

• Database size — soft limits per plan (see Database)
• Connection count — concurrent Postgres connections
• Storage — total bucket size in GB
• Function invocations — edge function calls per month

When you hit a cap, the dashboard surfaces a banner with the option to top up or upgrade. Top-ups are USD, charged from your workspace balance, and apply only to Cloud resources.

Where to next

• Database — Postgres schemas, queries, RLS, migrations
• Authentication — sign-in flows, providers, sessions
• Storage — buckets, uploads, signed URLs
• Edge Functions — server-side TypeScript on Deno
• Realtime — subscribing to row changes
• Supabase integration — connecting a Supabase project you already own

Want to provision Cloud programmatically? See the projects API for creating a project with Cloud enabled from the start.