Platform overview

Institutional teams evaluating platform software need a clear map: which product does which job, how pieces relate, and where evaluation should begin.

Without orientation, product pages and documentation become a pile of claims instead of a coherent operating model.

AOVIAS products share engineering standards for security, identity, and interoperability. Each product still has a distinct job.

AOVIAS Command is the operational control and institutional operations workspace. AOVIAS Studio is the delivery workspace to design, refine, and ship institutional work. Do not swap their value propositions.

Start with Command when the primary need is structured visibility and accountable operational control. Start with Studio when the primary need is coherent solution design and delivery discipline.

Use this documentation set for implementation context, then review packaging and demonstration paths with AOVIAS. Prefer depth in a focused pilot over breadth that obscures ownership.

Continue with Getting started with AOVIAS Command and Studio delivery practices. Pair documentation with product pages when you need capability detail, and with Contact when you are ready to evaluate fit for your institution.