nilly cloud
Fair 3.3 Easy 4.3 Secure 4.3
| Pillar | Criterion | Score | Evidence |
|---|---|---|---|
| Easy | Day-one UX Can non-technical staff use it without a project? | 5 | Minimal setup for editors. Source |
| Easy | Operate Admin burden, updates, backups and language coverage. | 5 | Fully managed. Source |
| Easy | Integrate SSO, mail/CalDAV, APIs and common NGO connectors. | 3 | WordPress and generic script. Source |
| Fair | Lock-in / exit Can you leave with your data in open formats, at known cost? | 4 | One-line embed; easy to replace. Source |
| Fair | Sovereignty EU legal entity, EU hosting, and exposure to extra-EU lawful access? | 4 | Swiss company; confirm hosting region. Source |
| Fair | Openness Open source or open standards? Are independent implementations possible? | 2 | Closed source. Source |
| Secure | IT security Authentication, encryption, patch cadence and independent audit. | 4 | Small privacy SaaS. Source |
| Secure | User security 2FA, roles, phishing resistance and safe defaults. | 4 | Simple access model. Source |
| Secure | Personal data GDPR fit: DPA, residency, sub-processors and Schrems II posture. | 5 | GDPR/FADP-oriented design. Source |