Digital sovereignty means a company’s ability to decide about its digital infrastructure itself: where data live, who processes them, which dependencies arise. In the mid-market it rarely means full autarky. What matters is room to act when conditions change. Sovereignty means decide deliberately, not run everything yourself.

Why the topic matters for the mid-market

Production data, supply chains, customer information, and finance processes sit in ERP, specialist software, and cloud services. When terms change, interfaces fail, or a service is discontinued, what counts is whether you can respond. Typical questions before every major IT decision:

• Where do business-critical data live, and who has access?
• How dependent is the company on individual platforms or contract models?
• What happens on term changes, failing interfaces, or service discontinuation?
• Can operations and support be switched without stopping the process?

Whoever cannot answer these questions makes IT decisions without a risk picture.

What resilience delivers as a pragmatic approach

Resilience is the pragmatic path to sovereignty: document critical systems, check export options, test backups and recovery, define exit strategies before you need them. Details: What is IT resilience for mid-market companies?. Vendor lock-in is one of the most common risk factors. Whoever cannot switch cannot steer well.

Sovereignty and resilience overlap: one aims at deliberate decisions, the other at continuity when disruption hits. Both need documentation and regular review, not a permanent transformation program.

Why the ERP sits at the center

The ERP sits at the center of many SMEs: orders, finance, warehouse, and production depend on it. Whoever has no freedom of choice here on operations, support, and further development risks standstill when unexpected changes hit. Check therefore:

1. Operating model: cloud vs. on-premise
2. Data holding and export: data sovereignty for cloud ERP
3. Adaptability of processes and open interfaces
4. Switchability of service providers and exit strategy

Open platforms support sovereignty when source code, data, and extensibility stay with the company. Open source ERP goes deeper on this point. Nuclos is licensed under the GNU AGPL 3.0 and supports cloud and on-premise. The license alone is not enough. Without export, documentation, and clear contracts, sovereignty stays theory.

Which checklist helps before the ERP decision

Put sovereignty into vendor evaluation, on equal footing with functions and price:

• Where do data and backups live, and who has access?
• Can data be exported completely and in a machine-readable format?
• Can customizations be continued by another team?
• Which minimum terms and exit clauses apply?
• How do license and operations costs scale with growth?
• Is a later switch of operating model possible?

This list does not replace legal or security advice. It creates the frame for a deliberate decision.

What leadership should decide concretely

Digital sovereignty is risk management with a clear goal: respond flexibly without endangering operational flows. Accept dependencies that are reversible and documented. Avoid dependencies that would block the core business. Cloud or on-premise is secondary. Portability, contracts, and operational control decide. Whoever treats the ERP as critical infrastructure and clarifies exit options before they are needed acts sovereignly, even when external partners run operations.