Topologies by edition

The same codebase deploys in different shapes depending on the edition and the constraints you are designing for. Key points:

• A free Starter tenant, a hosted multi-tenant deployment, and a self-hosted or air-gapped install are points on one spectrum, not different products. The same isolation and the same controls hold across them.
• Edition gating decides which capabilities are present. Your job as an architect is to map the customer's constraints (residency, isolation, network posture, scale) to a topology, then justify it.
• Name what changes between topologies and what does not. The isolation model and the audit trail do not change; where the platform runs and who operates it do.