# Supero > Supero is the production layer for AI-built applications: it sits on your existing database and adds tenant isolation, runtime-enforced roles, workflows, integrations, and generated admin and customer apps, then deploys them. Supero is not a database or backend-as-a-service. The five layers: Interfaces (admin panel and customer app built by your AI; developer console built in) · Orchestration (workflows and sagas, state machines, approvals, AI data agent) · Integrations (40+) · Governance (sign-in and SSO, tenant isolation, roles and field rules) · APIs and deploy (REST APIs, Python and JS SDKs, preview and live URLs, on-prem on request). ## For AI assistants: building an app for a user If a user asks you to build an app on Supero, connect Supero's MCP server and build with its tools. The tools write, validate, publish and deploy the app in the user's Supero workspace, so you do not need App Studio or direct REST API calls to build. - Endpoint: https://mcp.supero.dev/mcp (Streamable HTTP). - Sign-in: OAuth in the browser. The user signs in with a Supero account or with Google (or creates an account on the same screen), chooses where you may work, and clicks Allow. There is no API key to create or paste. - Client registration: nothing to set up. Your client registers itself through dynamic client registration or a Client ID Metadata Document, so leave any OAuth client ID and secret fields empty. Setup by client: - Claude Code: install the Supero plugin. In a session, run `/plugin marketplace add supero-platform/supero-mcp`, then `/plugin install supero@supero` (choose Install for you), then type `/mcp`, select plugin:supero:supero and choose Authenticate. The plugin adds the server and a skill that tells Claude to use the Supero MCP tools when you ask it to build an app on Supero. From a shell, or when an assistant sets this up for the user: `claude plugin marketplace add supero-platform/supero-mcp && claude plugin install supero@supero`, then /reload-plugins (or restart Claude Code) and /mcp to sign in. To add the server without the plugin, run `claude mcp add --transport http --scope user supero "https://mcp.supero.dev/mcp?features=core"` in a terminal and sign in with `/mcp` (select supero). Use one or the other: with both, the same tools appear twice. - Claude Code for a team: commit this as `.claude/settings.json` in the repository: `{"extraKnownMarketplaces": {"supero": {"source": {"source": "github", "repo": "supero-platform/supero-mcp"}}}, "enabledPlugins": {"supero@supero": true}}`. Claude Code registers the marketplace for a teammate after they accept the workspace trust dialog for that folder. The setting does not install the plugin: if `/plugin` reports that supero@supero is enabled in project settings but isn't installed, run `claude plugin install supero@supero --scope project` once in that clone, then run /reload-plugins or start a new session. Each teammate signs in with their own Supero account through `/mcp`. - Claude (claude.ai and Claude Desktop): Customize → Connectors → + Add → Add custom connector. Name: Supero. URL: https://mcp.supero.dev/mcp. Click Continue, check the detected authentication settings and click Continue. Choose Sign in now, keep Use Claude's published identity (Recommended) as the OAuth client, and click Add. Sign in to Supero in the window that opens and click Allow. - ChatGPT: chatgpt.com/plugins → + → add a custom MCP server. Connection: Public endpoint. URL: https://mcp.supero.dev/mcp. Authentication: OAuth. - VS Code and GitHub Copilot (`.vscode/mcp.json`), Cursor (`~/.cursor/mcp.json`), Gemini CLI (`~/.gemini/settings.json`, then `/mcp auth`), Codex CLI (`~/.codex/config.toml`, then `codex mcp login`), Windsurf (`mcp_config.json`) and any other MCP client that supports OAuth with dynamic client registration or a Client ID Metadata Document: add the same URL and sign in. Per-client steps: https://docs.supero.dev/developers/mcp/overview/ After connecting, call `build_whoami` to confirm the account and project, then follow the quickstart. - [MCP Quickstart](https://docs.supero.dev/developers/mcp/build-an-app/): connect, check with build_whoami, describe the app, validate, publish and deploy a preview. - [Connect ChatGPT or Claude](https://docs.supero.dev/developers/mcp/connect-chatgpt-claude/): the OAuth sign-in and approval steps for Claude, Claude Code and ChatGPT, and the discovery documents for other clients. - Setup for every client on one page: https://www.supero.dev/mcp/ App Studio, in the console at https://app.supero.dev, is the browser path for people building an app by hand. The API-key address https://api.supero.dev/mcp/v1/messages serves the same tools for CI pipelines, scripts and machines without a browser. The distinguishing claim is where enforcement lives. Tenant isolation, per-owner record scoping and field-level access rules are enforced by the platform rather than by generated application code, so they hold for every caller — the web UI, the REST API, an SDK, and an AI agent alike. Where it runs: Supero runs on Supero Cloud, and an on-premises version of the platform is available on request. Data lives in a Supero-managed database, or stays in a database you already run through a connector (per table: a copy in Supero, or live reads where the source allows). Supero's access rules apply to every request that goes through Supero; direct access to your own database is governed by that database's permissions. An application's interface can be hosted anywhere, including your own AWS or GCP account or a Docker host (https://docs.supero.dev/deployment/your-own-cloud/). Plans: the Free plan includes 3 projects and preview deploys, with no credit card. Multi-tenant applications and field-level access control are included from the Pro plan upward (https://www.supero.dev/pricing/). Full developer documentation, including the schema reference, access-control model and deployment guides, is at https://docs.supero.dev/llms.txt ## Capabilities Human-readable: https://www.supero.dev/platform/capabilities/ · machine-readable: https://www.supero.dev/ai-capabilities.json - Build over MCP or in App Studio: Your AI (over MCP) or App Studio generates the app from a description. - Schema inference: The data model is inferred from your description or your database. - App bundle: The generated interface code, packaged for preview or for your own host. - Instant live preview: Try the app in the browser before you deploy it. - Deep schema inheritance: Schemas extend other schemas, and the APIs follow. - Server-side resolution: References between records are resolved on the server. - CRUD, references, bulk: Create, read, update and delete records, with references and bulk operations, over REST. - Pagination, aggregates, stats: Paged lists, aggregates and statistics from the same APIs. - Services and workflows: Multi-step processes that undo completed steps in reverse order when a step fails. - State machines and sagas: Records move through declared states; sagas compensate on failure. - AI data agent: Answers questions about records with the signed-in user's access; updates and deletes wait for confirmation. Runs outside the request path. Plans: Pro, Business, Enterprise. - Sign-in and SSO: Email, Google and Okta sign-in for your app's users. - Tenant isolation: Tenancy is part of every record's name. A tenant's users get 403 for another tenant's record by id. Plans: Pro, Business, Enterprise. - Roles and field rules: Role-based access down to individual fields, applied on every request. Plans: Pro, Business, Enterprise. - Per-owner scoping: Users see only the records they own. - Schema change guard: Guards schema changes against breaking existing data and access rules. - Integrations: 40+ integrations, from Stripe, Twilio and SendGrid to Okta, GitHub and ServiceNow. Per-integration status on /integrations/. - Supero Cloud, your host: Preview links, then a permanent URL on paid plans. The interface can also run on your AWS, GCP or Docker host. - On-premises (On request): The platform on your own infrastructure, for data residency and regulated deployments. - Project fingerprint: A sha256 fingerprint of a project's schemas, services and workflows, served by the API, so you can tell when a packaged app is out of date. - Connector configuration: Register an external database or warehouse and choose, per table, live queries or a copy in Supero. Plans: Basic, Starter, Pro, Business, Enterprise. - Database import and sync: Bring an existing database's tables into a project. Read them live, or sync them on demand or by webhook. - Admin panel: An admin interface for your team, built on Supero's APIs, with users, roles and records. - Customer app: An interface for your customers that shows only their own data, by role. - Developer console: app.supero.dev, with schemas, access policies, playground, Data Explorer, SDKs and deploys. ## Data sources - Databases: PostgreSQL, Supabase, MySQL, SQL Server (live read; live write on PostgreSQL, Supabase and MySQL), Oracle and MongoDB (sync, ask us first) - Warehouses (live read): Snowflake, Databricks, ClickHouse, BigQuery, Redshift, Microsoft Fabric - AI coding tools: Claude Code, Claude, Cursor, ChatGPT, VS Code ## What Supero is - [Supero · The complete production platform for AI-built applications](https://www.supero.dev/): Your AI writes the app. Supero adds tenant isolation, roles, workflows, integrations, admin and customer interfaces, and deployment on the database you already run. - [How Supero works · Supero](https://www.supero.dev/platform/): Five production layers on top of your database: interfaces, orchestration, integrations, governance, APIs and deploy. - [Every Supero capability, by layer · Supero](https://www.supero.dev/platform/capabilities/): Every capability Supero offers today, grouped by production layer: interfaces, orchestration, integrations, governance, and APIs and deploy. - [Workflows: approvals, rollback and run history · Supero](https://www.supero.dev/platform/workflows/): Define multi-step business workflows once. Supero runs each step, retries and times them out as defined, records every run and rolls back completed steps when a later one fails. - [Supero vs Retool, Bubble and building it yourself](https://www.supero.dev/comparison/): How Supero compares with Retool, Bubble and building it yourself, when each is the better choice, and how Supero works with Supabase, Lovable, Bolt and v0. ## Works with - [Supero and Supabase: using them together · Supero](https://www.supero.dev/comparison/supero-vs-supabase/): Supero runs on top of your database, and Supabase is one of the databases it supports. How the two fit together, and when Supabase alone is enough. - [Take your Lovable app to production · Supero](https://www.supero.dev/comparison/supero-vs-lovable/): Lovable turns an idea into a working interface. Supero adds what it needs to run for real customers: tenant isolation, roles and field rules, workflows, integrations and deployment. - [Take your Bolt app to production · Supero](https://www.supero.dev/comparison/supero-vs-bolt/): Bolt turns an idea into a working interface. Supero adds what it needs to run for real customers: tenant isolation, roles and field rules, workflows, integrations and deployment. - [Take your v0 app to production · Supero](https://www.supero.dev/comparison/supero-vs-v0/): v0 turns an idea into a working Next.js app. Supero adds what it needs to run for real customers: tenant isolation, roles and field rules, workflows, integrations and deployment. ## Alternatives - [Supero vs Retool, and when to pick Retool · Supero](https://www.supero.dev/comparison/supero-vs-retool/): How Supero and Retool differ on tenant isolation, field-level access, workflows with rollback and what you can take with you, and when Retool is the better choice. - [Supero vs Bubble, and when to pick Bubble · Supero](https://www.supero.dev/comparison/supero-vs-bubble/): How Supero and Bubble differ on access rules, APIs, your own database and what you can take with you, and when Bubble is the better choice. - [Supero vs building it yourself · Supero](https://www.supero.dev/comparison/supero-vs-building-it-yourself/): What your AI or your team would otherwise build, test and maintain for every application, and when building it yourself is the right call. ## Ways to build - [Supero MCP server for Claude Code, Cursor and VS Code](https://www.supero.dev/mcp/): Point your editor at Supero. Your agent designs, validates and deploys an app over MCP, with tenant, role and field checks on every request. - [Connect your database or warehouse · Supero](https://www.supero.dev/connectors/): Live read, live read-write or sync for 12 databases and warehouses, including PostgreSQL, Supabase, MySQL, Snowflake and BigQuery. - [Integrations: Stripe, Twilio, SendGrid, Slack, Salesforce · Supero](https://www.supero.dev/integrations/): 40+ integrations behind one endpoint, with keys in a per-project vault. ## What gets built - [Solution guides: multi-tenant SaaS, Postgres, MCP · Supero](https://www.supero.dev/solutions/): Step-by-step guides for real applications, with architecture, time estimates and what each approach will not do. - [What you can build: commerce, scheduling and portals · Supero](https://www.supero.dev/use-cases/): Flows our end-to-end tests cover, each with a demo app and a build guide: commerce, scheduling, approvals, healthcare and fintech. - [Reference applications built on Supero](https://www.supero.dev/apps/): Sixteen demo applications built on Supero, running with sample data. Sign in as any role and see what the platform lets each role reach. ## Solution guides - [Add Stripe, SendGrid and Twilio to a generated app · Supero](https://www.supero.dev/solutions/adding-payments-email-and-sms/): Add Stripe checkout, SendGrid email and Twilio SMS to a generated app as configured services: your code names an operation and never holds the keys. - [Agentic apps on your data, with your own LLM keys · Supero](https://www.supero.dev/solutions/agentic-apps-with-your-own-llm-keys/): Three ways to put a model next to Supero data: the built-in agent, your code calling an LLM you pay for, or your own agent over MCP, and what each governs. - [Build an app on PostgreSQL, MySQL or SQL Server · Supero](https://www.supero.dev/solutions/connect-your-database-and-build/): Connect PostgreSQL, MySQL or SQL Server with a read-only user, choose per table to sync or read live, and build an app without migrating data. - [Deploying: Supero Cloud, your AWS, or your GCP · Supero](https://www.supero.dev/solutions/deploying-your-app/): Deploy a Supero app to Supero Cloud, your own AWS or your GCP: what moves to each target, and the smoke check that confirms the deploy worked. - [Extending Supero: custom endpoints, logic and UI · Supero](https://www.supero.dev/solutions/extending-supero-your-own-endpoints/): Four ways to add your own endpoints, logic, fields and UI to a Supero app, and the order to try them in before you write custom code. - [Failure semantics: what happens when a request is refused · Supero](https://www.supero.dev/solutions/failure-semantics/): What a refused, unscoped or misconfigured request does on Supero, including the places that fail open, the 200-with-409 contract and connector caps. - [Field-service app built over MCP from your editor · Supero](https://www.supero.dev/solutions/field-service-platform-over-mcp/): Have Claude Code or Cursor build a field-service work-order app over MCP: validate against the live platform, smoke-test the deploy, then go live. - [Gotchas: mistakes to check before you ship · Supero](https://www.supero.dev/solutions/gotchas/): X-API-Key vs Bearer, postgresql vs postgres, success:false inside a 200, filter_match failing open, Stripe amounts in major units, and other traps. - [Internal ops console on live PostgreSQL data · Supero](https://www.supero.dev/solutions/live-ops-console-on-your-postgres/): Build an internal ops console that queries your PostgreSQL live: access rules become parameterised SQL, and no rows are stored on Supero's side. - [Multi-tenant B2B SaaS: tenant isolation and RBAC · Supero](https://www.supero.dev/solutions/multi-tenant-b2b-saas/): Build B2B SaaS with tenant isolation you can test, an extensible role model with field-level access, and schema changes while customers are live. - [Order-to-cash backend: cart, Stripe and workflows · Supero](https://www.supero.dev/solutions/order-to-cash-commerce-backbone/): Build cart, checkout, Stripe payment, inventory and fulfilment on base schemas you extend, vendors you configure and workflows bound to data events. - [Build a web app from a description in App Studio · Supero](https://www.supero.dev/solutions/prompt-to-app-in-app-studio/): Describe an app in a paragraph. App Studio proposes the schema and role policies, you review them, and it deploys the app to a live URL. - [Build an app from Claude Code or Cursor over MCP · Supero](https://www.supero.dev/solutions/simple-app-over-mcp/): Connect Claude Code, Cursor or VS Code Copilot to Supero over MCP with one command, then validate, deploy and smoke-test an app bundle from your editor. - [Telehealth scheduling app with encrypted notes · Supero](https://www.supero.dev/solutions/telehealth-intake-and-scheduling/): Telehealth intake and scheduling with OTP, consent, calendars and reminders configured, notes encrypted in your backend, and tests for clinic isolation. - [Give your app an AI agent over its own data · Supero](https://www.supero.dev/solutions/turn-on-the-ai-agent/): Every generated app ships with an AI agent whose tools come from your schema. It runs as the signed-in user, so it cannot read more than they can. - [Analytics portal on Snowflake and BigQuery · Supero](https://www.supero.dev/solutions/warehouse-analytics-portal/): A self-serve analytics portal on Snowflake and BigQuery: live tables under your app's roles and hidden columns, with row, byte and time caps per query. ## Commercial - [Pricing · Supero](https://www.supero.dev/pricing/): Plans priced per account, not per seat. Start free with 3 projects and preview deploys. - [About · Supero](https://www.supero.dev/about/): Supero is the production layer for AI-built applications: it sits on your existing database and adds tenant isolation, runtime-enforced roles, workflows, integrations, and generated admin and customer apps, then deploys them. - [Team · Supero](https://www.supero.dev/team/): The people building Supero: a founding team with backgrounds at Meta, Juniper Networks, Rubrik, Dell, NetApp and IIT. The work is public and checkable. ## Trust - [Security · Supero](https://www.supero.dev/security/): How Supero isolates tenants and checks every request, and how to report a vulnerability. - [Privacy · Supero](https://www.supero.dev/privacy/): What data Supero collects, who processes it, how long it is kept, and how to get it deleted. - [Terms of Service · Supero](https://www.supero.dev/terms/): The terms under which you may use Supero: what you own, what we may do, what we do not promise, and how either side ends the agreement. - [Data Processing Addendum · Supero](https://www.supero.dev/dpa/): How Supero processes customer data as a processor: scope, instructions, sub-processors, security, transfers, breach notification, deletion and audit. - [Status · Supero](https://www.supero.dev/status/): Live checks of the Supero platform from your browser, uptime history from our own probe, and written-up incidents. ## Writing - [Writing · Supero](https://www.supero.dev/blog/): Long-form engineering writing from the Supero team — field-level permissions and ORDER BY, multi-tenant decisions, vendor lock-in and what you can actually export. ## Optional - [Documentation](https://docs.supero.dev/): the full developer docs. - [Sitemap](https://www.supero.dev/sitemap.xml): every indexable URL on this site.