Transparency alternatives to Articulate
Other Learning management vendors we measure, sorted by how much we found at them and not at Articulate. This is a comparison of disclosure, not of features or fitness.
12 shown of 42 that differ from Articulate on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Articulate has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Articulate” is the one that closes them.
| Vendor | Score | Found there, not found at Articulate | Found at Articulate, not found there | |
|---|---|---|---|---|
| TalentLMStalentlms.comSee also Transparency alternatives to TalentLMS | 52/100 | 5 Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS, +2 | 3 Data location stated, Status page with history, security.txt (RFC 9116) | Compare |
| Skilljarskilljar.comSee also Transparency alternatives to Skilljar | 70/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 security.txt (RFC 9116) | Compare |
| Codiocodio.comSee also Transparency alternatives to Codio | 57/100 | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| LearnWorldslearnworlds.comSee also Transparency alternatives to LearnWorlds | 57/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Teachableteachable.comSee also Transparency alternatives to Teachable | 57/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Anthologyanthology.comSee also Transparency alternatives to Anthology | 48/100 | 4 Subprocessor list, No third-party tracking before consent, Notice before subprocessors change, +1 | 3 Data location stated, Public pricing, Certifications named | Compare |
| D2Ld2l.comSee also Transparency alternatives to D2L | 43/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Named privacy contact | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| eloomieloomi.comSee also Transparency alternatives to eloomi | 39/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Named privacy contact | 3 Data location stated, Public pricing, security.txt (RFC 9116) | Compare |
| Continucontinu.comSee also Transparency alternatives to Continu | 30/100 | 3 Uptime SLA with a figure, HTTPS enforced with HSTS, Named privacy contact | 3 Data location stated, Status page with history, security.txt (RFC 9116) | Compare |
| Arloarlo.coSee also Transparency alternatives to Arlo | 39/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Instructureinstructure.comSee also Transparency alternatives to Instructure | 30/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Data location stated, Public pricing | Compare |
| iSpringispringsolutions.comSee also Transparency alternatives to iSpring | 30/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 4 Data location stated, Status page with history, Certifications named, +1 | 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.