# Supero > Supero turns a declared schema into a production multi-tenant backend: REST APIs, typed SDKs, RBAC with field-level access control, workflows, connectors to databases you already run, and an MCP server so an AI editor can build against it directly. Tenant isolation, per-owner record scoping and field-level access rules are enforced by the platform rather than by application code. Apps deploy to Supero Cloud, your AWS, or your GCP. ## Getting Started - [Create Your Account](https://docs.supero.dev/getting-started/create-your-account/): Sign up for Supero in a browser: what the form asks for, how email verification works, what a new account actually contains, and what to do in the first ten minutes. - [What is Supero](https://docs.supero.dev/getting-started/what-is-supero/): Supero turns a plain-language description of your app into a deployed, full-stack product: a data model, a staff admin console, a customer-facing web experience, and the REST API and SDKs behind it. - [Quick Start](https://docs.supero.dev/getting-started/quick-start/): Register a domain, create a project, upload a schema, and start reading and writing data through the Supero REST API (and the Python SDK) in a few minutes. - [Core Concepts](https://docs.supero.dev/getting-started/core-concepts/): The vocabulary and data model every Supero app is built on: the Domain/Project/Tenant hierarchy, namespaces, schemas, records, and how roles map to the generated UI. ## Building Your App - [Build Your First App (App Studio)](https://docs.supero.dev/building-your-app/ai-assistant/): How App Studio turns a plain-English description into a running, deployable app: describe it, review the generated backend, choose a UI, generate, and publish to a supero.live address — including which plans include a live deployment, and what to do when a step fails. - [Anatomy of a Supero App](https://docs.supero.dev/building-your-app/app-anatomy/): A Supero app is a directory bundle with a fixed shape: a handful of files you author, and a UI runtime the SDK generates for you on every run. This page maps every file so you know exactly what to edit and what to leave alone. - [Schema Reference](https://docs.supero.dev/building-your-app/schema-design/): How data models are defined in Supero: the attributes[]/references[] schema format, system fields, the domain-project-tenant hierarchy, namespaces, and schema inheritance via extends. - [Managing Data](https://docs.supero.dev/building-your-app/managing-data/): Create, read, update, and delete records through the CRUD API, the Python SDK, or the JavaScript client available in your app's frontend code. - [Files & Media](https://docs.supero.dev/building-your-app/files-and-media/): Uploading, fetching, replacing and deleting files: the exact request and response shapes, size and type limits, thumbnails, how a record points at a file rather than containing it, who can read one — and why a record export does not include your attachments. - [Transactional Services](https://docs.supero.dev/building-your-app/transactional-services/): Prebuilt backend capabilities — cart, order, payment, booking, membership, and more — with a real state machine, idempotency guarantees, and a single wire primitive: POST /api/v1/services/execute. - [Subscriptions & Memberships](https://docs.supero.dev/building-your-app/subscriptions-and-memberships/): Compose recurring billing and access/role membership for your app's own users from two platform services — recurring_plan and membership — plus your own schema, a billing loop, and Stripe Checkout for sign-up. - [Workflows & Automation](https://docs.supero.dev/building-your-app/workflows-and-automation/): Chain email, SMS, billing calls, and CRUD writes into declarative, auditable multi-step flows that run on their own — triggered directly, or fired automatically when your data changes. - [AI Data Agent](https://docs.supero.dev/building-your-app/ai-agent/): Every generated app ships with a chat your end users can ask about their own records — and act on them. It runs as the signed-in user, needs no API key, and is on by default. - [Dynamic UI](https://docs.supero.dev/building-your-app/dynamic-ui/): How Supero turns your schema into working tables, forms, and detail views automatically, and the real UI-schema mechanism you use to customize labels, view modes, per-field renderers, and conditional form fields. - [Field Encryption](https://docs.supero.dev/building-your-app/field-encryption/): How to encrypt sensitive field values yourself before they reach Supero, what Supero seals on your behalf and under what condition, and what to expect when you query encrypted data. - [Marketplace: Publish, Import & Personalize](https://docs.supero.dev/building-your-app/marketplace/): How Marketplace listings work — browsing, importing, publishing from a project or an uploaded bundle, and versioning — and which of it the dashboard offers no entry point for today. - [Support & Ticketing](https://docs.supero.dev/building-your-app/support-and-ticketing/): Build a helpdesk on the ticket transactional service: the base_ticket lifecycle, its five operations, and how to compose it with comment, attachment, notification, and approval for a full support flow. - [Email & Notifications](https://docs.supero.dev/building-your-app/email-and-notifications/): Send transactional email through SendGrid or your own SMTP server, push in-app notifications through their own queued → sent → seen lifecycle, and wire both into workflows so a data change can email, alert, and acknowledge on its own. - [Going to Production](https://docs.supero.dev/building-your-app/going-to-production/): The checklist to run before real customers touch your app: rotate the seeded credentials, close the permissive defaults, confirm which tenant your customers are in, and check your plan before launch day. ## Managing Your App - [Projects & Tenants](https://docs.supero.dev/managing-your-app/projects-and-tenants/): How to create, list, and manage the Project and Tenant levels of your account hierarchy day to day — and how to avoid the 'tenant' naming overload. - [Building Multi-Tenant Apps](https://docs.supero.dev/managing-your-app/building-multi-tenant-apps/): How Supero's Domain -> Project -> Tenant hierarchy gives every app you build tenant isolation for free, and how to provision, staff, and customize tenants through the API. - [Users & Roles](https://docs.supero.dev/managing-your-app/user-management/): Create and manage user accounts, assign built-in and custom roles, and understand how sessions and role-assignment limits work in Supero. - [Access Control (RBAC)](https://docs.supero.dev/managing-your-app/access-control/): How Supero's two-layer RBAC model works: coarse role permissions plus fine-grained, per-schema access policies you configure without writing code. - [Roles & Permissions Reference](https://docs.supero.dev/managing-your-app/roles-and-permissions/): The real, closed set of Supero roles — hierarchy, scope, who can assign what, custom-role relabels, permission strings, and every sign-in/account flow. - [Access Policies (Entity, Record & Field)](https://docs.supero.dev/managing-your-app/access-policies/): The full reference for object-level access policies: how access_policy and access_rule records restrict a role per schema entity, per record (owner-scope), and per field, with no application code. - [The Admin Panel](https://docs.supero.dev/managing-your-app/admin-panel/): The in-console Admin Panel page and its Manage Records operator view — what's on them, who can reach them, and how they carry over unchanged to your deployed app. - [Admin vs Customer Views](https://docs.supero.dev/managing-your-app/app-admin-and-customer-views/): Every generated Supero app ships one bundle that renders two different experiences — an operator admin shell and a task-oriented customer view. Here's exactly what each one shows, and how the split is decided. - [Security](https://docs.supero.dev/managing-your-app/security/): How Supero authenticates requests, isolates your tenants' data, and gives you the building blocks — access control, client-side field encryption, and audit logging (being rebuilt) — to protect what you build. - [Compliance & Trust](https://docs.supero.dev/managing-your-app/compliance-and-trust/): An honest answer to the questions a security review asks: which legal documents exist and where to read them, what Supero is and is not certified for, where your data lives, how to report a vulnerability, and which questions this page deliberately does not answer. - [Plugin Registry](https://docs.supero.dev/managing-your-app/plugin-registry/): Register your own external HTTP endpoint as a domain-scoped plugin, then call it through Supero with centralized credential storage, automatic retries, and a circuit breaker. - [Continuity & Exit](https://docs.supero.dev/managing-your-app/continuity-and-exit/): What you own, how to get your source and your data out, what you would have to replace if you left, and what does not exist yet. Written for the security review, not the sales deck. ## Connectors - [Connectors Overview](https://docs.supero.dev/connectors/overview/): Connect an external database, warehouse, file store, REST API, or webhook to a Supero project. Choose whether Supero copies the data in or reads it live at query time — your app talks to it through the exact same CRUD and query API either way. - [Database Connectors](https://docs.supero.dev/connectors/databases/): Bring your own PostgreSQL, Supabase, MySQL, SQL Server, Oracle, or MongoDB database into Supero — sync data into a managed schema, or read it live without copying a single row. - [Warehouse Connectors](https://docs.supero.dev/connectors/warehouses/): Connect Snowflake, BigQuery, Databricks, ClickHouse, Redshift, or Microsoft Fabric as a live, read-only data source — no copy job, no sync schedule. Query it through the normal CRUD API or run ad-hoc analytical SQL through the Query console. - [File, HTTP API, Webhook & Public Catalog](https://docs.supero.dev/connectors/files-apis-webhooks/): Connect Supero to flat files on S3/SFTP/a URL, poll any REST API, receive verified inbound webhooks, or one-click add a curated public API — the connector plugins that move data over plain HTTP or object storage instead of a database driver. - [Live Data, Read-Only & Security](https://docs.supero.dev/connectors/security/): The security model behind live (BYODB) connectors: how read-only and write-through are enforced, how multi-tenant sources stay isolated, how source credentials are protected, and how every query is validated before it reaches your database or warehouse. ## Integrations - [API Integrations](https://docs.supero.dev/integrations/api-integrations/): Connect third-party services — email, SMS, chat, payments, CRM, dev tools, cloud storage, and more — to your Supero app through one managed API. Wire your own custom HTTP endpoints when the catalog does not cover a provider yet. - [Webhooks & Events](https://docs.supero.dev/integrations/webhooks/): How external systems push events into Supero — payment and messaging provider callbacks through the managed services catalog, and inbound triggers for your own connectors. Read the verification table before you rely on a callback: signature checking is built in for four providers, not for the whole catalog. - [Managed Integrations & Provider Catalog](https://docs.supero.dev/integrations/managed-integrations/): Browse and wire up dozens of managed third-party providers — payments, messaging, identity, and data services — through one import, configure, execute lifecycle instead of hand-rolling an HTTP client for every vendor. ## Deployment - [Choosing a Deployment Option](https://docs.supero.dev/deployment/overview/): Two separate decisions hide under the word "deploy" — where your generated app UI runs, and whether you want to self-host the whole Supero platform. This page walks through both. - [Publish Your App (Go Live / Supero Cloud)](https://docs.supero.dev/deployment/cloud-deployment/): Go Live publishes your generated app to a permanent, Supero-hosted URL — no cloud account, no infrastructure to configure. This page covers the Supero Cloud path: how preview and live differ, how long a preview lasts, what the deploy contract is, and how to take an app back offline. - [Custom Domains](https://docs.supero.dev/deployment/custom-domains/): Pointing your own domain at a deployed Supero application is not self-service today. This page explains what a published app's address actually is, what the custom-domain fields in settings are really for, and how to arrange a branded address. - [Deploy to Your Own AWS or GCP](https://docs.supero.dev/deployment/your-own-cloud/): Run your app's UI in your own AWS or GCP account, on your own cloud bill, while your data and business logic stay on Supero's backend. The Connect and Deploy flow for both clouds, exactly what each grant allows, how to verify a deploy, and how to tear it down. - [Deploy to AWS / GCP — Verification Runbook](https://docs.supero.dev/deployment/aws-gcp-verification-runbook/): A hands-on runbook: build an app in App Studio, hit Go Live, ship its UI to your own AWS or GCP account with one command, and verify the deploy actually works. Your data stays in Supero. - [On-Premise Deployment](https://docs.supero.dev/deployment/on-premise/): Run the entire Supero platform — API, data, and admin console — on infrastructure you control, then deploy your apps against it. No cloud account, no phone-home. - [On-Prem Add-On Packages](https://docs.supero.dev/deployment/on-prem-add-ons/): Add live database connectors, the integrations catalog, or a self-hosted AI agent to an on-premise Supero backend — each ships as a separate package that stays off until it is installed and licensed. ## Account & Billing - [Workspace, Domains & Tenants](https://docs.supero.dev/account/workspace/): What your Supero workspace actually is, how the Domain -> Project -> Tenant hierarchy fits together, and how to register a domain, scope API keys, add team members, and turn on sub-tenant multi-tenancy or SSO as you grow. - [Plans & Billing](https://docs.supero.dev/account/plans-and-billing/): How Supero plans, Power usage, storage, add-ons, and quotas work, and how to read your usage from the billing API. ## Start Here - [Solutions Overview](https://docs.supero.dev/solutions/overview/): Ten reference architectures you can build on Supero, plus two worked case studies. Each one names the object types involved, the platform services it leans on, and the page that takes you further. - [Ways to Build](https://docs.supero.dev/solutions/ways-to-build/): Supero gives you five ways into building an application. They all end in the same place — a multi-tenant app with access control and an admin panel, running on your database or ours. Pick the one that matches how you already work. ## Foundations - [Connect Your Database](https://docs.supero.dev/solutions/connect-your-database/): Register the tables in a database you already run as object types in a Supero project, then read them where they are — synced into the platform store, or served live from the source on every request. - [External Integrations](https://docs.supero.dev/solutions/external-integrations/): Payments, email, SMS, object storage, calendars and LLM keys, invoked through one endpoint — with the credentials held in the platform keystore instead of your application code. - [Workflow Orchestration](https://docs.supero.dev/solutions/workflow-orchestration/): A record changes, a workflow runs, and services fire in a defined order — with the definition stored as an ordinary record and every step written to a log you can query. ## Application Architectures - [Online Storefront](https://docs.supero.dev/solutions/storefront/): One seller, one catalog, many buyers. Product types that extend product:base_product, a cart that converts into an order, and a payment record that tracks the money — assembled from platform base types rather than written from scratch. - [Multi-Vendor Marketplace](https://docs.supero.dev/solutions/marketplace/): Two audiences on one dataset: sellers who list and shoppers who buy, both modelled by extending customer:base_customer, with one catalog type that references its seller. What the platform provides, and where the two-sided economics remain yours. - [Appointment & Service Booking](https://docs.supero.dev/solutions/service-booking/): A priced service catalog, a set of staff who deliver it, and appointments that move through a real state machine — requested, confirmed, completed, cancelled, no_show. What the appointment service handles, and why contention is still your problem. - [Membership & Recurring Billing](https://docs.supero.dev/solutions/membership-billing/): Plans, subscriptions and payments modelled on the platform's recurring_plan, membership and payment base types. Worked from a real 39-schema gym application. - [Events & Ticketing](https://docs.supero.dev/solutions/events-ticketing/): Events with tiered, priced admission, a cart that sells several tickets in one transaction, and a booking record per ticket held. Where the base types fit cleanly, where the fit is loose, and why capacity is a number you check rather than a limit the platform holds. - [Warehouse-Backed Reporting](https://docs.supero.dev/solutions/warehouse-reporting/): Register tables from Snowflake or Databricks as read-only object types, then read them through the same governed CRUD surface as the rest of your application. From a real 18-schema Databricks bundle. - [Approvals & E-Signature](https://docs.supero.dev/solutions/approvals-compliance/): Multi-step approval chains, signed documents, and the audit trail around them — built on the approval and document_signature base types, from a real 22-schema clinical trial application. ## Case Studies - [Multi-Tenant Issue Tracker over MCP](https://docs.supero.dev/solutions/case-study-issue-tracker/): Ten object types, authored from an AI editor over MCP, serving every customer from one deployment — and the permission error that only appeared when a real user tried to file a bug. - [A Subscription Business, End to End](https://docs.supero.dev/solutions/case-study-subscription-gym/): IronWorks Three — 39 schemas, sixteen platform services, and a workflow that fires the moment a class is booked. Including the billing loop the platform does not run for you. ## Resources - [Contact & Links](https://docs.supero.dev/resources/contact/): Where to reach the Supero team, where the product lives, and where to follow along. ## Platform Overview - [Architecture](https://docs.supero.dev/developers/overview/architecture/): The mental model you need before integrating: one public API host, how a request is authenticated and scoped, how the schema drives everything downstream, and how tenant isolation is enforced. - [Platform Concepts](https://docs.supero.dev/developers/overview/platform-concepts/): The core mental model behind Supero: how domains, projects, tenants, and namespaces isolate your data, how schemas drive the API, and how roles and policies control access. - [Operations & Observability](https://docs.supero.dev/developers/operations-and-observability/): What Supero records, where each kind of record is read from, how to follow one request across the whole platform, what to check when something fails — and, stated plainly, which observability surfaces do not exist so you can plan to build them yourself. - [Debugging & Troubleshooting](https://docs.supero.dev/developers/debugging/): The one skill that matters most on Supero: telling apart responses that look identical but mean different things. A 200 with an empty list has four causes; a connector run that says completed has four more. This page is the probe for each — what to check to know which one you are looking at. ## API Reference - [API Overview & Conventions](https://docs.supero.dev/developers/api-reference/overview/): The conventions every Supero REST endpoint follows: one base URL, two route families, two auth schemes, and one response envelope. Read this before any individual endpoint reference. - [Authentication](https://docs.supero.dev/developers/api-reference/authentication/): How to authenticate against the Supero API with a login-issued JWT or a long-lived API key, and how to manage token lifecycle. - [OpenAPI Export & Developer Tools](https://docs.supero.dev/developers/api-reference/openapi-and-tools/): Export a machine-readable OpenAPI 3.0.3 document for your schemas, try endpoints in the playground, and hand the spec to a frontend generator. The console's developer tools, and the four things the spec tells a code generator that it would otherwise get wrong. - [CRUD Endpoints](https://docs.supero.dev/developers/api-reference/crud-endpoints/): The auto-generated Create, Read, Update, and Delete endpoints every schema type gets on api.supero.dev, plus bulk reads, rich queries, and batch writes. - [Querying & Pagination](https://docs.supero.dev/developers/api-reference/querying-and-pagination/): How to filter, sort, page through, and aggregate CRUD data across GET list, POST /list-bulk, and POST /query — plus references and fully-qualified-name resolution. - [Errors & Status Codes](https://docs.supero.dev/developers/api-reference/errors-and-status-codes/): Every status code the Supero API returns and what it actually means here, the error body shapes, the error_code values worth branching on — and the failures that come back as 200. - [Rate Limits & Quotas](https://docs.supero.dev/developers/api-reference/rate-limits/): How Supero limits traffic: the per-surface request-rate limits and their 429 contract, the plan quota system and its 402 contract, and the per-request size and count limits that apply to every caller. - [Schema API](https://docs.supero.dev/developers/api-reference/schema-api/): Create, validate, read, update, and delete schema definitions over REST — the same operations the dashboard, CLI, and AI Assistant use under the hood. - [Domains, Projects & Tenants API](https://docs.supero.dev/developers/api-reference/tenant-api/): Reference for the account hierarchy Supero is built on -- Domain, Project, and Tenant -- and the REST endpoints for registering a domain and managing tenant lifecycle. - [Plugins API](https://docs.supero.dev/developers/api-reference/plugins-api/): REST API reference for the Plugin Registry — register your own HTTP endpoint as a project-scoped plugin, invoke it through the platform gateway, and monitor its health. - [AI Agent API](https://docs.supero.dev/developers/api-reference/ai-agent-api/): Talk to your domain's data in natural language: the AI Data Agent turns your uploaded schemas into callable tools, runs a reasoning loop over them, and returns structured results — as a single response or a live SSE stream. - [Billing & Usage API](https://docs.supero.dev/developers/api-reference/billing-usage-api/): Read-only endpoints for pulling your domain's current-period usage, plan catalog, prepaid Power-credit wallet, and add-on catalog into your own dashboards or alerts. ## SDK - [Python SDK](https://docs.supero.dev/developers/sdk/python-sdk/): The official Python client for Supero — a synchronous library that wraps the REST API with a connected "org" object, a fluent query builder, schema upload, and file handling. - [JavaScript SDK](https://docs.supero.dev/developers/sdk/javascript-sdk/): The Supero JavaScript SDK (@supero/js-lib) is a Node.js client for authenticating, running CRUD, and calling platform services against api.supero.dev. - [Custom / Per-Domain SDK](https://docs.supero.dev/developers/sdk/custom-sdk/): Generate a typed Python or JavaScript client library from your own domain's schemas, and manage its versions through the SDK Generation API. - [Build an App with Your Own AI Agent](https://docs.supero.dev/developers/build-with-ai-agent/): Use your own coding agent (Claude Code, Cursor, or similar) to author a full Supero app locally, then validate, publish, and deploy it over the Supero MCP server. - [GitHub Resources & Sample Apps](https://docs.supero.dev/developers/github-resources/): The open sample applications: nineteen production-shaped apps across industry verticals, each with its schemas, setup, tests and editor rules — readable, clonable, and the fastest way to see how a real Supero app is put together. ## CLI Reference - [CLI (App Runner)](https://docs.supero.dev/developers/cli/commands/): The supero command line tool that sets up and runs a generated Supero app on your machine — not a general-purpose account/management CLI. ## MCP - [Connect Your AI Editor over MCP](https://docs.supero.dev/developers/mcp/overview/): Point Claude Code, Cursor, or GitHub Copilot at Supero's MCP server and build, validate, publish, and deploy real Supero apps without leaving your editor. - [Build an App over MCP](https://docs.supero.dev/developers/mcp/build-an-app/): The end-to-end path: mint a correctly scoped API key, connect your editor, drive a build through the build_* tools, and deploy — either a short-lived preview or a permanent one. - [MCP Tools & Protocol Reference](https://docs.supero.dev/developers/mcp/tool-reference/) - [MCP Integration Services](https://docs.supero.dev/developers/mcp/integration-services/): How a generated app calls external MCP tool servers (services.mcpClient) and exposes its own schemas as MCP tools (services.mcpServer) — the services.* wrapper pair for Model Context Protocol integrations. ## Workflows - [Workflow Engine Reference (Steps, Templates, Sagas)](https://docs.supero.dev/developers/workflows/engine-reference/): The full reference for the Workflow Engine service: step types, template syntax, error handling, and saga compensation for orchestrating multi-step business logic across your imported services. ## Access control - [Permissions that leak through ORDER BY](https://docs.supero.dev/articles/field-level-permissions-order-by/): Field-level permissions that mask the API response do not protect the field. If a caller can still sort, filter or group by it, they reconstruct it. ## Multi-tenancy - [What breaks first when your SaaS gets a second tenant](https://docs.supero.dev/articles/multi-tenant-saas-checklist/): The multi-tenant SaaS checklist: seven decisions, what each costs if you defer it, and the one everyone worries about far too early. ## Transactional correctness - [Three backend jobs whose first version is wrong](https://docs.supero.dev/articles/thirty-percent-nobody-estimates/): Payment compensation when the compensating action fails, two-phase inventory reserve, and the balance column that should have been a ledger. Three checks you can run today. ## Building on Supero - [What you walk away with](https://docs.supero.dev/articles/what-you-walk-away-with/): Platform vendor lock-in, compared: what Bubble, Retool, Lovable, Bolt, v0, Supabase and Supero each hand you on the way out, and what still calls home. - [A playbook for freelancers and agencies](https://docs.supero.dev/articles/freelancer-agency-playbook/): How much to charge for a client portal: the four-week build shape, the week-zero questions that win the job, and the pricing model that makes it recurring. ## Under the hood - [What Supero is, and what it replaces](https://docs.supero.dev/articles/what-supero-is/): Supero in plain terms: a governed multi-tenant backend you generate or wrap around your own database. What it replaces, the four things you still build, and where it is weak. - [Building an app over MCP](https://docs.supero.dev/articles/mcp-build-tools/): An MCP server with 64 tools, 33 of them for building and deploying an app. The full catalogue is readable without an account. Here is what each phase does. - [Idempotency without an idempotency table](https://docs.supero.dev/articles/insert-is-the-lock/): How to implement an idempotency key with a unique index instead of a lock: the deterministic name trick, why the row is deleted on failure, and the concurrency test that proves it. - [Your unauthenticated test client is authenticated](https://docs.supero.dev/articles/green-tests-that-proved-nothing/): A shared pytest fixture called api_client was documented as unauthenticated and was not. Thirty-two security assertions passed anyway. Three meta-tests you can copy. - [Four ways a list endpoint lies to you](https://docs.supero.dev/articles/list-endpoint-lies/): Unbounded default reads, a silent limit clamp, dropped filters answered with 200, and a keyset cursor that empties page two. Four list-endpoint failures and how to test for them. - [The permission that returned zero rows](https://docs.supero.dev/articles/zero-rows-for-everyone/): Read filters and write stamps must be generated from one declaration. When they drift, the endpoint returns an empty list instead of an error, and empty looks exactly like new. - [Querying a warehouse you do not pay for](https://docs.supero.dev/articles/warehouse-guardrails/): Guardrails for reading a customer's warehouse: a fail-closed byte cap, a timeout pushed to the source, an injected LIMIT, mandatory type mapping, and a self-service kill switch. - [A 409 should tell you what to do next](https://docs.supero.dev/articles/the-409-that-helps/): An error body that names the current state, whether it is terminal, the states the operation was allowed from, and what you can do instead. And why enforcing it centrally is harder than it looks. - [Give your AI agent no credentials of its own](https://docs.supero.dev/articles/agent-with-no-credentials/): An AI agent that answers questions over your data should hold no credential of its own. How the caller's token is forwarded, where enforcement actually lives, and what is still open. - [When a language model writes your schema](https://docs.supero.dev/articles/schemas-a-model-wrote/): Three things a schema system needs once a model is authoring the schemas: synonym folding at write time, refusing to guess an ambiguous base, and telling hard dependency edges from soft ones. ## Reference apps - [Lumen: clinic booking](https://docs.supero.dev/articles/lumen-clinic-booking-app/): Lumen is an open-source clinic appointment booking app. Patients book visits and staff run the schedule. Source on GitHub, live demo at lumen.supero.live. - [BrightSmile: dental practice](https://docs.supero.dev/articles/brightsmile-dental-practice-app/): BrightSmile is an open-source dental practice app for a four-clinic group, with priced treatment plans patients accept. Code on GitHub, and it runs live. - [Medora: hospital network](https://docs.supero.dev/articles/medora-hospital-network-app/): Medora is an open-source hospital patient portal for a three-site network, with fields hidden per role. The source is on GitHub and a live demo is running. - [TrialCore: clinical trials](https://docs.supero.dev/articles/trialcore-clinical-trial-app/): TrialCore is an open-source clinical trial management app with a sponsor console, coordinator view and public study registry. Code on GitHub, demo live. - [Helix: blinded multi-site trials](https://docs.supero.dev/articles/helix-multi-site-clinical-trials-app/): Helix is an open-source multi-site clinical trial app that hides the treatment arm from the investigator role. Source on GitHub, with a live demo. - [Ledgerline: subscription billing](https://docs.supero.dev/articles/ledgerline-billing-app/): Ledgerline is an open-source subscription billing dashboard with invoices, dunning and expense approval. Source open on GitHub, with a live demo running. - [Sentinel: insurance claims](https://docs.supero.dev/articles/sentinel-insurance-claims-app/): Sentinel is an open-source insurance claims portal for two insurers, with scripts that test its access rules. Source on GitHub, and it runs live as a demo. - [Summit: sales CRM](https://docs.supero.dev/articles/summit-crm-app/): Summit is an open-source sales CRM with accounts, leads, a deal pipeline and forecasts scoped to each rep. Source on GitHub, live at summit.supero.live. - [Amplify: social media management](https://docs.supero.dev/articles/amplify-social-media-management-app/): Amplify is an open-source social media management app that can post to four networks and records live or simulated delivery. Source on GitHub, with a live demo. - [Atelier: wholesale marketplace](https://docs.supero.dev/articles/atelier-wholesale-marketplace-app/): Atelier is an open-source wholesale marketplace app with multi-brand orders and Net 30 payment terms at checkout. The code is on GitHub and it runs live. - [Concierge: AI support desk](https://docs.supero.dev/articles/concierge-support-desk-app/): Concierge is an open-source help desk with an AI assistant, a ticket queue and an agent console. MIT source on GitHub, live demo at concierge.supero.live. - [FieldOps: field service](https://docs.supero.dev/articles/fieldops-field-service-app/): FieldOps is an open-source field service management app: quotes, dispatch, parts, signed work orders, payment. Source on GitHub, with a live demo. - [Relay: healthcare staffing](https://docs.supero.dev/articles/relay-healthcare-staffing-app/): Relay is an open-source healthcare staffing marketplace app with shifts, credential checks, timesheets and payouts. On GitHub, live at relay.supero.live. - [Tavola: restaurant ordering](https://docs.supero.dev/articles/tavola-restaurant-ordering-app/): Tavola is an open-source restaurant ordering system with a kitchen board, reservations and loyalty points. Source on GitHub, live at tavola.supero.live. - [Backlot: film production](https://docs.supero.dev/articles/backlot-film-production-app/): Backlot is an open-source film production scheduling app: slate, crew, strip board, call sheets by email and SMS. On GitHub, live at backlot.supero.live. - [Haven: real estate brokerage](https://docs.supero.dev/articles/haven-real-estate-brokerage-app/): Haven is an open-source real estate brokerage website with listing search, tour requests and offers. Source on GitHub, live demo at haven.supero.live. - [Lattice: property management](https://docs.supero.dev/articles/lattice-property-management-app/): Lattice is open-source multi-tenant property management software with leases, rent and maintenance requests. On GitHub, live at lattice.supero.live. - [Pulse: multi-location gym](https://docs.supero.dev/articles/pulse-multi-location-gym-app/): Pulse is open-source multi-location gym software where each gym is its own tenant, with classes and bookings. On GitHub, live at pulse.supero.live. - [PulseFit: gym class booking](https://docs.supero.dev/articles/pulsefit-gym-booking-app/): PulseFit is an open-source gym class booking app with a weekly timetable, a waitlist and a member portal. Source on GitHub, live at pulsefit.supero.live. ## Optional - [Supero marketing site](https://www.supero.dev/): product overview, pricing, comparisons. - [Sitemap](https://docs.supero.dev/sitemap.xml): every documentation URL.