See it before you install it

lumen.supero.live is one of the 19, running the code in apps/healthcare/lumen. The login page lists every demo account with its role and password — click one and you are in. No signup, nothing to install.

Sign in as the front-desk user, then sign out and back in as the patient. The patient's record is missing clinical_notes — and nothing in ui/app.js is doing that. The rule is five lines in apps/healthcare/lumen/setup.py.

Or check it from a terminal in ten seconds, no signup, no clone of your own domain:

git clone https://github.com/supero-platform/supero-apps
cd supero-apps/verify && ./02-rbac-enforcement.sh

That script logs into the live insurance demo as a claims adjuster and as a policyholder, finds one claim both can see, and compares the two responses. The adjuster gets fraud_score and internal_notes; the policyholder gets the same record without them. verify/ explains what it proves — and what it does not.

Then run it yourself, in about two minutes

New here? Start with lumen — it is the smallest app in the repo and the one the docs follow.

git clone https://github.com/supero-platform/supero-apps
cd supero-apps/apps/healthcare/lumen

cp .env.example .env    # set SUPERO_DOMAIN, SUPERO_ADMIN_EMAIL and SUPERO_PASSWORD
./run.sh

run.sh creates a venv, installs the supero SDK, registers your domain, uploads the schemas, seeds demo data, wires up roles — then serves the app at http://localhost:5663.

That takes about 90 seconds on a cold machine with an empty pip cache — roughly 10 seconds of install and 60-odd of platform setup. Call it two minutes with the time it takes you to fill in .env.

You do not need an account, an invite, or a credit card. Domain registration is open. The name you put in SUPERO_DOMAIN becomes yours if it's free.

Prefer containers? docker compose up works identically.

The apps

Each one is a complete, multi-tenant application — public storefront and admin panel, with role-based access enforced on the server, not in the UI.

🩺 Healthcare & Life Sciences

💰 Finance & Insurance

🛍️ Commerce & Sales

🔐 Multi-tenant (one deployment, many organisations)

Every app above runs a single organisation. These four run several at once, and the isolation is enforced by the server: a user signed into one tenant cannot read another tenant's rows even by calling the API directly with their own valid token. Two of them also demonstrate field-level access control on top of that, so a row you can read still arrives with fields removed.

Sign in on any of them and the login page lists every demo account with its tenant, role and password — click a row to fill the form.

🏢 Operations & Services

🏡 Property & Media

Build it with your AI

Every app ships a CLAUDE.md (and .cursorrules / .windsurfrules) so your assistant understands the codebase before it touches a line.

You can also connect your editor directly to the platform over MCP — 64 tools that let an assistant design schemas, run CRUD, connect a database, and take an app from a sentence to a live URL:

claude mcp add --transport http supero https://api.supero.dev/mcp/v1/messages \
  --header "X-API-Key: ak_your_key_here"

Then just ask:

"Add a waitlist to the clinic app — patients join, staff promote them when a slot opens."

The interesting part is what the assistant is allowed to do. An MCP call carries your credential to the same API a browser would use — no service account, no elevated path. So the agent inherits your permissions rather than getting its own, and the row scoping and field hiding above apply to it identically. An agent you point at a customer's data is bounded by the same policy the customer is.

The server is live and you can inspect it without a key:

curl https://api.supero.dev/mcp/v1/info

docs/mcp.md covers getting a key and the tool families. The complete reference, every parameter, is at docs.supero.dev/developers/mcp/tool-reference.

What you actually get

Two things, and it's worth being precise about which is which.

From schemas.py (95–270 lines, median 120), automatically — no code: