A Position on Artificial Intelligence in Church Ministry
FaithKit is free, open-source church management software. It was built with the assistance of artificial intelligence tools — and we believe churches deserve to know that, and to understand exactly what it means.
This statement exists because transparency is not optional. When a church entrusts its member directory, its prayer requests, and its giving records to a piece of software, the people who built that software owe a clear accounting of how it was made and what principles govern its operation.
We are not writing this statement because AI is controversial. We are writing it because honesty requires it, and because Scripture provides a clear framework for the relationship between tools and the people who use them.
Artificial intelligence assisted in building FaithKit. AI tools were used during development for code generation, design iteration, documentation, and testing. This is disclosed here, in the source code, and in the onboarding process. There is nothing hidden.
AI is a tool. It is a tool the way a printing press is a tool, the way a sound system is a tool, the way a church bus is a tool. Each of these extends the reach of human effort. None of them replaces the human being doing the work. A printing press does not write the sermon. A sound system does not preach it. A church bus does not shepherd the family it carries.
FaithKit was built by a developer who used AI the way a carpenter uses a power drill — to work faster, more precisely, and with fewer errors. The judgment, the architecture, the decisions about what to build and what not to build, and the accountability for every line of code belong to the craftsman, not the tool.
AI serves the ministry. It does not define the ministry.
The following principles govern every technology decision in FaithKit. They are not aspirational. They are operational. If a proposed feature, integration, or design choice cannot satisfy all five, it does not ship.
Technology decisions are subject to scriptural authority. The question is never "Can we build this?" but "Should we build this?" — and the answer is found in the same place it has always been found.
If we cannot articulate a biblical basis for a technology choice, we do not implement it. This is not a piety exercise. It is a design constraint. It keeps the software honest and the builders accountable.
AI assists the developer the way a power drill assists the carpenter. The drill does not design the house. It does not choose the wood. It does not decide where the load-bearing walls go. The craftsman does all of that. The drill makes the holes.
Every line of FaithKit's code was reviewed, tested, and approved by a human developer. The craftsman's judgment, skill, and accountability remain with the human being — always.
Pastoral care, prayer, counseling, preaching, and the work of the Holy Spirit cannot be delegated to algorithms. The command was "Feed my sheep" — not "Automate my sheep." The shepherd knows his flock by name. Software does not.
FaithKit will never generate sermons. It will never automate prayer responses. It will never produce counseling content. It will never simulate or replace the shepherd's relationship with his flock. These boundaries are permanent.
Every AI-assisted component of FaithKit is documented. The development process is disclosed. The source code is open. Any church, any pastor, any member of any congregation can audit every line of code that touches their data.
We do not hide what AI built. We do not obscure how AI was used. We do not claim human authorship for machine-generated output without disclosure. Honesty in the sight of men is not a feature — it is a requirement.
FaithKit never sends church data to external AI services. No member information, no prayer requests, no giving records, no attendance data, no contact details leave the church's own infrastructure. The data lives on the church's server and stays there.
Faithful stewardship means the church controls its own information. It means no third-party AI model is trained on your congregation's prayer requests. It means no vendor holds your member directory hostage. Your data is yours — completely, permanently, non-negotiably.
For clarity, here is a plain accounting of how AI relates to FaithKit — both in its development and in its operation.
You are the shepherd. You know your people by name. You sat in the hospital room. You made the phone call at midnight. You opened the Word on Sunday morning and preached what the Lord laid on your heart. No software did that. No software will.
FaithKit is a filing cabinet, not a co-pastor. It organizes what you already do well — member records, prayer lists, giving statements, sermon archives, event schedules. That is all it does. Use it when it serves the flock. Put it down when it does not.
If the software ever gets between you and the work God called you to do, close the laptop. The church existed for two thousand years without a database. It will outlast every technology we build.