Built and operated by
the engineers who wrote it.

Why we built it

We went through church management software the way a church council would: a spreadsheet of vendors, features, and prices. Three problems showed up on every row.

The pricing punished you. The base subscription covered a member database and not much else. Online giving cost extra. Accounting cost extra. Text messaging cost extra. Check-in cost extra. By the time the quote covered what a church office actually does in a normal week, the annual number looked like a staffing decision.

The features weren't there. Things a church needs every single week, guest followup that actually happens, fund accounting a treasurer can close the month in, volunteer scheduling with text confirmations, statements that generate themselves, were missing, half-built, or sold as separate products.

The platforms felt old. Desktop-era screens, clumsy on a phone, and confusing enough that volunteers needed training sessions for tasks that should be obvious. The pages parishioners touch directly, giving, profiles, sign-ups, embarrassed the churches that had bought them.

What we wanted didn't exist: a platform simple and easy enough that staff and volunteers just get it, yet complete enough to fully run the church, every member, every gift, every event, every followup, without bolting on other tools. So we wrote it.

Every screen was built the way the rest of our platforms are: in front of the people who had to use it. Office staff told us where data entry was slow and the screens were reworked. Clergy told us what they needed to see before a hospital visit and what should stay confidential, and the pastoral care module took its shape from those conversations. Parishioners told us, sometimes bluntly, which pages were confusing. Every one of those became a fix.

How it's engineered

We made one decision early that shapes everything else: SanctuaryIQ uses no third-party libraries or frameworks. Every line of the platform, from the data layer to the interface, was written in-house.

That choice costs more engineering time, and it buys three things churches should care about:

• Security. Most modern software inherits hundreds of dependencies its vendor has never read. We inherit none. There is no supply chain to attack and no framework vulnerability announcements to race against. Queries are parameterized, credentials are encrypted at rest, every endpoint is role-gated, and every change is audit-logged.
• Accountability. When something needs fixing or explaining, the person responsible for the code is the person you email. There is no "we're waiting on an upstream patch."
• Speed. With no framework overhead, the platform stays fast on an office desktop and on a volunteer's phone in the parish hall.

What we charge for

One price per church, with every module included: membership, giving, pledges, fund accounting, attendance, check-in, communications, volunteers, events, and reporting. No per-seat pricing and no per-module fees. A church shouldn't have to buy its own operations back one module at a time.

Who you'll deal with

We support what we ship. If you email us about SanctuaryIQ, the reply comes from the engineers that built the product, not a sales team. When you evaluate the platform, the demo is given by the engineer who wrote it. When you have a support question, it is answered by someone who can read the code. Churches told us for years that they missed talking to people who actually understand their systems. That is the standard here.