Resource Review11 min read

One Church Software / My One Church App

4.2App Store rating · 23 ratings

One Church Software is a capable all-in-one ChMS with contacts, groups, check-in, giving, events, serving, sermons, forms, and a free shared member app—but profile-based pricing and add-ons accumulate, sensitive church data demands disciplined permissions, and its store privacy labels show only part of the service.

Starting price
Core from $58/mo · shared My One Church app included
Free tier
No
Platforms
Web · iPhone · Android · shared and branded member apps
Developer
One Church Software, Inc.
Launched
2015
Updated
Aug 2, 2026
$58 monthly · $556.80 annuallyCore start
Shared app included · App Builder $49/mo · Branded $295/moMember app
About 4.2 from 23 US ratingsApp Store
About 4.4 · 10K+ downloads · 70+ reviewsGoogle Play
Version 2.3.1 · January 2026Latest app

The verdict

One Church Software covers most of the operational loop a small or midsize congregation expects from a modern church management system: people, households, groups, attendance, child check-in, forms, events, contributions, giving, communication, serving, service plans, sermons, metrics, reporting, workflows, and member self-service. The included My One Church App is a practical shared container rather than a standalone app anyone can use; a church must already subscribe. Pricing is reasonably visible but needs full-cost modeling because App Builder, a branded app, accounting, texting, storage, deposit tools, training, migration, payment processing, and other options sit outside Core. The vendor publishes useful security claims and granular profile privacy settings, yet churches remain responsible for permission design, data minimization, child-safety practices, payment compliance, exports, and incident planning. Pilot with a representative team and a written governance checklist before migrating the congregation.

Try One Church Software / My One Church App

Opens onechurchsoftware.com

One Church Software is a cloud church management system, commonly shortened to ChMS. Administrators use the web platform to maintain people and household records, coordinate groups and events, track attendance, receive contributions, create forms, schedule volunteers, plan services, publish sermons, report metrics, and communicate. Members use a browser portal or the My One Church App to find their church, update profiles, join groups, register and pay for events, give, pre-check a family, view teachings, consult a directory when allowed, and manage serving availability.

The faith.tools listing is named One Church Software, while the exact Apple and Google product is My One Church App. They are two views of the same service, not interchangeable products. The mobile app has no useful independent free mode: the user’s church must maintain a One Church account. Every subscription includes access to the shared native app. An optional $49-per-month App Builder lets the organization arrange mobile screens and navigation; the $295-per-month Branded App tier supplies a church-branded iOS and Android product, includes App Builder, and requires a 12-month commitment.

Current public pricing begins at $58 per month for Core, or $556.80 when paid annually, and rises with profile count and the Core+ package. Core already includes a substantial module list. Separately priced options include accounting, branded-app services, texting, storage above the allowance, remote-deposit tools, training, migration, and Chat Pro, while online giving adds payment-processing rates. A church should price its actual profile band, message volume, storage, giving mix, implementation labor, required modules, and contract term—not quote the attractive base number in isolation.

This independent review is based on One Church Software’s public feature, pricing, app, help, privacy, security, permission, and payment pages; the exact Apple and Google listings, release history, reviews, and data labels; and faith.tools. We did not open a trial, migrate a database, configure permissions, run a live check-in, reconcile a contribution batch, process a gift, build an app, send messages, test backups or recovery, request deletion or export, interview a customer, or conduct a security, privacy, accessibility, PCI, accounting, safeguarding, availability, penetration, or code audit. Prices and profile bands can change.

✓ The good

  • Broad core suite - contacts, households, events, reports, forms, check-in, contributions, connections, sermons, serving, groups, service planning, communication, settings, and metrics reduce tool sprawl
  • Shared native member app included - every subscribed church can offer iOS and Android self-service without first buying a branded app
  • Granular profile visibility - individuals can mark fields for everyone, group members, leadership, or keep the profile unlisted, subject to church controls
  • Published security overview - encryption, password hashing, backups, scans, permission tools, and payment-provider responsibilities are documented more openly than at many small ChMS vendors
  • Active operational development - version 2.3.1 shipped in January 2026 with fixes for group email and serving availability after a larger platform transition
  • Flexible upgrade path - a church can begin with the shared app, add configurable screens, and move to a branded app only if adoption justifies the cost

