Church hosting shaped around the weekly service cycle.
A church site does the same thing every week: publishes a sermon, takes giving, and gets most of its traffic on one morning. The hosting should assume all three.
Everything a church site asks of a host.
New media every week, one predictable traffic peak, and donation pages that must never be served from a cache.
Sermons that start playing immediately
Audio and video are served from the edge with byte-range support, so a listener can skip to twenty minutes in without the server sending the first twenty, and without a PHP worker held open for the stream.
An archive that keeps growing
A weekly upload is fifty files a year and it never stops, so storage is sized for accumulation rather than for a launch-day snapshot that looked fine at the time.
Giving handled properly
Donation and gift-aid pages bypass the cache entirely and are never shared between visitors, so nobody is shown a form carrying somebody else's details.
Sunday morning, without a surprise bill
The weekly peak is a known shape rather than an incident, and it is part of what the plan is sized for instead of something billed as an overage afterwards.
Volunteers who cannot break it
Rota, newsletter and event editing sit behind roles that do not include plugin installation, and staging exists for the changes that genuinely need it.
One place for the person who looks after it.
Church sites are usually maintained by a volunteer with several other responsibilities. The dashboard is built for somebody who checks it monthly rather than daily.
- Plain-language update status
- Storage view as the sermon archive grows
- One-click admin login for staff and volunteers
- Restore any daily backup from the dashboard
Sunday morning, everybody at once.
The peak is narrow, predictable and mostly media. Sizing for the weekday average is what makes a church site slow on the one morning it matters.
What we change for a church site
These are the settings that differ from a standard WordPress site on the same plan. Each follows from a weekly publishing cycle with one predictable peak.
| Setting | What we do | Why |
|---|---|---|
| Media delivery | Edge-served with byte-range support, off the PHP workers | A thirty-minute sermon streamed through PHP occupies a worker for the length of the sermon. |
| Storage | Sized for weekly accumulation rather than a fixed allowance | Fifty new recordings a year is a growth curve, and a fixed allowance only moves the problem into year two. |
| Full-page cache | Bypassed on giving, gift-aid and prayer-request URLs | Anything a person types about their finances or their circumstances must not be capable of being served to the next visitor. |
| Peak capacity | Provisioned for the weekly service window | The Sunday peak is a recurring shape rather than an incident, and treating it as an overage penalises the site for working. |
| User roles | Volunteer editing without plugin or theme rights | The person updating the rota should not be one click away from installing something that takes the site down before a service. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Can we stream the service live?
How much sermon audio can we store?
Are donations processed on our site?
Who can we let edit the site?
Do we pay more for Sunday?
Move your church site to a host that knows what Sunday looks like.
Free migration, sermon media from the edge, and giving pages that stay private.