All features

Stage 05 · Backend

A backend that keeps your secret keys out of the app

Each app gets its own Supabase backend, rendered from the spec. When the app uses AI, the calls go through a Supabase edge function that holds the provider key, the limits are checked on the server and usage is recorded there.

12 tools in this stage127 in the whole pipelineFor Claude Code, Codex CLI, Gemini CLI and Cursor

The job it replaces

Hours of busywork, gone

Doing it by hand

  • API keys baked into the app binary
  • Free users burning paid AI calls with no server side limit
  • Privacy and terms pages written and hosted by hand

With AppFactory

  • A Supabase project per app with anonymous sign in, and Sign in with Apple linked to the same user
  • Free use and daily limits enforced on the server, with clear answers the app acts on: show the paywall, cap reached, consent needed or try again
  • Privacy and terms pages served in every app language and verified live

What the agent does

Step by step

  1. Render it from the spec

    Migrations, edge functions, limits and legal sources are rendered offline from the spec, trimmed to the app's monetization mode.

  2. Create the project

    A new Supabase project in your own organization.

  3. Plan, then deploy

    The deploy is a dry run by default and returns the plan without a single call. The live deploy runs migrations, secrets, auth, the legal build and the edge functions.

  4. Proxy the AI

    Only if your app uses AI: the provider key is stored as a server side secret for the edge function, never in the app.

  5. Publish the legal pages

    Privacy and terms are filled from the spec, anything still blocking is listed, and every deployed page is checked in each app language for your support email and leftover placeholders.

  6. Keep secrets server side

    Edge function secrets are written on the server. The service role key is saved in a private file on your Mac and never returned to the agent.

What you get

At the end of this stage

  • A deployed Supabase backend for the app
  • Usage limits enforced on the server
  • Privacy and terms URLs that work in every app language
  • An AI proxy, only when the app needs one

Where it stops for you

  • Creating a project, running SQL, setting secrets and deploying all wait for your approval.
  • You enter your service keys on a local page that opens on your Mac, or in your agent's MCP settings, never in the chat.

Every stage, in one purchase

Founding members pay $99 once, every update included. Only 10 seats at this price, then $149.