← All case studies
Case study
Keeping every ministry site standing up
Across all JTCM-operated sites
Uptime checks, link-rot and dependency scanning, and scheduled backups — so problems reach us before they reach the ministry.
The problem
Small ministries rarely find out their site is down until someone tells them, and a site that quietly breaks can stay broken for weeks. Outbound links rot, dependencies pick up vulnerabilities, and data loss is usually discovered far too late to fix.
What we did
Every site we operate is covered by uptime checks that alert us rather than the ministry, automated link-rot and dependency scanning, and scheduled backups of the data behind the sites that store any.
Result
Problems generally reach us before they reach the ministry, and the ministry is not expected to run any of this themselves.
What changed for the people using it
| Aspect | Before | After | Change |
|---|---|---|---|
| Finding out a site is down | Someone eventually mentions it | An automated check alerts us | We hear first |
| Dead outbound links | Found by accident, if ever | Scanned across every site | Caught early |
| Dependency vulnerabilities | Unmonitored | Audited across every app | Monitored |
| Data loss | Nothing to restore from | Scheduled backups of every database | Recoverable |
| Who runs all this | Nobody | Us, not the ministry | Off their plate |