Supo gives each customer organization an isolated application environment while keeping identity, metadata, data access, and schema evolution under one control plane.

Platform model

Understand how organizations, environments, repositories, schemas, and roles fit together.

Architecture

Explore the system components and the trust boundaries between them.

Identity and access

See how WSO2 identities become scoped Supo sessions and database permissions.

Data and migrations

Learn how runtime data operations and reviewed structural changes follow separate paths.

​
The platform in one sentence

Supo is a tenant-aware application platform where identity establishes the organization boundary, the control plane resolves immutable infrastructure mappings, and every data operation executes with the minimum role required for one organization and one environment.
This documentation describes the intended platform architecture and its current development implementation. It does not claim that the present deployment is production-ready.

​
Design principles

  • Identity defines tenancy. The server derives organization context from a validated session and live membership, never from a browser-supplied schema.
  • Control and data planes are separate. Platform metadata can locate tenant resources but cannot read tenant application data.
  • Environments are explicit. main and dev are independent mappings with their own Git branches, schemas, and database roles.
  • Structure is reviewed. Table changes become migration files in Git before a dedicated service applies them.
  • Least privilege is structural. Runtime and DDL capabilities use separate non-login roles and transaction-local role assumption.