SaaS Ranking

Alternatives to Tithe.ly

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

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

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

VendorScorePublishes, and Tithe.ly does notTithe.ly publishes, and they do not
Churchsuitechurchsuite.com 26/100 3 Public pricing, Certifications named, security.txt (RFC 9116) 3 Data location stated, Status page with history, Named privacy contact Compare
Pushpaypushpay.com 39/100 2 Public pricing, security.txt (RFC 9116) 1 Status page with history Compare
Worship Toolsworshiptools.com 35/100 2 Public pricing, security.txt (RFC 9116) 2 Status page with history, Named privacy contact Compare
Aplosaplos.com 22/100 2 Public pricing, Certifications named 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact Compare
Church Socialchurchsocial.com 13/100 2 Public pricing, security.txt (RFC 9116) 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 Compare
Church Community Builderchurchcommunitybuilder.com 43/100 1 Public pricing nothing Compare
CHMeetingschmeetings.com 35/100 1 Public pricing 1 Status page with history Compare
Multitracksmultitracks.com 35/100 1 Public pricing 1 HTTPS enforced with HSTS Compare
Breezebreezechms.com 26/100 1 Public pricing 2 Data location stated, Named privacy contact Compare
Churchdeskchurchdesk.com 17/100 1 Public pricing 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact Compare
Elvantoelvanto.com 17/100 1 Public pricing 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact Compare
Faithlifefaithlife.com 17/100 1 Certifications named 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact 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.