Google Cloud (global)
Fair 1.7 Easy 2.7 Secure 3.7
| Pillar | Criterion | Score | Evidence |
|---|---|---|---|
| Easy | Day-one UX Can non-technical staff use it without a project? | 2 | Console and IAM are non-trivial. Source |
| Easy | Operate Admin burden, updates, backups and language coverage. | 2 | You operate landing zones and billing. Source |
| Easy | Integrate SSO, mail/CalDAV, APIs and common NGO connectors. | 4 | Good APIs; fewer NGO-specific guides than AWS. Source |
| Fair | Lock-in / exit Can you leave with your data in open formats, at known cost? | 2 | Kubernetes and open APIs help; Google 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; Kubernetes is open. Source |
| Secure | IT security Authentication, encryption, patch cadence and independent audit. | 5 | Strong infrastructure security. Source |
| Secure | User security 2FA, roles, phishing resistance and safe defaults. | 4 | IAM complexity is the user-security risk. Source |
| Secure | Personal data GDPR fit: DPA, residency, sub-processors and Schrems II posture. | 2 | DPA available; Schrems II remains. Source |