Provider sovereignty assessment - Sovereign Computing Initiaitve

Answer for the platform you operate or offer. This is a self-check against the Sovereign Computing conformance framework and the Sovereignty Test, not a formal audit. "Unsure" is a valid answer. We will store your responses and follow up with a fuller assessment.

Platform or cloud name *

Operator organisation *

Your name *

Email (for your report) *

Key components in your stack

Inter-level support handovers are exposed via documented, versioned APIs *

Those APIs accept any licensed adjacent-level provider without a separate partnership *

You publish a machine-readable registry of providers at each support level *

Nothing in your terms prevents a customer sourcing Level 1 to 4 support independently *

Level 0 docs, FAQs, forum, and knowledge briefs are public under a redistributable licence *

You publish a machine-readable feed of knowledge briefs *

Open ticket-exchange and status APIs connect the support levels *

Ticket history is portable and survives a change of support provider *

Level 3 has defect-filing into upstream and a change-request channel to the operator *

Components have public issue trackers accepting submissions from any Level 3 provider *

Component source is public, with a published roadmap and release calendar *

Releases are cryptographically signed and reproducible from public sources *

A coordinated disclosure process and machine-readable CVE feed are published *

Governance is conducted in public, with accessible decision records *

A customer can migrate ticket history, knowledge, and telemetry at any level *

At least two independent providers exist at each of L1, L2, and L3 (and two maintainers at L4) *

You publish a current, signed conformance report *

Tier you believe you meet today *

May we contact you about your assessment? *

Last updated: 26 June 2026