cryptee
- Fair 4.3
- Easy 3.3
- Secure 3.7
FES Scores 9
| Pillar | Criterion | Score | Evidence |
|---|---|---|---|
| Easy | Day-one UX Can non-technical staff use it without a project? | 4 | Cryptee offers a free tier with no credit card required for basic use, enabling day-one access. Source |
| Easy | Operate Admin burden, updates, backups and language coverage. | 4 | Rule baseline (rubric_v1): vendor-operated SaaS — low ongoing ops burden for a small NGO. Source |
| Easy | Integrate SSO, mail/CalDAV, APIs and common NGO connectors. | 2 | Limited public API documentation is available, restricting integration options. Source |
| Fair | Lock-in / exit Can you leave with your data in open formats, at known cost? | 3 | Rule baseline (rubric_v1): EU SaaS usually allows export, but remapping integrations still costs effort. Source |
| Fair | Sovereignty EU legal entity, EU hosting, and exposure to extra-EU lawful access? | 5 | Rule baseline (rubric_v1): EU legal entity + EU-hosted SaaS offering. Source |
| Fair | Openness Open source or open standards? Are independent implementations possible? | 5 | Rule baseline (rubric_v1): license classified as open-source family. Source |
| Secure | IT security Authentication, encryption, patch cadence and independent audit. | 4 | Cryptee uses client-side encryption (AES-256) and zero-knowledge architecture for data security. Source |
| Secure | User security 2FA, roles, phishing resistance and safe defaults. | 3 | Two-factor authentication (2FA) is supported via TOTP or hardware keys. Source |
| Secure | Personal data GDPR fit: DPA, residency, sub-processors and Schrems II posture. | 4 | Cryptee states that user data is encrypted client-side and not stored in plaintext. Source |
Indicative scores from public information — how we score.