Early access

Apply

Documentation
Documentation/Start here/What Supero adds to your app

What Supero adds to your app

Supero sits on your existing database and adds five layers to the app your AI builds: interfaces, orchestration, integrations, governance, and APIs and deploy. This page summarises each layer and links to the docs for it.

Overview

Supero is the production layer for AI-built applications. Your AI builds the app over MCP or in App Studio, and Supero supplies the layers underneath it, on top of your existing database or a fresh managed one. Each section below covers one layer in a few sentences and lists the pages that go into detail.
The full capability list, with plan availability for each row, is on Supero capabilities.

Interfaces

Every generated app has an admin panel for your team, with users, roles and records, and a customer app that shows each customer only their own data, by role. Your AI builds both on Supero's APIs. The developer console at app.supero.dev is built into every project and holds schemas, access policies, the playground, Data Explorer, SDKs and deploys.

Orchestration

Workflows run multi-step processes and undo the completed steps in reverse order when a later step fails. Records move through the states you declare, and sagas compensate on failure. The AI data agent answers questions about records with the signed-in user's access, and any update or delete it proposes waits for confirmation.

Integrations

Supero has 40+ integrations, from Stripe, Twilio and SendGrid to Okta, GitHub and ServiceNow. The status of each one is listed on the integrations page.

Governance

Tenancy is part of every record's name, and a tenant's users get a 403 for another tenant's record when they ask for it by id. Role-based access goes down to individual fields and is applied on every request. Your app's users sign in with email, Google or Okta.

APIs and deploy

Your schemas get REST APIs to create, read, update and delete records, with references, bulk operations, paged lists, aggregates and statistics, plus Python and JavaScript SDKs. A deploy starts as a preview link and moves to a permanent URL on paid plans, and the interface can also run on your own AWS, GCP or Docker host. Running the platform itself on your own infrastructure is available on request.

Next Steps