Data Security & Isolation

Orquestra relies on strictly enforced Multi-Tenant Architecture. Because institutional workflows process highly sensitive data (admissions, finance, health records), cross-tenant isolation is the primary non-negotiable invariant.

Multi-Tenant Isolation Enforcement Model

• Auth & RBAC: Every API access requires a tightly scoped Application versioned API Key or a JWT tied to an authenticated Institutional user.
• Row-Level Security (RLS): Every query explicitly filters by institution_id and project_id at the database engine level. Applications cannot accidentally query cross-institution workflows.
• Frontend Enforcement Middleware Layer (FEML): The Orquestra Console interface utilizes FEML to guarantee that state, Zustand stores, and Websocket subscriptions are categorically destroyed and recreated when shifting between Projects or Institutions.

Immutability of Blueprints

Once a generated Institutional Workflow Blueprint is deployed by a Control Plane administrator, it is designated as immutable.