✗ Watch out

  • Total price grows through add-ons - app branding, App Builder, accounting, texting, storage, OCR deposits, training, migration, and processing can materially exceed Core
  • No free church plan - the free mobile download is access to a paid organization account, not a free ChMS for an independent user or congregation
  • Sensitive centralized data - children, attendance, giving, contact, group, prayer, serving, demographic, and family records create serious misuse and breach consequences
  • App ratings are mixed and small - Apple averages roughly 4.2 from 23 US ratings, and 2026 Android reviews report login, black-screen, and navigation issues around platform updates
  • Store privacy is incomplete context - Apple lists only unlinked device and crash data even though the underlying church service necessarily processes member records and transactions
  • Migration and governance remain church work - buying software does not clean duplicates, define retention, establish lawful access, train volunteers, or create an incident plan

Best for

  • Small and midsize churches seeking one integrated system rather than separate people, events, giving, check-in, service, and communication tools
  • Congregations satisfied with a shared member app or willing to pay later for configurable or branded mobile presentation
  • Teams prepared to appoint a data owner, design roles, train users, audit access, and maintain backup exports and incident procedures
  • Churches able to model profile count, messaging, payment, storage, implementation, and app costs before signing

Avoid if

  • You need a permanent free ChMS, a mobile app that works without a church subscription, or one flat price including every optional service
  • You cannot define who may see children, giving, pastoral, directory, attendance, demographic, and household information at field level
  • You require published independent security certifications, guaranteed recovery objectives, a public uptime history, full subprocessor list, or enterprise contract terms before a pilot
  • Your accounting, denomination, multisite, workflow, API, data-residency, accessibility, or regulatory requirements have not been confirmed in writing

What One Church Software / My One Church App is

One Church Software is both a staff system of record and a member engagement layer. The database links individuals to households, groups, events, contributions, serving assignments, communications, forms, attendance, and permissions. The member surfaces expose only the subset a person’s role and the church’s configuration allow. That integration can eliminate duplicate entry and make follow-up much easier.

Integration also concentrates risk. A church database can reveal religious affiliation, family relationships, a child’s routine, contact details, donations, group participation, attendance patterns, notes, pastoral circumstances, and volunteer roles. Even ordinary directory fields—birthday, marital status, address, ethnicity, occupation, phone, and social profiles—can become sensitive in combination. A secure vendor is necessary, but correct local configuration and restrained collection are equally important.

The included shared app lowers the mobile threshold without forcing a branded-app contract

Many churches want members to register, give, pre-check children, find a group, view sermons, and update contact information on a phone, but do not need a unique app-store listing. My One Church App lets participating congregations offer those functions inside one shared container. A mobile-friendly web portal remains available for the full feature set, reducing dependence on a native install.

The tiering is sensible when expectations are clear. Shared branding can confuse members searching the store; App Builder improves navigation but does not create a standalone brand; the $295 branded tier is expensive and contract-bound. Measure member adoption, task completion, support volume, accessibility, and push value in the shared app before committing. Also confirm who controls developer accounts, reviews, certificates, source assets, notifications, and transition if the church leaves.

People, groups, events, and serving create one operational graph

A member can belong to a household and groups, register for events, submit forms, indicate serving availability, receive messages, and appear in attendance or connection workflows. Version history shows expanding calendar, media, group membership and administration, directory contacts, push inbox, sermon search, files, notes, attendance, and profile functions.

The value is fewer disconnected lists. The danger is permission creep. One Church says the default Guest role is restrictive, but a non-guest user with no added rights can see the directory, subject to privacy settings. Churches should begin with least privilege, separate staff from volunteer roles, review group-leader access, test impersonated accounts, remove dormant users, and audit export capability on a schedule.

Giving and contributions connect the member experience to finance

Members can give online and pay for events, while staff record contributions, funds, statements, deposits, and reporting in the same ecosystem. One Church says current electronic payments use Usio, card and bank details are encrypted, and sensitive payment credentials are not stored by the church. Accounting and remote-deposit capabilities carry separate charges.

The vendor’s payment design does not remove the church’s responsibilities. Its help center says each church completes an annual SAQ A process through VikingCloud and warns against collecting card details manually. Finance leaders should document processor contracts, fees, refunds, chargebacks, reconciliation, restricted funds, role separation, audit trails, donor anonymity, retention, and the boundary between ChMS records and accounting books.

Check-in and family pre-check can shorten lines while exposing child patterns

