| Easy |
Day-one UX
Can non-technical staff use it without a project?
|
5 |
Staff usually already know Gmail and Drive.
Source
|
| Easy |
Operate
Admin burden, updates, backups and language coverage.
|
5 |
Google operates the stack; almost no local admin load.
Source
|
| Easy |
Integrate
SSO, mail/CalDAV, APIs and common NGO connectors.
|
5 |
SSO, mail and a huge integration marketplace.
Source
|
| Fair |
Lock-in / exit
Can you leave with your data in open formats, at known cost?
|
2 |
Rule baseline (rubric_v1): global SaaS APIs/export exist, but suite gravity and remapping remain.
Source
|
| Fair |
Sovereignty
EU legal entity, EU hosting, and exposure to extra-EU lawful access?
|
1 |
Rule baseline (rubric_v1): non-EU legal entity + global SaaS — high extra-EU lawful-access exposure.
Source
|
| Fair |
Openness
Open source or open standards? Are independent implementations possible?
|
2 |
Rule baseline (rubric_v1): proprietary / non-OSI license — openness capped unless open standards dominate.
Source
|
| Secure |
IT security
Authentication, encryption, patch cadence and independent audit.
|
4 |
Mature security programme and encryption in transit/rest.
Source
|
| Secure |
User security
2FA, roles, phishing resistance and safe defaults.
|
4 |
Strong 2FA and admin roles; phishing of Google login remains common.
Source
|
| Secure |
Personal data
GDPR fit: DPA, residency, sub-processors and Schrems II posture.
|
2 |
DPA available; Schrems II / US cloud remains the hard GDPR question.
Source
|
