Publish our Sovereignty Profile#
What this is, concretely#
This commitment consists of publishing on your own website a declaration structured according to the Sovereignty Profile format defined on the /garanties page of the manifesto. The Profile documents, across seven domains, your current situation regarding technological sovereignty: strategic third-party components you use, contingency plans in case of a flip, supply-chain dependencies, hosting and data, continuity on failure, governance and capital, commitments and assumed limits.
The format is designed to be filled in honestly rather than perfectly. You may declare blind spots, dependencies you do not control, and dimensions you are still working on. Transparency on these zones is explicitly valued by the manifesto as a signal of reliability.
In practice, you use the /declarer web generator, which produces two files (sovereignty.json and sovereignty.md) that you publish at the root of your domain — exactly like a robots.txt or security.txt file. You do not need prior authorisation, certification, or external audit.
Why this commitment matters#
This is probably the most structuring commitment in the entire device. The manifesto argues for a deep market shift: moving from a regime where sovereignty is a hollow marketing promise to one where it is a documented, verifiable, comparable object. Without massive Profile publication, that shift does not happen.
For you as a provider, the exercise of filling in the Profile is an investment that goes beyond publication itself. Many providers discover, while filling in the seven domains, dependencies they had not consciously registered, blind spots they had not examined, commitments they were not formally upholding. The Profile acts as a trigger for internal work whose benefit then flows back into the quality of the service delivered.
For your clients, the Profile is a concrete document they can integrate into their own processes — procurement, listing, periodic reassessment. Without a Profile, they have only your marketing claims and their own intuition. With a Profile, they have workable material.
For the manifesto community, the aggregation of Profiles feeds the gap observatory and makes it possible to map collectively the zones where the European ecosystem lacks alternatives.
A concrete example#
A European B2B SaaS publisher, around 50 employees, offers a customer relationship management solution used by about 800 clients across Europe. Management decides in March 2026 to publish a Profile. The technical team fills in domains 1 (third-party components: PostgreSQL, Redis, Elasticsearch, Kubernetes, etc.) and 2 (contingency plans) in two weeks. Domain 3 (supply chain: GitHub, npm, Docker Hub, Let’s Encrypt, etc.) takes a few days. Domain 4 (hosting at Outscale qualified SecNumCloud 3.2) is quick. Domains 5 (continuity on failure), 6 (governance and capital), and 7 (commitments and assumed limits) take a few days each, in conjunction with management.
The exercise reveals two blind spots the publisher declares honestly: a dependency on a US transactional mailing service which it plans to migrate within 18 months, and the absence of a formal software escrow which it plans to put in place within 12 months. The Profile is published at https://example-publisher.eu/sovereignty.json and sovereignty.md. The sales department announces the Profile in a client communication and now includes it in commercial presentations.
Six months after publication, several clients indicate that the availability of the Profile weighed positively in their renewal decision. Two European competitors publish their own Profile in turn. A public tender begins to require the publication of a Profile as a prerequisite.
Anti-pattern to avoid#
A Profile reduced to self-promotion (“we guarantee a service of the highest quality, in line with industry best practice”) without verifiable information is exactly what the device seeks to move beyond. The format is designed to resist that kind of filling: if the seven domains are hollow, reading the Profile reveals it immediately.
A Profile that hides blind spots rather than declaring them is more fragile than a Profile that owns them. If a client discovers on their own a blind spot you had not declared, your credibility is dented. If you have declared it, you keep control of the conversation.
Success indicators#
The commitment is fulfilled when the two files (sovereignty.json and sovereignty.md) are published at the root of your domain, conform to the manifesto’s JSON schema v3, and the seven domains are filled in with a level of precision that lets a reader understand your situation. Publication should be notified to the public index via the notification form.
The long-term commitment includes annual updating of the Profile. A one-off publication that is not refreshed gradually loses its informational value.
JSON schema category: publication. Default horizon: 6 months. Applicable to: businesses, associations, foundations.