The app lets a family pre-check before arrival and present a QR code, while the administrative system supports check-in workflows and labels. Used well, this reduces Sunday bottlenecks and transcription errors, especially for recurring families. Event and group attendance can support care and planning.

Child information deserves a higher standard than ordinary directory data. Minimize birth dates, medical notes, custody information, photos, pickup authorizations, schedules, and location history; restrict access to trained roles; prevent directory exposure; secure printers and discarded labels; establish guardian verification and emergency procedures; and delete data on a defensible schedule. Convenience must not become silent surveillance of children or vulnerable adults.

Pricing

Best value

Core

From $58/mo

The starting profile band was $58 month-to-month or $556.80 annually when reviewed. Includes the main ChMS modules and access to the shared My One Church App; price rises by profile count.

Core+

From $82/mo

The higher package started at $82 monthly or $787.20 annually for the entry profile band. Compare its exact current additions with Core rather than buying by name alone.

App Builder

$49/mo

Adds configurable mobile screens and navigation while remaining inside the shared My One Church App. The free shared app itself is included with all ChMS plans.

Branded App

$295/mo

Includes App Builder and a branded iOS and Android presence with unlimited push notifications. A 12-month commitment is advertised; confirm store ownership and exit behavior.

Common extras

Varies

Accounting $36/mo, Chat Pro $9/mo, messaging, payment processing, storage, deposit tools, migration, and training may apply. Recalculate from current official prices and usage.

Begin with the correct profile band. Public starting figures are not a quote for every church, and imported inactive or duplicate people can push the count upward. Ask exactly which records count, how contacts are archived, when overages recalculate, whether annual payment is refundable, and how pricing changes during growth or merger.

Core appears broad enough for many churches, so build a requirements matrix before choosing Core+. Map every required workflow to a named module, owner, permission, report, integration, and acceptance test. Do not pay for a package because its label sounds future-proof.

Model extras over three years. Add $49 monthly if configurable shared-app navigation is necessary or $295 monthly for branded apps, then accounting, texting at the published setup and per-message rates, storage above five gigabytes, giving processing, OCR deposits, Chat Pro, migration, training, hardware, labels, and staff time. The branded app alone is $10,620 across a three-year term before other extras.

Exit cost matters too. Obtain a sample full export, attachments, contribution history, notes, forms, media, audit records, family relationships, app content, and identifiers. Confirm export format, support fees, deletion timetable, read-only access, branded-app shutdown, and what members experience after cancellation.

Where One Church Software / My One Church App falls behind

Store privacy scope. Apple lists only device identifier and crash data as unlinked, which may describe native-app telemetry but does not explain the member data processed through the One Church service. Publish separate controller/processor maps for app telemetry, church records, giving, communications, support, websites, and each optional module.

Independent assurance. The vendor describes 256-bit SSL, hashed and salted passwords, nightly geographically distributed backups retained up to six months, scanning, penetration testing, PCI status, and permissions. Publish current audit scope, certificate or report availability, recovery objectives and tests, subprocessor list, incident history, vulnerability disclosure, encryption at rest, key management, staff access, and customer notification terms.

Mobile reliability and accessibility. Recent Android reviews report black screens and login failures around the version 7 transition, and another criticizes a difficult menu target. Publish incident notes, supported app versions, forced-upgrade handling, status history, screen-reader and large-text results, keyboard access, contrast, captions, and remediation targets.

Permission governance. Supply tested least-privilege role templates for pastors, finance staff, children’s workers, group leaders, volunteers, auditors, communications, and guests; show risky grants; require multifactor authentication for privileged roles; log bulk views and exports; and schedule access recertification.

Lifecycle and portability. Document retention and deletion by record type, legal holds, individual requests, church closure, administrator departure, denominational transfer, merger, and contract termination. A six-month backup period should not leave deleted personal data conceptually undefined.

Pricing comprehension. Put a configurable total-cost calculator beside the plan table, including profile bands, annual discount, app tiers, accounting, messages, storage, payments, deposit services, migration, training, taxes, commitment, and termination. Churches should not need a spreadsheet to discover the actual stack price.

One Church Software vs. Planning Center vs. Breeze

One Church Software emphasizes a broad integrated Core and an included shared member app, with optional configurable and branded-app tiers. Planning Center is a polished modular suite whose Services product is particularly strong for worship planning and volunteer schedules. Breeze favors a simpler small-church experience and straightforward administration. Tithely and Subsplash lean more heavily toward giving, websites, media, and branded engagement bundles.

