Church Commons-first
Secure shared platform · tenant-specific delivery
One trusted system.
A growing suite of ministry tools.
Replace separate subscriptions for directories, forms, email, events, websites, formation, records and reporting with one connected Church Commons platform—without surrendering privacy.
Architecture rule 01Protect information by design.
Every record is tenant-separated, role-controlled and auditable. Information is entered once and exposed only to the people and sites authorized to use it.
Application portfolio
Core app map
Select a module to see what it owns and when it is ready.
System shape
Build in layers, not silos
Every new app reuses the layers beneath it.
Identity, tenants, roles, audit, files, notifications, search.
Organizations, people, roles, relationships, consent, history.
Forms, communications, sites, events, formation, governance, finance.
MVP portal, WordPress plugins, calendars, email, domains, payments, APIs.
Continuity
Project memory is part of the product.
Navigation, messaging, image plan, forms direction, and staging boundary remain intact for the later connector phase.
Reusable schemas, workflows, permissions, and integrations are developed here first.
Licensed modules, actual use, unique data, reports, and risk must be verified before cancellation.
Non-negotiables
No live MVP cutover yet.GoDaddy and the current public site remain untouched.
No security shortcuts.Tenant isolation, least privilege, field-level privacy and audit history precede real data.
No duplicate systems of record.MVP and church websites consume Church Commons data through controlled connectors.