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. Use the information button beside each question to see what it means and where it comes from.

Your data and privacy

We use your responses only to produce your report. We delete the submitted assessment data within 7 days of producing your report, unless you ask us to keep it. We keep your contact details on record so we can follow up about Sovereign Computing - unless you choose "Report only" at the end, in which case we use your details to send your report and then delete them.

Leave this empty

Platform or cloud name *

Operator organisation *

Your name *

Email (for your report) *

Key components in your stack

1. Inter-level support handovers are exposed via documented, versioned APIs * -- Select -- Yes Partly No Unsure

2. Those APIs accept any licensed adjacent-level provider without a separate partnership * -- Select -- Yes Partly No Unsure

3. You publish a machine-readable registry of providers at each support level * -- Select -- Yes Partly No Unsure

4. Nothing in your terms prevents a customer sourcing Level 1 to 4 support independently * -- Select -- Yes Partly No Unsure

5. Level 0 docs, FAQs, forum, and knowledge briefs are public under a redistributable licence * -- Select -- Yes Partly No Unsure

6. You publish a machine-readable feed of knowledge briefs * -- Select -- Yes Partly No Unsure

7. Open ticket-exchange and status APIs connect the support levels * -- Select -- Yes Partly No Unsure

8. Ticket history is portable and survives a change of support provider * -- Select -- Yes Partly No Unsure

9. Level 3 has defect-filing into upstream and a change-request channel to the operator * -- Select -- Yes Partly No Unsure

10. Components have public issue trackers accepting submissions from any Level 3 provider * -- Select -- Yes Partly No Unsure

11. Component source is public, with a published roadmap and release calendar * -- Select -- Yes Partly No Unsure

12. Releases are cryptographically signed and reproducible from public sources * -- Select -- Yes Partly No Unsure

13. A coordinated disclosure process and machine-readable CVE feed are published * -- Select -- Yes Partly No Unsure

14. Governance is conducted in public, with accessible decision records * -- Select -- Yes Partly No Unsure

15. A customer can migrate ticket history, knowledge, and telemetry at any level * -- Select -- Yes Partly No Unsure

16. At least two independent providers exist at each of L1, L2, and L3 (and two maintainers at L4) * -- Select -- Yes Partly No Unsure

17. You publish a current, signed conformance report * -- Select -- Yes Partly No Unsure

Tier you believe you meet today * -- Select -- Tier1 Tier2 Tier3 Tier4 Unsure

Staying in touch * -- Select -- Keep-me-informed Report-only

Submit assessment