Glossary
- sovereign software
Sovereign Software has a (very) high level of autonomy and does not depend on external control.
The correct behaviour of the program (or system) doesn’t depend on anything but the software itself. For example, there is no ‘help desk’ to call when the system falters in the field; the software is its own final authority.Usually, Sovereign software is completely self-written and owned by the company. Or, the company has a full copy of the (often ‘open’) external source — so that it can build and maintain that software. This ensures any future change is (technically) possible. For the same reason, it is usually based on open standards. So that no vendor lock-in is possible. Sometimes that includes the tools/infrastructure essential to build that software – this can include the ‘compiler’ and even influence the selected programming language.
Nowadays, ‘geopolitical sovereignty’ makes this topic even more relevant. E.g. the EU is stimulating that software (and especially data) does not depend on foreign administrations, nor cross borders.
Apparently, the trust in former allies has shrunk.The concept is not new, however.
Many embedded systems operate in regulated domains (e.g., healthcare, defense, automotive, and gambling) where regulations demand a (permanent) right to audit. And so, the need for “readable” source code is vital