Pick how you want to run churchit. Most churches self-host with Docker: one command on any spare Linux box, VPS, or mini-PC.
Recommendedπ³ Self-host with Docker
One command. That's the whole install.
Run this in a terminal on the machine that will host churchit (Linux, Windows via WSL, or macOS with Docker Desktop). It installs Docker if it's missing, asks for your domain, generates strong passwords, and starts everything.
β οΈAlpha software. churchit is still in active development and is not yet ready for official/production use. Please install it for testing and evaluation only.
Windows and macOS steps, a real domain with HTTPS, DNS and port forwarding, password resets, and uninstalling are all in the self-hosting guide β
πΊοΈ Three ways to run churchit
Pick the path that fits your church
It's the same churchit on every path. The only thing that changes is who looks after the server.
Frappe Cloud
Best for
Anyone who does not want to run a server
Cost
A few dollars/month
Effort
Click Install
Create a free account at Frappe Cloud and verify your email address.
Click New Site. Choose the Version 16 release group, a region, and a plan. The cheapest plan is fine for a typical church. Enter a site name (for example mychurch) and click Create Site.
The script installs Docker if it is missing, asks for your domain (press Enter to try it out locally at http://churchit.localhost), generates passwords, and starts everything. When it finishes it prints your site address and the Administrator password.
To update:
cd ~/churchit && docker compose pull && docker compose up -d
For Windows/macOS steps, password resets, and uninstalling, see the self-hosting guide. To make the site reachable from the internet with your own domain, see Setting up a public domain.
Existing Frappe bench (Pilot)
Best for
Admins who already run Frappe, or want other Frappe apps alongside Churchit
Cost
Free
Effort
A few commands
Pilot is Frappe's official tool for running benches on your own Linux server. Use it if you already have a Pilot bench, or want Churchit next to other Frappe apps. Follow Pilot's README to install it and create a bench, then:
# Replace "church" with your bench name and church.example.org with your domain.
pilot -b church get-app https://github.com/meichthys/churchit --install-dependencies
pilot -b church new-site church.example.org --apps churchit
pilot -b church setup production
To update:pilot -b church update.
On a plain bench (without Pilot), the equivalent is bench get-app https://github.com/meichthys/churchit, bench --site <your-site> install-app churchit, and bench update to upgrade.
Churchit cannot share a site with an app that ships a doctype, report or other standard record of the same name. Today this includes Frappe Learning (Function) and Frappe Suite (Email Address, Slide). Installing Churchit on such a site, or installing such an app on a Churchit site, stops with an error that names the shared records.
Churchit and ERPNext on one site
Churchit and ERPNext can share a site. Install them in either order:
pilot -b church get-app https://github.com/frappe/erpnext --branch version-16
pilot -b church install-app church.example.org erpnext
Update and migrate an existing Churchit site before you install ERPNext. Until you do, the install stops with an error.
When both apps are on one site:
Area
What happens
Setup wizard
After you add ERPNext to a Churchit site, desk users go to ERPNext's setup wizard until a System Manager completes it.
Website
Churchit owns the public website: home page, menu, theme, favicon and login logo. Installing Churchit on an ERPNext site replaces the website menu and footer and turns off sign-up.
Letterhead
The church's default letterhead, such as Church Letter Head, stays the default, so ERPNext documents also print with it. To print them with an ERPNext letterhead, set it in Company > Default Letter Head.
Email
Churchit turns off the standard email footer, so church emails do not end with "Sent via ERPNext". You can turn it on again in System Settings.
Address Template
ERPNext's setup wizard replaces the default Address Template for your country, and its template has no phone and email lines. Giving statements print the church address with that template, so check Address Template after the wizard.
Addresses
The Address form shows the fields ERPNext needs, such as Preferred Billing Address, Is Your Company Address and Tax Category. A site without ERPNext keeps the short form. Every Address link, on church and ERPNext forms, shows the first line of the address. To find an address, type part of the street, the city or the name it was saved under. The search no longer finds an address by its country or state. Only church addresses go to OpenStreetMap for the map. Addresses linked to customers, suppliers or companies stay on the site.
Portal
The customer and supplier lists (/orders, /invoices, /addresses and others) work beside the Member Portal at /portal. ERPNext's customer and supplier logins are not added to People as Visitors. A login is still linked to the person whose primary email is the same address.
Notifications
Communication consent does not apply to ERPNext notifications. ERPNext messages, such as invoices, go to all their recipients, church members included.
Gender
Churchit keeps only Male, Female and Unknown. Installing Churchit on an ERPNext site deletes the other genders, so update the employees and contacts that used one.
Apps screen
Every desk user sees an ERPNext tile. Users without ERPNext roles cannot use it. Desk users who can open Summary go to Summary after login. Other desk users go to their own default.
Churchit renamed three records so that ERPNext can use their names: Budget is now Church Budget, Location is now Church Location, and the Open Work Orders report is now Open Church Work Orders. Migrate moves the records, the links to them, your customizations and each user's list settings. Update anything else that uses the old names, such as Client Scripts, Server Scripts, saved reports, dashboard charts, bookmarks (/app/budget) and API calls (/api/resource/Location).
MCP after an update: Churchit closes Frappe's MCP server (System Settings > AI Agents > Enable MCP, which a Frappe 16 update turned on in October 2026) until a church turns on AI. MCP is one setting for the site, so ERPNext and the other apps on the site lose MCP too. To open it again, turn on AI in Settings > Module Settings > AI Settings, then tick Enable MCP in System Settings. Only a Church Manager, a System Manager or a person with the new Church AI User role can then connect an AI app; give that role on the User record to the other people who need it. Each System Manager gets one bell notice that says so.
Whichever path you took, do these before inviting anyone else in.
Change the Administrator password if you have not already (top-right avatar β My Settings). Keep this account for site administration only. Do not use it day to day.
Create your own user: type New User in the search bar. Under Roles & Permissions, give the user the Church Manager Role Profile and the Church Module Profile. This user can manage all aspects of the church.
For other staff and volunteers, create users with the Role Profile that matches their job, and the Church Module Profile:
Role Profile
For
Can change
Church Staff
Staff who look things up
Their own prayer requests, sign-ups, care requests and room bookings. Reads people, events, groups and ministries.
Church Office
Office administrators
People, families, groups and member transfers
Church Care Team
Pastors, deacons, care team
Care, counseling, visitation, background checks, prayer and alms requests
Church Treasurer
Treasurer, bookkeeper
Collections, expenses, funds, budgets and giving statements
Church Check-In Volunteer
Check-in desk
The Check-In Station only
Combine profiles when one person has several jobs. Open the Role Permissions Manager to see exactly what each role can do.
Members do not need a desk login. Use Invite to Portal on their Person. It gives them the Church User role, which reaches the portal and their own records only.
π Your own web address
Set up a public domain
Do this once so people can reach your site at an address like www.yourchurch.org.
A domain lets people open your site at an address like www.mychurch.org. The goal is the same on every deployment path:
Get a domain name. Register one with a domain registrar, or use a subdomain you already own (for example churchit.mychurch.org).
Point the domain at your site. Follow the part below that matches how you run Churchit.
Check HTTPS. Open https:// plus your domain from a phone that is not on your home or office Wi-Fi. The page should load with a padlock.
Frappe Cloud. At your domain provider, add a DNS record. For a subdomain, add a CNAME record pointing to your Frappe Cloud site name (for example mychurch.frappe.cloud). For a bare domain like mychurch.org, add a single A record pointing to the Inbound IP shown on your Frappe site's page. Then open your site's Domains tab, click Add Domain, enter the domain, click Verify DNS, and click Add Domain again. Frappe Cloud sets up the HTTPS certificate for you. See Frappe's custom domain guide for details.
Self-hosted (Docker or Pilot). Your server has to be reachable from the internet, and the exact setup depends on your network.
Tunnel (recommended). A service such as Cloudflare Tunnel or Tailscale Funnel connects out from your server, so you open no ports and change nothing on your router. It also works if your internet provider does not give you a public IP (CGNAT). The tunnel handles DNS and HTTPS. Install the tunnel on the server and point it at Churchit's local address.
Reverse proxy or port forwarding. With port forwarding, add an A record to your domain pointing to your public IP address, and forward TCP ports 80 and 443 from your router to the server. If your public IP changes, use a dynamic DNS service to keep the record current. If you already run a reverse proxy such as Nginx, Caddy, or Traefik, point your domain at the proxy and have the proxy forward traffic to Churchit. Pass the original Host header through, so Frappe can tell which site the request is for. Learn more about port forwarding.
For Docker with port forwarding, enter your domain when the setup script asks, and Churchit gets a free HTTPS certificate automatically once DNS and ports are right. The self-hosting guide has the full steps. For Pilot, create the site with your domain as its name, as in the example above, and see Pilot's README for HTTPS.
Putting a site on the internet has security risks. Use a strong Administrator password, keep the server up to date, and take regular backups.
π§ͺ Want to look around first?
Try the demo before you install
Poke around a fully loaded church. No sign-up, no sales call, no personal information.