The operating system for your church
Stop paying five companies for software that does not talk to itself. ChurchOS runs your website, your people, your services and your livestream from one record of the truth.
Free while ChurchOS is pre-launch · No card required · Nothing is charged
Good morning
Grace Community Church
Next: Sunday Gathering · 10:30
People
148
Guests
18
Last Sunday
133
Follow-ups
6
Attendance · last eight gatherings
Replaces the stack most churches are paying for
Why one system
The join is the product
Any of these can be bought separately. What no church can buy separately is the part where they agree with each other.
Product tour
What your church actually gets
Five surfaces, one system. Every preview below is drawn from the real interface rather than a screenshot that will go stale.
A website a volunteer can edit
Drag sections, change the words, see exactly what a visitor sees on a phone, then publish. Every church gets a free, permanent address at mychurchos.app.
Sundays at 10:30
You are welcome here, exactly as you are.
Latest message
This Sunday
Need prayer?
Security & trust
Your congregation's records deserve better than a spreadsheet
Churches hold some of the most sensitive information in a community — a note a pastor wrote in confidence, a family's address and phone number, who asked for prayer on Sunday. That is not ordinary customer data.
Church data is separated by the database
Every table carrying church data has a row-level security policy, enforced by PostgreSQL rather than by application code remembering to filter.
Pastoral notes are not staff-wide
A note written in confidence is readable by the people a church chose, and by nobody else — including administrators.
Credentials are never shown twice
Stream keys and OBS passwords are encrypted at rest and shown once. No screen in the product can display one afterwards.
Pricing
One price, the whole church
No per-module upsell and no charge per person. Every plan includes the website builder, a free permanent address at mychurchos.app and unlimited people.
Comparison
ChurchOS against a stack of separate tools
Not a claim that the alternatives are bad. Most are good at the one thing they do — which is the problem. The rows ChurchOS cannot do yet are in the same table rather than left out of it.
| Capability | ChurchOS | Separate tools |
|---|---|---|
| Church website a volunteer can edit | Included today | Separate product |
| People, households and attendance | Included today | Separate product |
| Service planning and presentation | Included today | Separate product |
| Livestream production and overlays | Included today | Separate product |
| One record shared by every module | Included today | Manual export and import |
| Your own domain name | Not built yet | Usually included |
| Online giving with statements | Not built yet | Separate product |
| A single bill | Not built yet | Four to six |
A row marked Not built yet does not exist in ChurchOS today and is not something a church can switch on. About lists every module in that state, and no dates are given for any of them. A church that needs one of these now should keep the product it already uses for it.
Questions
What churches ask first
Do we have to move everything at once?
No. Most churches start with the website and people records, then bring services and livestream across when they are ready. Nothing requires the modules you are not using.
What happens to our data if we leave?
It is yours, and we will not hold a congregation hostage. Be aware that self-service export is not built yet: today a church that wants a copy of its records, or wants them deleted, asks us and we do it by hand. We would rather describe the manual process that works than an automated one that does not exist.
Can volunteers use it without training?
That is the design constraint. A volunteer running the desk on a Sunday should not need to be told what a scene collection is, and a staff member adding a person should not have to think about permissions.
Are our people and pastoral records separated from other churches?
Yes, and it is enforced by the database rather than by application code remembering to filter. Every table carrying church data has a row-level security policy, and the isolation is proven by a test suite in both directions.
Do we need our own streaming hardware?
Only if you already stream. ChurchOS drives OBS on a machine at the church, and nothing else in the product depends on it — a church with no camera uses everything else exactly as normal.
Put your church on one system
No card, and no charge. ChurchOS cannot bill anybody yet, so if it is not right for your church nothing is taken and nothing is deleted.