SaaS Ranking

Alternatives to Lillio

Other Childcare management vendors we measure, sorted by how much they publish that Lillio does not. This is a comparison of disclosure, not of features or fitness.

12 shown of 22 that differ from Lillio on at least one criterion we measured for both. Public transparency score, not a product or security rating.

Lillio has 11 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and Lillio does not” is the one that closes them.

VendorScorePublishes, and Lillio does notLillio publishes, and they do not
Cheqdincheqdin.com 52/100 6 Data processing agreement, Data location stated, Public pricing, +3 1 security.txt (RFC 9116) Compare
Ovivioovivio.com 48/100 6 Data processing agreement, Status page with history, Public pricing, +3 1 security.txt (RFC 9116) Compare
Famlyfamly.co 48/100 5 Data location stated, Status page with history, Public pricing, +2 nothing Compare
Educageteduca.com 43/100 4 Subprocessor list, Data location stated, Public pricing, +1 1 security.txt (RFC 9116) Compare
Illumineillumine.app 30/100 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 1 security.txt (RFC 9116) Compare
Daily Connectdailyconnect.com 30/100 3 Data location stated, Public pricing, HTTPS enforced with HSTS 1 security.txt (RFC 9116) Compare
Little Birdlittle-bird.de 29/100 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact 1 security.txt (RFC 9116) Compare
Tadpolestadpoles.com 29/100 3 Data location stated, Public pricing, Named privacy contact 1 security.txt (RFC 9116) Compare
Connect Childcareconnectchildcare.com 26/100 3 Data location stated, Public pricing, Named privacy contact 1 security.txt (RFC 9116) Compare
Storyparkstorypark.com 22/100 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact 1 security.txt (RFC 9116) Compare
Kigarookigaroo.de 17/100 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact 1 security.txt (RFC 9116) Compare
Brightwheelmybrightwheel.com 22/100 2 Data location stated, Status page with history 1 security.txt (RFC 9116) Compare

Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.