Definitions of the terms used throughout this site. For questions rather than terms, see the FAQ.

Sovereign computing

Open source, self-hosted foundation infrastructure - compute, storage, network, identity, security, and operational services - that an organisation runs and controls. See what is sovereign computing.

Foundation infrastructure

The layer beneath applications and above hardware. The category covers this layer, not the hardware below it or the applications above it.

Support levels (0 to 5)

A model in which each level of support, from self-service to strategic advisory, can be sourced from an independent vendor through open interfaces. See the support model.

Knowledge Brief

A published note - covering a known defect, a workaround, or the status of a fix - that Level 0 makes freely available and higher levels contribute back to.

Conformance report

A dated, signed, openly published completion of the conformance checklist, marking each requirement pass, fail, or not applicable. See conformance.

The Sovereignty Test

The requirement that a customer could change any provider without losing data, history, or the ability to operate - the practical test of an open sovereign cloud. See conformance.

Component Conformance Manifest

A published list of every component in a platform, its upstream (Level 4) status, and whether it is substitutable or load-bearing.

Substitutable and load-bearing components

A non-conformant component is substitutable if the customer can replace it through documented APIs, and load-bearing if they cannot. A load-bearing, non-conformant component caps the platform's tier.

Verified Sovereign Computing Mark (VSCM)

The tiered mark that certifies a conformant platform, backed by a verifiable report. See the Mark.

Tiers 1 to 4

The conformance grades, from Tier 1 (fully conformant, independently audited) to Tier 4 (non-conformant). See the Mark.

Provider plurality

The availability of more than one independent provider for a given support level - the strongest signal that a customer is not locked in.

Zero trust

A design principle in which encryption in motion and at rest, and strict access control, are the baseline rather than optional add-ons.

Portability

The ability to move data and workloads between providers in standard formats, without vendor assistance or proprietary lock-in.