Transparency alternatives to ARMS
Other Software for local government vendors we measure, sorted by how much they publish that ARMS does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 64 that differ from ARMS on at least one criterion we measured for both. Public transparency score, not a product or security rating.
ARMS has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and ARMS does not” is the one that closes them.
| Vendor | Score | Publishes, and ARMS does not | ARMS publishes, and they do not | |
|---|---|---|---|---|
| Submittablesubmittable.com | 52/100 | 4 Subprocessor list, Data location stated, Notice before subprocessors change, +1 | 1 Uptime SLA with a figure | Compare |
| Fluxxfluxx.io | 43/100 | 4 Data location stated, Status page with history, security.txt (RFC 9116), +1 | 1 Uptime SLA with a figure | Compare |
| Foundantfoundant.com | 39/100 | 3 Data location stated, Status page with history, Named privacy contact | 1 Uptime SLA with a figure | Compare |
| Rekorrekor.ai | 39/100 | 3 Data location stated, Public pricing, Named privacy contact | 1 Uptime SLA with a figure | Compare |
| Accelaaccela.com | 35/100 | 3 Data location stated, Status page with history, Named privacy contact | 2 Certifications named, Uptime SLA with a figure | Compare |
| OpenGovopengov.com | 39/100 | 2 Data processing agreement, Status page with history | nothing | Compare |
| Polcopolco.us | 26/100 | 2 Data location stated, Named privacy contact | 2 Certifications named, Uptime SLA with a figure | Compare |
| ProudCityproudcity.com | 26/100 | 2 Public pricing, security.txt (RFC 9116) | 1 Certifications named | Compare |
| Apply4apply4.com | 17/100 | 2 Data location stated, Named privacy contact | 3 Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS | Compare |
| Granicusgranicus.com | 17/100 | 2 Status page with history, Named privacy contact | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | Compare |
| Zencityzencity.io | 17/100 | 2 Data location stated, Named privacy contact | 3 Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS | Compare |
| Axonaxon.com | 26/100 | 1 Data location stated | 1 Uptime SLA with a figure | 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.