A feature checklist will not settle the choice. Run the same scenarios in each finalist: add a household, restrict a sensitive field, import contributions, issue statements, register and refund an event, pre-check a child, schedule a volunteer, send a segmented message, build a report, handle a duplicate, export everything, remove an administrator, and complete the task with a screen reader. Include both staff and ordinary members.

Choose One Church when its integrated modules and included shared app fit the workflow and its full modeled cost beats assembling alternatives. Choose Planning Center when deep service planning and modular maturity matter most, Breeze when administrative simplicity dominates, or a communications-first platform when website, media, giving, and branded mobile delivery are the central needs. Contract, security, support, and exit evidence should break close ties.

The bottom line

One Church Software is a credible ChMS contender with a strong core module list and a practical mobile ladder from included shared app to fully branded presence. It can reduce duplicate entry and give members a coherent path for groups, events, giving, pre-check, sermons, profiles, and serving. The decision should not be made on the free app download or $58 headline. Price the full profile band and extras, test real workflows and accessibility, demand security and recovery evidence appropriate to the congregation, and govern every sensitive field with least privilege. For a prepared small or midsize church, it can consolidate a fragmented operation. For an unprepared one, it merely centralizes the fragmentation and risk.

Alternatives to One Church Software / My One Church App

Frequently asked questions

Is My One Church App free?

The app is free to download, and the shared member app is included with One Church ChMS plans. It does not work as an independent free church system; your church must already subscribe.

How much does One Church Software cost?

Core started at $58 monthly or $556.80 annually for the entry profile band when reviewed. Core+ started at $82 monthly. Profile count and optional services change the total, so obtain a current quote.

What is the difference between App Builder and Branded App?

The $49-per-month App Builder customizes screens and navigation inside the shared My One Church App. The $295-per-month Branded App includes App Builder and supplies branded iOS and Android apps under a 12-month commitment.

Does One Church Software handle online giving?

Yes. It supports contributions and member giving, with payment processing handled through current vendor integrations such as Usio. Processing rates, PCI tasks, accounting, refunds, and reconciliation require separate review.

Is One Church Software secure?

The vendor publishes claims about encryption, hashed passwords, backups, scanning, testing, PCI compliance, and permissions. A church should request current independent evidence, recovery terms, subprocessors, incident procedures, and contract commitments appropriate to its risk.

Can members control directory privacy?

One Church documents visibility choices such as everyone, group members, church leadership, and unlisted for profile fields. Church administrators still need to configure roles carefully and explain which leadership users can see restricted data.

What should we test before migrating?

Test permissions, households, duplicates, giving, statements, refunds, check-in, groups, events, forms, serving, communication, reports, accessibility, integrations, imports, complete exports, administrator removal, backup recovery evidence, and member support.

Sources & further reading

More Church Management Software

Subsplash 5.0The all-in-one church platform megachurches keep choosing - fully custom-branded apps across phone, web, and TV that make a 5,000-member ministry feel like an Apple keynote.VisitorReach 4.9VisitorReach combines managed digital advertising, local texting numbers, AI-assisted replies, automated follow-up journeys, a mobile inbox, NFC connection cards, coaching, and church-database integrations—but unpublished prices and the sensitivity of seeker conversations make this a procurement decision, not a simple app download.Gracely 4.9Gracely is an unusually affordable church-management platform with unlimited members, free migration, a capable free plan, flat-rate paid tiers, giving, accounting, child check-in, communication, websites, and the My Gracely member app—but its low price should not shorten security, privacy, finance, or safeguarding review.Called 4.9A thoughtfully designed church-community layer for chat, groups, prayer, events, and shepherding—stronger on engagement than full ChMS operations, with a costly pricing cliff and conflicting youth rules.Flare - For Groups 4.9Flare is a genuinely free, genuinely capable group app with attendance tracking, admin-only announcements and QR check-in - and its own site, FAQ, tutorials and 28 blog posts never once mention a church, a ministry, or prayer.Clearstream 4.9Bootstrapped since 2010, founder-owned, church-only since around 2016, with the deepest integration list in church texting and a compliance position most buyers never think to ask about - sold on a credit ladder that punishes buying too small.
Try One Church Software / My One Church App