Core: health checks
Core runs automatic health checks for security and performance every 24 hours. Among other things, we check outdated PHP and CMS versions, SSH firewall rules, database encryption, InnoDB settings and WordPress indexes. For each finding you see why it matters, and after a change you can run the checks again straight away.
Monitoring comes standard. Health checks are the step after
Every managed hoster runs monitoring: it tells you when something falls over. Health checks judge the configuration of the server and of the applications on it, which is a step that is rarely taken. A platform has to understand how WordPress, WooCommerce and Laravel are put together to do it.
| Monitoring Is it still running? Comes with managed hosting. | Health checksUnique to Core Is it configured properly? Comes with truly managed hosting. | |
|---|---|---|
| Server is online |  |
|
| Enough disk space available (more than 20%) | |
|
| Enough CPU available (below 80%) | |
|
| Server security | ||
| Database encryption enabled | |
|
| SSH access limited to IP addresses | |
|
| Automatic security updates | |
|
| Application security | ||
| PHP version still receives security updates | |
|
| CMS version up to date | |
|
| Performance | ||
| InnoDB buffer pool large enough | |
|
| Database optimisation enabled | |
|
| QUIC enabled | |
|
| Database indexes for better performance | |
|
| WooCommerce HPOS enabled | |
|
Strict mode for SaaS
With strict mode, Core raises the bar: measures that are a recommendation for a brochure site become a finding. Ideal for applications that store personal data.
Think of database encryption at rest, automatic OS upgrades, and SSH reachable only from known networks.
