Data and permissions
Record where active data and backups reside and who can access them. Include identity providers, external apps and connected systems.
Cloud, hosting and IT for businesses
Control over data and systems takes more than choosing a location. We examine access, dependencies, open applications and the ability to move again later.
| Area | Specific question | Documented outcome |
|---|---|---|
| Data | Where are files, databases and backups stored? | An inventory of data and storage locations |
| Access | Who can administer and change permissions? | Named roles and handover procedures |
| Dependencies | Which external services does the application require? | An inventory of integrations and licences |
| Exit | How can data and configuration leave the platform? | A tested export and handover plan |
Your own platform can create flexibility, while also requiring maintenance, updates and recovery. Digital sovereignty therefore includes assigning those tasks deliberately. We connect application choices with a documented operating model and a practical handover.
Record where active data and backups reside and who can access them. Include identity providers, external apps and connected systems.
Nextcloud, GitLab and other open-source projects offer self-hosting options. Still review editions, licences, additional features and the work required for updates.
Exports, configuration, documentation and administrative access help with a later migration. A practical test shows which data can be transferred completely in a usable format.
No. You can arrange support while retaining clear access, responsibilities and the ability to change platforms. The details of the operating model are what matter.
Not necessarily. Licences are only part of the cost. Setup, integration, ongoing operation, support and future upgrades also belong in the calculation.
Tell us your application, user count and the support you need.