Church OS
AI multi-tenant church operating system
A multi-tenant operating system for churches — each congregation an isolated tenant over a shared, hardened platform. AI turns sermon notes into presentation slides, drafts announcements and summaries, and surfaces scripture references. Her own venture.
- Django · django-tenants
- DRF
- Next.js
- PostgreSQL
- LLM
- Docker
Context
Church OS is an operating system for churches — a single platform where each congregation runs its own members, announcements, and sermon workflows as an isolated tenant. It's my own venture. (In development — this page describes what I'm building toward.)
The problem
Churches run on a patchwork of spreadsheets, chat groups, and ad-hoc docs, and any platform serving many congregations has to keep each one's data strictly separate. On top of that, admin work — turning sermon notes into slides, drafting announcements, writing summaries — eats time that could go to the congregation.
Approach
The design I'm building toward: multi-tenancy via django-tenants with a schema-per-tenant model, so each congregation's data lives in its own isolated schema on a shared platform. DRF for the API, Next.js for the front end, Docker to package it. A planned AI layer turns sermon notes into slides, drafts announcements and summaries, and surfaces scripture references.
Securing it
Tenant isolation is the whole game here, and schema-per-tenant is the foundation I'm building on: one congregation shouldn't be able to read another's data because they aren't even in the same schema. The plan is to enforce tenant context on every request and background job, add per-congregation roles, and scope the AI features to a single tenant's data.
What shipped
In development — currently repo scaffolding.
Links