Library of sovereign commitments
Reading the corpus — two entries to the same records
You are here
By axis of action
Provider · User · Developer · Investor
Also available →
By transversal issue
Reversibility · Continuity · Sovereignty · Funding · Readability · European bricks · Structured demand
By theme
See the full index →- Theme · 5 commitments
Choosing European bricks
Prefer, at functional equivalence, bricks under European governance or held in a neutral foundation, to give alternatives the critical mass they lack.
Manifesto anchor · thèses 11, 12 - Theme · 4 commitments
Continuity on failure
Guarantee the customer a continuous operating trajectory even if the provider disappears, is acquired, or shuts down its service.
Manifesto anchor · thèse 13 - Theme · 5 commitments
Ecosystem funding
Sustain economically the foundations, the maintainers and the infrastructures without which free software becomes a technical debt funded by others than us.
Manifesto anchor · thèses 8, 11 - Theme · 3 commitments
Legal and capital sovereignty
Put legal and capital conditions to work for autonomy, rather than enduring them at the moment of an acquisition or a requisition.
Manifesto anchor · thèses 4, 6, 7 - Theme · 7 commitments
Readability, transparency, mapping
Make readable what was opaque — components, jurisdictions, governance, dependencies — to enable informed choices and reveal critical concentrations.
Manifesto anchor · thèses 1, 6, 10 - Theme · 5 commitments
Reversibility and portability
Guarantee the customer's technical and legal capacity to leave at any time, without losing data or rewriting code.
Manifesto anchor · thèse 13 - Theme · 4 commitments
Structured demand for commitments
Make sovereignty an explicit criterion of purchases, due diligence and contractual relations — to transform the market through demand.
Manifesto anchor · thèse 11, programme positif axe 4
All commitments
30 commitments arranged along four angles of action — each one describes what is undertaken, how, and over which horizon.
§ Axis provider
Provider14 commitments
Commitments made by publishers, hosts, integrators — what a provider can write into a contract or an architecture to guarantee its clients' sovereignty.
- pub-001-publish-sovereignty-profile
Publish our Sovereignty Profile
Publish on your own website a structured declaration following the Sovereignty Profile format defined by the manifesto.
Horizon · 6 monthspublication - pub-002-fund-upstream-projects
Allocate a documented fraction of our software revenue to funding the open source projects we depend on
Each year, allocate a documented fraction of your software revenue to funding the open source projects your solution depends on.
Horizon · 1 yearfunding - pub-003-prefer-european-bricks-equiv
At functional parity, prefer bricks under European or multi-vendor neutral governance in the offers we put forward
Introduce a European or multi-vendor neutral preference into the technical composition of the offers you put forward to your clients.
preference - pub-004-qualify-commercial-discourse
Honestly qualify the governance nature of the solutions we distribute
Describe accurately the governance nature (neutral foundation, single-vendor, proprietary) of the solutions in your catalogue.
Horizon · 6 monthscommunication - pub-005-establish-software-escrow
Establish a software escrow mechanism with a trusted European third party, or publicly commit to releasing the source code under defined circumstances
Guarantee your clients a continuity path if you disappear, through software escrow or a public release commitment.
Horizon · 18 monthspublication - pub-006-publish-component-jurisdiction-list
Publish the list of strategic third-party components of our solution with their governance jurisdiction
Publish on your website the named list of strategic third-party components of your solution with their jurisdiction.
Horizon · 9 monthspublication - pub-007-contribute-to-european-foundations
Actively contribute to at least one open source project under European governance or under a neutral foundation
Make an active, measurable, and lasting contribution to at least one open source project under European governance or a neutral foundation.
Horizon · 1 yearcontribution - pub-008-european-host-default
Offer hosting with a European cloud provider as the default for our European clients
Make hosting with a European cloud provider the default option offered to your European clients.
Horizon · 1 yearpreference - pub-009-standard-reversibility-clause
Include a standard reversibility clause in all client contracts, with documented open formats, tested export scripts, and contractually guaranteed export deadlines
Guarantee your clients a complete, usable export of their data and flows, through open formats, tested scripts, and contractual deadlines.
Horizon · 1 yearpublication - pub-010-minimum-notice-period
Contractually guarantee a minimum notice period (six to twelve months) before any end of support, unilateral flip, or substantial change to the service
Give your clients time to migrate by guaranteeing a minimum contractual notice period before any major change to the service.
Horizon · 6 monthspublication - pub-011-operational-continuity-arrangement
Prepare an operational continuity arrangement that can be activated in the event of cessation — organised transfer of the client relationship, sector guarantee fund, or mutual takeover agreement between peers
Prepare a continuous operations path for your clients in the event of cessation, through a takeover agreement, sector fund, or mutual takeover.
Horizon · 2 yearspublication - pub-012-anti-foreign-acquisition-statute
Write into the statutes protective clauses against a non-EU acquisition — shareholders' agreement, European pre-emption rights, golden share, specific share with blocking rights
Lock the capital chain of your company against a jurisdiction flip through non-EU acquisition.
Horizon · 2 yearspublication - pub-013-source-code-audit-right
Open a source code audit right to clients whose contract justifies it — sensitive public bodies, critical infrastructures, strong sovereign requirements — under non-disclosure agreement
Recognise for your sensitive clients a right to verification of the code by independent eyes, under non-disclosure agreement.
Horizon · 1 yearaudit - pub-014-paas-application-portability
Guarantee PaaS clients application portability of their workloads — standard OCI packaging, manifests portable to diverse targets (Compose self-hosted as priority, other PaaS, Kubernetes as an option), detachable managed services, tested relocation contract
Guarantee PaaS clients the portability of their workloads to diverse targets, with light self-hosted via Docker Compose as the priority target.
Horizon · 18 monthspublication
→ To use these commitments from the reader’s side, see the guide by persona of the “Reading a Profile” guide.
§ Axis user
User7 commitments
Commitments made by buyers and user organisations — audit, structured demand, contractual requirements.
- user-001-audit-dependencies
Conduct an internal audit of our exposure to single-vendor technology dependencies
Systematically examine your technologies to identify those whose trajectory depends on a single publisher.
Horizon · 1 yearaudit - user-002-integrate-profile-procurement
Integrate the Sovereignty Profile as a prerequisite in our next procurement-listing processes for technology providers
Modify your procurement processes so that publication of a Sovereignty Profile formally weighs in the decision.
Horizon · 1 yearprocurement - user-003-prefer-european-governance
Give preference to bricks under European or multi-vendor neutral governance
Introduce in your technical decisions a preference criterion for neutral foundations or European governance, at functional parity.
preference - user-004-study-migration-single-vendor
Study at least one migration away from an identified single-vendor component
Conduct an in-depth migration study on at least one single-vendor component strategic to you.
Horizon · 18 monthsmigration - user-005-document-jurisdiction-supply-chain
Publicly document the governance jurisdiction of the main components of our supply chain
Publish on your website readable documentation of the components of your supply chain with their jurisdiction.
Horizon · 9 monthsaudit - user-006-fund-open-source-foundations
Allocate a documented fraction of our software budget to direct funding of open source projects
Each year, allocate a documented fraction of your software budget to funding the open source projects you depend on.
Horizon · 1 yearfunding - user-007-require-suppliers-profile
Require Sovereignty Profiles across the entire chain in our high-stakes tenders
Turn taking the Profile into account into a formal requirement for high-stakes tenders and procurement processes.
Horizon · 18 monthsprocurement
→ To use these commitments from the reader’s side, see the Buyer angle of the “Reading a Profile” guide.
§ Axis developer
Developer6 commitments
Individual commitments by those who write code — forge choices, dependencies, contributions.
- dev-001-european-forge-new-projects
Prefer European forges for hosting my new projects
Choose, for your new projects, source code forges whose governance is European or neutral.
preference - dev-002-document-dependencies-jurisdiction
Examine the governance jurisdiction of the third-party components you use in your professional projects
Systematically examine, for each professional project, the governance jurisdiction of the third-party components used.
Horizon · 6 monthsaudit - dev-003-contribute-european-projects
Regularly contribute to an open source project under European governance or under a neutral foundation
Allocate a regular share of your time to active contribution to an open source project under European governance or a neutral foundation.
contribution - dev-004-recommend-european-alternatives
Explicitly recommend European or neutral-foundation alternatives to your clients and colleagues
Make explicit, argued recommendation of European or neutral-foundation alternatives a part of your daily professional practice.
communication - dev-005-document-personal-stack-choices
Publish your technical stack choices and the sovereignty reasoning behind them
Publish on your personal site your preferred technical stack and the sovereignty reasoning behind it.
Horizon · 6 monthspublication - dev-006-fund-maintainers
Allocate a documented fraction of your professional income to direct funding of open source maintainers
Each year, allocate a documented fraction of your professional income to direct funding of the open source maintainers you depend on.
Horizon · 6 monthsfunding
→ To use these commitments from the reader’s side, see the Developer angle of the “Reading a Profile” guide.
§ Axis funder
Funder3 commitments
Commitments made by public and private funders — channelling spending towards European components, structuring demand.
- fund-001-sovereignty-criteria-due-diligence
Integrate technological sovereignty criteria into our due diligence process
Modify your internal due diligence processes so that technological sovereignty becomes a formal element of the analysis.
Horizon · 1 yearprocurement - fund-002-fund-european-foundation-projects
Allocate a documented share of our investments to support open source projects under European governance or under a neutral foundation
Complement your equity investment approach with direct support to non-VC-able open source projects under European governance or a neutral foundation.
Horizon · 18 monthsfunding - fund-003-publish-sovereignty-thesis
Publish our investment thesis on European technological sovereignty
Publish on your website an explicit investment thesis describing your view of European technological sovereignty.
Horizon · 9 monthspublication
→ To use these commitments from the reader’s side, see the Investor angle of the “Reading a Profile” guide.