AWS (global)
Fair 1.7 Easy 3.0 Secure 3.7
| Pillar | Criterion | Score | Evidence |
|---|---|---|---|
| Easy | Day-one UX Can non-technical staff use it without a project? | 2 | Steep console learning curve for non-ops staff. Source |
| Easy | Operate Admin burden, updates, backups and language coverage. | 2 | You still design IAM, billing and patching. Source |
| Easy | Integrate SSO, mail/CalDAV, APIs and common NGO connectors. | 5 | Largest ecosystem of connectors and SaaS. Source |
| Fair | Lock-in / exit Can you leave with your data in open formats, at known cost? | 2 | Open APIs help exit; proprietary managed services create gravity. Source |
| Fair | Sovereignty EU legal entity, EU hosting, and exposure to extra-EU lawful access? | 1 | US company; CLOUD Act exposure. Source |
| Fair | Openness Open source or open standards? Are independent implementations possible? | 2 | Closed platform; some open-source tooling around it. Source |
| Secure | IT security Authentication, encryption, patch cadence and independent audit. | 5 | Strong shared-responsibility security model. Source |
| Secure | User security 2FA, roles, phishing resistance and safe defaults. | 4 | IAM is powerful and easy to get wrong. Source |
| Secure | Personal data GDPR fit: DPA, residency, sub-processors and Schrems II posture. | 2 | DPA available; Schrems II remains the hard question. Source |