Alternatives to Rock RMS
Other Church and community management vendors we measure, sorted by how much they publish that Rock RMS does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 30 that differ from Rock RMS on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Rock RMS has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, 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 Rock RMS does not” is the one that closes them.
| Vendor | Score | Publishes, and Rock RMS does not | Rock RMS publishes, and they do not | |
|---|---|---|---|---|
| Planning Centerplanningcenter.com | 57/100 | 6 Subprocessor list, Status page with history, Certifications named, +3 | 1 security.txt (RFC 9116) | Compare |
| Church Community Builderchurchcommunitybuilder.com | 43/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 1 security.txt (RFC 9116) | Compare |
| Tithe.lytithe.ly | 35/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Pushpaypushpay.com | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Servant Keeperservantkeeper.com | 39/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| CHMeetingschmeetings.com | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Multitracksmultitracks.com | 35/100 | 3 Data location stated, Status page with history, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Subsplashsubsplash.com | 32/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Bible Appyouversion.com | 30/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Church Metricschurchmetrics.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| iKnow Churchiknowchurch.co.uk | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Worship Toolsworshiptools.com | 35/100 | 2 Data location stated, HTTPS enforced with HSTS | nothing | 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.