- Starting price
- Early access free; public pricing also says $30/month
- Free tier
- Yes
- Platforms
- Web · Mobile-responsive web app · Planning Center integration
- Developer
- Gatherly
- Launched
- 2025
- Updated
- Aug 9, 2026
The verdict
Gatherly understands a real church problem: texts, email threads, generic group chats, prayer updates, and ministry signals are scattered. Its Circles, announcements, messages, prayer wall, answered-prayer flow, engagement view, personal onboarding, and Planning Center sync could create a calmer community layer. But the live homepage says selective early access with extended free use and future founding pricing while the public application still presents a $30 monthly Pro plan with a 30-day trial. More importantly, prayer requests, religious affiliation, private messages, membership, and imported people records demand a DPA, subprocessor list, verified security, granular roles, moderation, retention, deletion, export, child safeguards, and breach commitments that the short October 2025 policies do not provide. Demo with synthetic data; admit a small adult pilot only after written answers and a contract.
Try Gatherly ↗Opens gatherly.church
Gatherly is an emerging church communication and community platform. Its current early-access page promises one place for groups, announcements, messages, prayer requests, answered-prayer celebrations, and engagement beyond Sunday. Ministry-specific Circles can organize teams, life stages, and small groups. Leaders are told they can see which groups are thriving and where people may need support. Planning Center integration is offered during onboarding to sync member data, and Gatherly says each selected church receives personal help importing members and configuring the product.
The public go-to-market story is not settled. The main site invites a limited set of “Founding Churches,” says applicants should hear back in two to three business days, offers extended free access during development, and promises founding pricing when the product is available. It explicitly says Gatherly may not suit a church wanting immediate self-service. Yet the deployed pricing experience and site metadata also describe Gatherly Pro at $30 per month, a 30-day free trial, unlimited members, messaging, prayer wall, daily devotionals, analytics, priority support, no setup fee, monthly auto-renewal, and Stripe billing. A church cannot infer which path governs its account.
The data is unusually sensitive even without a care-management module. The privacy policy says Gatherly may process name, email, church affiliation or membership, profile information, prayer requests, fellowship messages, usage, device and browser data, IP address, general location, and cookies. A prayer post can reveal health, pregnancy, loss, addiction, conflict, abuse, finances, immigration, sexuality, mental health, family identity, or third-party information. Membership itself conveys religious affiliation. Private community messages can become pastoral or safeguarding records regardless of the product’s intended scope.
We reviewed the current early-access landing page, deployed application routes, pricing presentation, feature language, Planning Center claims, privacy policy dated October 12, 2025, terms dated October 11, 2025, and visible application behavior on August 9, 2026. We did not request admission, create a church, pay through Stripe, import Planning Center data, post a prayer, send messages, inspect role enforcement, test moderation or notifications, request deletion, validate encryption or audits, benchmark performance, inspect mobile stores, or perform penetration, code, legal, privacy, doctrinal, accessibility, child-safety, or pastoral-record review.
✓ The good
- Focused church scope - Circles, announcements, messages, prayer, and group health address community work without pretending to be a full financial or service-planning suite
- Personal onboarding - early churches receive help creating groups, importing people, and configuring integrations instead of being left with an empty self-serve tenant
- Prayer has an ongoing loop - sharing, support, and answered-prayer celebration can keep prayer relational rather than reducing it to a one-time form
- Planning Center connection - importing an existing people set can reduce duplicate entry for churches already using that ecosystem
- Early customers can shape development - direct feedback and priority support give a thoughtful pilot church more influence than a mature vendor normally offers
- Extended early-access use is free - selected churches can evaluate workflows before ordinary paid availability, provided data risk is contained
- Simple public price concept - if the $30 Pro offer becomes authoritative, unlimited members and core communication at one flat monthly price would be unusually accessible
- Fit guidance is candid - the homepage says the product is early and is not for churches that require immediate, fully self-service access
✗ Watch out
- Pricing and availability conflict - selective free early access with future pricing coexists with a public $30 monthly plan, 30-day trial, and automated subscription path
- Sensitive-data governance is incomplete - the policy names prayer, membership, messages, usage, IP, and location but omits a complete processor, retention, deletion, transfer, backup, and legal-role model
- Security claims lack evidence - “all communications” encryption, secure storage, audits, and access controls are asserted without scope, architecture, dates, standards, results, or independent reports
- “Church-only” is too absolute - data cannot literally stay only within a church if hosting, authentication, analytics, payment, support, monitoring, email, or Planning Center providers process it
- Planning Center detail is missing - no public scope list, field map, sync direction, conflict handling, household/child rules, historical range, revocation, or deletion cascade is provided
- Prayer moderation is underspecified - confidentiality, audience, anonymous posting, third-party consent, urgent-risk escalation, reporting, blocking, editing, retention, and leader responsibility need explicit controls
- Role and audit maturity is unclear - churches need circle leaders, pastors, admins, ordinary members, suspended users, departed staff, impersonation safeguards, and immutable activity records
- No established operating evidence - there is no public uptime history, customer count, app-store record, completion data, security assurance, accessibility conformance, or long-term support track record
- Terms are too light for institutions - the agreement does not visibly resolve data ownership, confidentiality, organization authority, IP, termination export, dispute, safeguarding, or service continuity in enough depth
Best for
- A small adult founding-church cohort willing to co-design the product under a written pilot agreement and strict data minimization
- Planning Center churches seeking a focused community and prayer layer rather than a replacement ChMS
- Ministry teams with an accountable privacy lead, safeguarding process, moderation owner, and capacity to test every role and notification
- A synthetic-data or staff-only proof of concept that can validate usability before any congregational invitation
- Churches that value personal onboarding and product influence more than immediate self-service maturity
Avoid if
- You require an established generally available platform, public uptime, mobile-store apps, independent security assurance, SLA, or a large support organization
- Your church will post counseling notes, abuse reports, medical records, children’s details, immigration status, financial cases, or other high-risk pastoral information
- Procurement requires a DPA, subprocessor list, SSO, MFA enforcement, granular roles, audit logs, data-region choice, backup/deletion specification, and incident notice
- You cannot reconcile the free early-access offer with the $30 trial and subscription terms in a signed order before entering data
- Members lack a private alternative to posting, a clear audience indicator, informed consent, reporting tools, and a human path for urgent or confidential prayer
What Gatherly is
Gatherly is a private church community workspace centered on Circles, communication, prayer, and engagement. The product aims to replace scattered texts, emails, and generic group chats with one member experience. Leaders can publish information, members can converse and pray, and analytics can show community activity. Planning Center can supply an existing people directory during supported onboarding.
It is not yet a demonstrated replacement for Planning Center, a complete ChMS, a confidential counseling record, a safeguarding case system, an emergency service, or an automatically safe social network. Early access means the product, policies, price, support, data model, and controls can change. Churches remain responsible for community rules, leader access, consent, pastoral response, record obligations, and alternatives for anyone who cannot or should not participate digitally.
Why early churches are interested in Gatherly: community and prayer are the product, not add-on modules
Large church suites often optimize databases, giving, check-in, schedules, or service operations. Generic group chats optimize rapid conversation. Gatherly places the space between Sundays at the center: a Circle with messages and announcements, a visible prayer rhythm, answered-prayer celebration, and enough engagement insight for a leader to notice whether the group is alive. Personal onboarding can translate that simple model into a church’s real ministries rather than asking users to configure dozens of unrelated modules.
Preserve simplicity through policy. Create only real ministry Circles with a named leader and backup; define who can discover, join, post, comment, moderate, export, and close each space; offer confidential pastoral contact outside the app; and keep sensitive prayer details out of public or broad groups. Measure whether people receive support, not raw posting frequency. A quiet member is not disengaged, a frequent poster is not necessarily healthy, and no dashboard should become a pastoral verdict.
Circles, announcements, and messages: consolidation must not erase boundaries
Circles organize ministries, life stages, teams, and groups, giving each a place for announcements and conversation. The promise is less fragmentation: a member knows where to find information, leaders are not copying the same message across texts and email, and newcomers can be oriented to the right spaces. Centralization can also improve handoff when a volunteer leader changes because communication history is not trapped in a personal phone.
Every Circle needs an audience model. Test private, hidden, discoverable, invitation-only, leader-only, and read-only behavior; household sharing; blocking; former-member removal; screenshots; search; file access; notification previews; exports; and deleted messages. A women’s recovery group, youth team, public events group, prayer circle, staff channel, and worship roster should not inherit identical defaults. Keep legal, employment, counseling, discipline, safeguarding, and medical records in systems designed for those purposes.
Prayer wall and answered prayers: spiritually meaningful, operationally high risk
The prayer experience lets members share requests, support one another, and mark or celebrate answers. This can extend congregational care beyond a weekly gathering and let a group pray with specificity. It also creates durable records about people who may never have agreed to appear: a spouse, child, patient, neighbor, employer, or person accused of wrongdoing can be named in someone else’s request.
Use a just-enough-information rule. Show the exact audience before posting; default to the smallest group; allow initials or category-only requests; warn against naming third parties; let authors edit, close, and delete; define leader moderation and reporting; and auto-expire ordinary requests. Provide private contact for abuse, self-harm, violence, child safety, illegal activity, or urgent needs and train leaders to escalate outside the app. “Answered” should never pressure a person to disclose an outcome or imply unresolved suffering reflects inadequate faith.
Planning Center sync and engagement analytics: useful context can become an unearned inference
Planning Center onboarding promises to sync member data so a church does not rebuild its directory manually. Engagement views then help leaders see activity across groups and identify where support may be needed. A well-designed connection could align existing people and membership structures, reduce duplicate accounts, and help a ministry owner notice an unanswered post or inactive Circle rather than surveilling every individual.
Require the complete data path. Which Planning Center products, OAuth scopes, fields, households, children, notes, photos, statuses, emails, phones, groups, campuses, and histories are read? Is there writeback? How are merges, removals, opt-outs, revocation, errors, and deletion handled? For analytics, expose formulas, time windows, missing-data behavior, source events, role visibility, corrections, and opt-out. Never infer spiritual health, risk, pastoral need, or commitment from logins, prayer posts, reads, or silence without human context and consent.
Pricing
Founding Churches early access
Extended free access
The current homepage offers selected churches free use while they help shape the product, personal onboarding, direct input, priority support, and future founding pricing. Acceptance is not immediate.
Gatherly Pro public route
$30/month
A separate deployed pricing experience advertises unlimited members, messaging, prayer wall, daily devotionals, analytics, priority support, and no setup fee. Confirm that it is currently orderable and authoritative.
Public trial claim
30 days free
The pricing flow describes a full-feature trial followed by monthly auto-renewal unless canceled. This conflicts with the selective extended-free early-access narrative and needs written reconciliation.
Planning Center onboarding
Shown as available
The main site says integration is available during onboarding to sync member data. Pricing, scopes, migration work, support, sync volume, and continued availability are not separately documented.
Governed pilot
Staff time + contract review
Even if software use is free, data mapping, consent, moderation, safeguarding, training, export, deletion testing, access review, and support ownership have real costs.
Treat pricing as unresolved. The authoritative-looking main page offers extended free early access and future founding pricing, while the deployed pricing route and metadata describe $30 per month after a 30-day trial. Both are live product evidence.
Ask Gatherly to identify the governing offer in writing: eligibility, features available now, trial start, card requirement, monthly renewal, taxes, limits, support, future founding rate, price protection, cancellation, export, and deletion.
A $30 unlimited-members plan would be competitively inexpensive. Low price does not reduce privacy, moderation, security, accessibility, or safeguarding obligations; it may mean a young vendor has fewer people and controls to meet them.
Early access should not be paid for with real prayer histories. Use synthetic profiles for configuration, then a small adult staff or leader cohort with low-risk content and a short deletion date. Expand only after contractual and technical gates pass.
Plan the exit before import. Preserve the Planning Center source, identify Gatherly-only records and files, schedule exports, capture consent and moderation evidence, test cancellation, and verify deletion from live systems, processors, and backups.
Where Gatherly falls behind
Publish one authoritative status and pricing page reconciling Founding Churches, extended free access, $30 Pro, 30-day trial, auto-renewal, Stripe checkout, included features, limits, availability, founding rate, and cancellation.
Provide a DPA defining controller/processor roles, purpose instructions, religious and prayer data, confidentiality, security, subprocessors, international transfers, assistance, audit rights, incident notice, return, deletion, and church termination.
Name every provider used for hosting, database, storage, authentication, email, notifications, analytics, monitoring, payment, support, backups, and Planning Center, with location, purpose, data categories, retention, and change notice.
Substantiate encryption, secure storage, audits, access controls, and “church-only” claims with architecture, in-transit and at-rest scope, key management, MFA, role matrix, logging, testing dates, independent reports, vulnerability intake, recovery, and uptime.
Document prayer and community safety: audiences, privacy defaults, anonymous or confidential paths, third-party consent, reporting, blocking, appeals, urgent-risk escalation, mandated-reporting boundaries, child accounts, guardian controls, and moderation records.
Publish Planning Center scopes, products, fields, direction, frequency, error handling, household and minor behavior, photos and notes, historical range, raw staging retention, revocation, writeback, merge, export, and deletion cascade.
Give churches configurable retention, auto-expiration, member access/correction/export/deletion, verified tenant deletion, backup schedule, immutable audit logs, granular roles, SSO/MFA roadmap, accessibility report, and data portability.
Gatherly vs. Flocknote vs. Church Center vs. private group chat
Gatherly offers a more focused prayer-and-community vision than a full ChMS and a cleaner church identity than a generic chat. Flocknote is an established church email and texting platform with groups and broad adoption; Planning Center Church Center gives congregants access to groups, events, giving, registrations, directory, and other connected modules; Slack, WhatsApp, GroupMe, or Facebook Groups may already be familiar but introduce general-purpose identities, metadata, policies, and boundary problems. Gatherly’s possible $30 flat price and personal onboarding are attractive, while its maturity and governance trail far behind the established options.
Compare one real workflow without real secrets. Create a private adult Circle, invite and remove users, post a low-risk prayer, report it, edit and delete it, change a leader, inspect notification previews, search, export, revoke Planning Center, correct a merged person, cancel, and request tenant deletion. Then ask what a non-smartphone member does and what happens during urgent harm. The best platform is the one whose social design, policies, and staff practice protect the person when the happy-path demo ends.
The bottom line
Gatherly’s product instinct is good: church community should not require members to search old text chains, live inside an advertising network, or treat prayer as an afterthought. A clean Circle, clear announcement, supportive prayer exchange, answered-prayer celebration, and thoughtful leader signal can strengthen life between Sundays. The implementation is not procurement-ready yet. Conflicting live pricing, selective early access, limited policy detail, unspecific security claims, unnamed processors, an undocumented Planning Center map, and absent prayer moderation and child safeguards matter more than a polished screen because the records disclose belief and vulnerability. Continue the conversation if your church wants to shape an early product, but begin with synthetic data and require written price, DPA, security, subprocessor, retention, deletion, export, roles, moderation, safeguarding, accessibility, and incident answers. A founding church should help Gatherly mature without making congregants the unknowing test dataset.
Alternatives to Gatherly
Frequently asked questions
Is Gatherly available now?
The main site is accepting selected Founding Churches through an early-access request and says it replies within two to three business days. It explicitly says immediate self-service may not be a fit, although deployed subscription screens also exist.
How much does Gatherly cost?
The main page promises extended free access while building and future founding pricing. A separate live pricing route says $30 per month after a 30-day trial. Obtain the governing offer in writing before onboarding.
What does Gatherly include?
Public materials describe Circles or groups, announcements, messages, a prayer wall, answered prayers, engagement analytics, daily devotionals in the Pro presentation, priority support, and personal onboarding.
Does Gatherly integrate with Planning Center?
Yes, the homepage says Planning Center integration is available during onboarding to sync member data. Public pages do not yet give the exact products, scopes, fields, direction, history, writeback, revocation, or deletion behavior.
Is Gatherly safe for prayer requests?
It has a privacy policy and makes encryption and security claims, but public evidence is not enough for highly sensitive content. Use minimal detail, small audiences, expiration, moderation, private alternatives, and a human urgent-risk process; avoid counseling or safeguarding records.
Does Gatherly keep data only inside my church?
The policy uses church-only language, but any hosted app normally relies on vendors for infrastructure and may use analytics, payment, monitoring, authentication, or messaging. Require a full subprocessor list and data-flow diagram rather than reading the phrase literally.
How should a church test Gatherly?
Start with synthetic users, then a time-limited adult staff pilot. Verify every role, Circle audience, notification, report, removal, export, Planning Center revoke, cancellation, and deletion before inviting members or allowing real prayer details.
