Self-hosted
Fair 5.0 Easy 3.0 Secure 3.3
| Pillar | Criterion | Score | Evidence |
|---|---|---|---|
| Easy | Day-one UX Can non-technical staff use it without a project? | 3 | Powerful, not pretty; staff need training. Source |
| Easy | Operate Admin burden, updates, backups and language coverage. | 2 | CMS, Civi and extensions must be kept current. Source |
| Easy | Integrate SSO, mail/CalDAV, APIs and common NGO connectors. | 4 | WordPress/Drupal, payment processors, mail. Source |
| Fair | Lock-in / exit Can you leave with your data in open formats, at known cost? | 5 | Your database; CSV/API export is normal practice. Source |
| Fair | Sovereignty EU legal entity, EU hosting, and exposure to extra-EU lawful access? | 5 | Host with an EU Civi partner. Source |
| Fair | Openness Open source or open standards? Are independent implementations possible? | 5 | AGPL with a large NGO community. Source |
| Secure | IT security Authentication, encryption, patch cadence and independent audit. | 3 | Security depends on CMS hygiene. Source |
| Secure | User security 2FA, roles, phishing resistance and safe defaults. | 3 | ACLs exist; defaults can be too open. Source |
| Secure | Personal data GDPR fit: DPA, residency, sub-processors and Schrems II posture. | 4 | Self-host or EU partner keeps member data closer to home. Source |