Club hosting built around the fixture list.
A club site is quiet midweek, spikes every matchday, and takes a season of membership renewals in about three weeks. All three of those are on a calendar you publish.
Everything a club site asks of a host.
A predictable weekly peak, a burst of renewals once a season, and a results archive that only ever grows.
Matchday, every week
The peak is on a schedule you already publish, so capacity follows the fixture list rather than reacting to it after supporters have started refreshing the page.
Live scores that are actually live
Score and commentary URLs bypass the page cache while a fixture is in progress and return to normal caching afterwards, so supporters see the goal rather than the page from ten minutes ago.
Renewals that all arrive together
Membership renewal is a write and it happens inside a three-week window each season, so that period gets the capacity rather than having it averaged across a quiet year.
Fixtures, results and tables
League tables and results archives are generated when a result is entered rather than computed on each request, so an archive spanning decades never slows the current season down.
Highlights without the bandwidth bill
Match video is served through the edge with byte-range support, so a clip that gets shared beyond your own supporters does not turn into an overage on the invoice.
One site, run by volunteers, on a Saturday.
Club sites get updated by whoever is free, usually from a phone, usually at the ground. The dashboard has to survive being used that way.
- Matchday uptime and response monitoring
- Renewal window capacity view
- One-click admin login for committee members
- Restore any daily backup from the dashboard
Full time, and everybody refreshes.
The narrow peak comes at the whistle. Everything either side of it is a quiet site, and sizing for the average gets the only moment that matters wrong.
What we change for a club site
These are the settings that differ from a standard WordPress site on the same plan. Each follows from a season with a weekly peak and one concentrated write window.
| Setting | What we do | Why |
|---|---|---|
| Matchday capacity | Provisioned against your published fixture list | The peak sits on a calendar you publish months ahead, so reacting to it rather than planning for it is a choice rather than a limitation. |
| Live score URLs | Cache bypassed while a fixture is in progress, cached again afterwards | A cached score during a match is a wrong score, and after the whistle it becomes the most cacheable page on the site. |
| League tables and archives | Generated on result entry rather than on request | Recomputing a table from decades of results on every page view repeats the same work thousands of times for an answer that changes once a week. |
| Renewal window | Extra write capacity for the three weeks it runs | A season's memberships arrive inside a fortnight, and that fortnight is the only period when a club site is genuinely write-heavy. |
| Match video | Edge-served with byte-range support | A clip that travels beyond the club's own supporters is the one thing capable of turning a small site's bandwidth into a real bill. |
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.
Does matchday traffic cost extra?
Can we post live scores?
What about membership renewals?
Can volunteers update it from a phone?
Will decades of results slow it down?
Move your club site to a host that reads the fixture list.
Free migration, live scores that are live, and a matchday peak nobody has to think about.