Digital autonomy: a practical next step together
Control over data, processes and change. We welcome conversations and collaboration with organisations working on these questions.

Digital autonomy becomes practical when you can choose how processes work, where data is used and how to move forward when an application or supplier changes. This requires technology and transferable agreements. For public organisations and education institutions, it directly affects continuity, accountability and the ability to keep improving.
Autonomy starts with the connections
A request may start in a portal, require a manager’s approval and create work in HR, identity, service management and a document system. When the meaning of those steps exists only in separate scripts or one administrator’s knowledge, change becomes difficult.
With Service Automation Suite, we aim to make those connections understandable and reusable: the authoritative source, applicable rule, authorised decision-maker and outcome that determines the next step. Your existing applications retain their own function. Their connections gain a manageable configuration.
Dutch technology with deliberate choices
Our foundation is Dutch technology and a platform developed as a coherent whole. This provides a starting point for targeted changes and reuse. It does not automatically mean every supplier, data flow or dependency is exclusively Dutch or European. That is precisely why we discuss the actual chain.
For each application, we agree data locations, hosting, support access, interfaces, export and handover. Which data can you take with you? Who can maintain the configuration? What changes with a different HR package, a new service desk or another supplier? These questions belong in the solution.
Start with one public-service challenge
A municipality may want to verify a case-file handover. An education institution may want to compare asset records and security observations. A public agency may need to connect a request, a supplier task and confirmed completion. These are different stories, but the same questions recur: source, agreement, responsibility, execution and evidence.
Begin with one bounded handover or check. Use existing building blocks where they fit and assess what needs additional configuration. This creates a practical first step whose outcome you can discuss with colleagues.
Better insight, with room to automate later
You can start by reading, comparing and presenting data. Then determine whether a discrepancy needs review, a service task or an approved system action. The process owner retains the decisions; technology makes execution traceable.
This supports the demand for demonstrable cyber resilience and control. An overview can support what a team needs to investigate. A decision with confirmed execution can show how an agreement is followed. Assessing standards and risks remains the responsibility of the organisation and its professionals.
Developing further together
We want to contribute to developments in digital autonomy and demonstrable process control. Existing integration and automation capabilities provide the starting point. Further sovereign process coordination, a Virtual Appliance and AI under organisational control are areas we are exploring and developing. For each application, we distinguish what is available, what can be configured and what still requires development.
We welcome contact with organisations working on these questions: to discuss experiences and needs, explore a check or develop a next step together. The conversation need not start with a large project plan. One recognisable challenge is enough.
Get in touch: where can we start together?
Read about digital autonomy, AI under organisational control, our sectors and the integration catalogue.
Keep reading
Cyber resilience in vocational education: make execution demonstrable · Defender and your asset register: start with a read-only check



