SaaS Ranking

Alternatives to Servant Keeper

Other Church and community management vendors we measure, sorted by how much they publish that Servant Keeper does not. This is a comparison of disclosure, not of features or fitness.

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

Servant Keeper has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Servant Keeper does not” is the one that closes them.

VendorScorePublishes, and Servant Keeper does notServant Keeper publishes, and they do not
Planning Centerplanningcenter.com 57/100 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 1 Data location stated Compare
Pushpaypushpay.com 39/100 2 security.txt (RFC 9116), Named privacy contact 1 Status page with history Compare
Churchsuitechurchsuite.com 26/100 2 Certifications named, security.txt (RFC 9116) 2 Data location stated, Status page with history Compare
Church Community Builderchurchcommunitybuilder.com 43/100 1 Named privacy contact nothing Compare
CHMeetingschmeetings.com 35/100 1 Named privacy contact 1 Status page with history Compare
Multitracksmultitracks.com 35/100 1 Named privacy contact 1 HTTPS enforced with HSTS Compare
Tithe.lytithe.ly 35/100 1 Named privacy contact 1 Public pricing Compare
Worship Toolsworshiptools.com 35/100 1 security.txt (RFC 9116) 1 Status page with history Compare
Subsplashsubsplash.com 32/100 1 Named privacy contact 1 Data location stated Compare
Church Metricschurchmetrics.com 26/100 1 Named privacy contact 2 Status page with history, Public pricing Compare
iKnow Churchiknowchurch.co.uk 26/100 1 Named privacy contact 2 Status page with history, Public pricing Compare
Aplosaplos.com 22/100 1 Certifications named 2 Data location stated, HTTPS enforced with HSTS 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.