About
Software for running a local church, built by people who run one
ChurchOS replaces the pile of subscriptions a church accumulates — website, directory, check-in, service planning, presentation, streaming — with one system where those parts know about each other.
One system, not seven subscriptions
A church website that does not know who attends, a directory that does not know who gave, a presentation tool that does not know the sermon — each seam is somebody re-typing something on a Saturday night. ChurchOS is built as one system so the joins are the product rather than an integration project.
The church owns its people
Congregation records belong to the church that gathered them. ChurchOS holds them on that church's instructions, does not use them for anything else, and does not treat a departing church as a retention problem.
Separation enforced by the database
Tenant isolation is a row-level security policy in PostgreSQL, not a `where` clause somebody has to remember. The policies apply even to the account that owns the schema, and a test suite attempts cross-church reads in raw SQL on every change.
Confidential means confidential
A pastoral note written in confidence is readable by the people the church chose and by nobody else — not by an administrator, not by a volunteer with a wide role. Reads of sensitive records are recorded.
Say what is not built
This site names the modules that do not exist yet, on the pages that would otherwise sell them. Marketing copy that outruns the software is the thing a church quotes back during a complaint, and it is not worth the signup.
No claim we cannot evidence
No customer counts, no testimonials, no uptime figure, no security certification. ChurchOS is pre-launch and has not completed an external audit or a SOC 2 examination. When any of that changes it will be stated with the evidence behind it.
Where ChurchOS actually stands
What works today, and what does not
Kept on this page rather than in a footnote. A module counts as available only where the records, the endpoints and the interface all exist and a test drives the whole workflow — a page that renders sales copy does not count.
A church can use these now
Church website builder
Pages, sections, theming and publishing at the church's own free ChurchOS address, with a visitor never seeing a half-finished edit.
People and households
Directory, relationships, and pastoral notes with their own visibility rules.
Attendance and connection
Self and steward check-in for adults, guest capture, connect cards, follow-up.
Service planning
A running order the whole team works from on a Sunday morning.
Worship and presentation
Main screen, stage display, stream output and congregation phones from one cue list.
Livestream and production
OBS control, overlays, and a LIVE status derived from the stream rather than a button.
Bible, study and sermons
Passage lookup, study workspace, outline building and a sermon archive.
These are not built
Online giving
No donation, fund or gift records exist, and no payment processor is connected.
Events and registration
No event or registration records exist.
Pastoral appointments
No booking or availability exists.
Children's check-in
No child, guardian or authorised-pickup records exist. Do not use ChurchOS for child safety.
Subscription billing
Nothing can be charged. There is no checkout, invoice or billing portal.
Self-service data export
A church cannot yet download its own records without asking us.
Your own domain name
A church can use its free ChurchOS address; connecting a domain you own is not yet wired up.
No dates are given for the second list, because a date given to a church becomes a plan that church builds around.
How ChurchOS is run
ChurchOS is pre-launch. It is not generally available, nobody is being charged for it, and the churches using it are doing so in direct conversation with us rather than by buying a subscription. That is the honest description of the stage it is at, and it is the reason the terms and privacy pages on this site are marked as drafts awaiting legal review rather than presented as agreed.
If you are weighing ChurchOS against something established, that context should count against us, and we would rather you had it before the conversation than during it.