Reseller vertical — Churches & Faith Groups
Church accounts and the volunteer who leaves
The person who built the church website has moved away and nobody knows the password, which is how most of these accounts arrive on a reseller's book in the first place.
Straight answer first
A church account is defined by turnover, not by traffic. Whoever looks after the website is a volunteer, and they will hand it on within a couple of years, so the reseller's real product is documentation and continuity rather than server capacity.
Set it up accordingly: its own cPanel account under your WHM, a written record of every mailbox and credential, a disk quota that anticipates a growing sermon archive, daily backups, and a support arrangement that says plainly what a volunteer can ring about.
Written by the Hosting Seller staff · Checked 4 August 2026
24/7
Cover for volunteer questions
1-click
Set-up for a new client site
Free
SSL on the church site
Daily
Backups taken every day
Most people reading a church website have never been through the door. They want a service time they can trust and a sense of whether they would be welcome, which means the site is small, mostly text, and quietly important.
Behind it is a rota of volunteers. One person set the site up years ago, another has the mailbox password, and the current treasurer is not sure who pays for the domain. That confusion is the problem you are solving.
For a reseller this is a modest account with an unusually loyal client. Congregations do not switch supplier casually, and being the firm that finally wrote everything down is a position that holds for years.
Write the handover before the volunteer leaves
Assume the person you are dealing with today will not be the person you deal with next year. So the first deliverable is a single page: which mailboxes exist and who holds each, who owns the domain and when it renews, which plugin runs the giving page, the PHP version, and exactly how somebody requests a restore.
Keep that page current, in a place the church controls rather than only in your inbox. It is a small piece of work that turns a fragile account into a durable one, and it is the reason your name survives three changes of volunteer.
What a sermon archive costs your pool
This is the one place a church account grows. A recording every week, uploaded at whatever size the desk exported it, accumulates steadily and forever. Ten years of audio is a real number, and it is the only line on this account that will ever surprise you.
Decide early where it lives. If the archive is going to sit in the hosting account, set a disk quota in the package and size the tier accordingly — the entry reseller tier's pool is 30 GB of NVMe shared across up to 100 client accounts, which is generous until one client has a decade of sermons in it. If it can live on a service built for audio and be embedded, the account stays small and cheap forever.
Costing an account that must stay affordable
Churches genuinely have small budgets, and it is fair to reflect that. The good news is that the resource cost is negligible: a text site with a few photographs takes almost nothing from the pool, and your own bill is a set fee for the platform plus a charge for the accounts that are live.
So the honest structure is a low monthly figure that covers the account, the mailboxes, the certificate and a defined amount of help — with anything larger quoted separately. Say what is included in writing. Unbounded goodwill on a volunteer-run account is how resellers end up doing unpaid work for years and resenting a client they like.
The support you are actually agreeing to
Expect three kinds of call. The service time on the site is wrong. Nobody can get into the mailbox because the volunteer who set it up has left. And a page has disappeared after somebody was editing on a Sunday afternoon.
Build for all three and price for them. Daily backups make the third a restore from WHM. Your written record makes the second a five-minute answer instead of a reset chain. And the first is a content change you should either include in the monthly or bill for — but decide which, once, and put it in the same document as everything else.
Continuity is the product
Each church gets a cPanel account to itself, with a certificate issued for its domain, daily backups running and limits you set deliberately.
Private nameservers and a branded panel mean the volunteer's point of contact is your firm, and the written record you keep means the next volunteer has one too.
- A written account record kept current
- Disk quotas set with the archive in mind
- Free SSL on the church site, renewed for you
- Daily backups across every client account
Why Hosting Seller
On every plan, as standard
An account that survives turnover
One written page of mailboxes, credentials and procedures means a new volunteer inherits a working relationship, not a mystery.
Archives that do not surprise you
A disk quota set in the package keeps a decade of sermon recordings from quietly consuming the pool you sold.
Costs low enough to be fair
A text site takes almost nothing from your resources, so a small monthly figure can still carry a sensible margin.
Sunday mistakes made reversible
Daily backups across the book mean a page deleted during an afternoon edit comes back from WHM in minutes.
A defined scope, in writing
Saying what the monthly includes protects a client you like from becoming a client you avoid.
Certificates handled quietly
Free SSL is issued and reissued per client site, so no volunteer ever has to understand what a certificate is.
First Steps
From choosing to live
- 1
Write the record on day one
Mailboxes, credentials, domain ownership and renewal, plugin list, restore procedure. Store it somewhere the church controls too.
- 2
Decide where the audio lives
In the account with a quota, or on a service built for audio and embedded. That single decision fixes the cost of the account for a decade.
- 3
Put the scope in writing
What the monthly covers, what is quoted separately, and how a volunteer raises something. One page, agreed before the first invoice.
In the Box
Packed with every plan
- A separate cPanel account for every congregation
- A written record of mailboxes, credentials and renewals
- Disk quota set with a growing archive in mind
- Free SSL on the client site, reissued automatically
- Daily backups, restorable by you from the panel
- Staging copies so an edit can be proved first
- Private nameservers carrying your company name
- Softaculous for a repeatable one-click install
- A defined support scope agreed before the first invoice
- Support answering at any hour, behind you and them
Across the Counter
Things people ask us all the time
How do I stop a church account becoming unpaid work?
Write the scope down before the first invoice: what the monthly covers, what is quoted separately, and how somebody raises a request. Volunteers ask in good faith and will keep asking if nobody has ever said where the line is. A single agreed page protects both sides and keeps a client you like out of the category of clients you dread.
Where should years of sermon recordings actually live?
Decide it once, at the start. Audio in the hosting account is simple but grows forever, so it needs a disk quota and a tier sized for it. Audio on a service built for media, embedded into the pages, keeps the account small and cheap indefinitely. Either is defensible; drifting into the first by accident is not.
What do I do when the volunteer who set everything up has gone?
That is the moment to impose a record. Reset what needs resetting through the account owner, document every mailbox and who now holds it, confirm who owns and pays for the domain, and store the page somewhere the church itself controls. You will be doing this once rather than every two years.
Can I hold a church account at a genuinely low price?
Yes, provided the scope is bounded. The resource cost is close to nothing and your own charge is a flat base rate plus live accounts, so a small monthly can still carry margin. What breaks the economics is not the price but open-ended support, so define the included help and quote anything beyond it.
Read next
Best Hosting for Nonprofit Projects
Buying hosting on a charity budget, with the tests and the verdict written out.
VPS Hosting for Churches & Faith Groups
Root access and a machine of its own for a client who has genuinely outgrown a pool.
Web Hosting
cPanel hosting on NVMe for the client who would rather hold their own account.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Be the firm that wrote it all down.
Reseller tiers with private nameservers, free client SSL, daily backups and support at any hour.
See VPS Hosting for Churches & Faith Groups plans