There is no separate security product to remember to buy, because a site we are responsible for never ships without protection. The security layer is our own plugin: fourteen hardening controls, login lockout, security headers and a daily vulnerability scan delivering its own updates over a cryptographically signed channel.
| Hardening | Applied at setup and maintained |
|---|---|
| Patching | In a maintenance window, not at random |
| Scanning | A daily vulnerability scan that fails honestly: if it cannot check, it says so instead of showing green |
| SSL | Configured and kept renewed |
| Backups | Nightly, written to storage separate from the server |
| Recovery | A bad update is a restore, not a rebuild |
| Included from | All plans |
A backup stored on the same server it protects is not a backup Backups Kept Elsewhere If the machine goes, the copy goes with it. Yours are written nightly to separate storage, so a bad update, a broken plugin or a compromised site is a restore measured in minutes rather than a rebuild measured in days. Infrastructure → . Across our entire infrastructure - the engines that publish, route, and monitor for you -backups run nightly and are encrypted before leaving the machine.
Everything you entrust us to manage, taken nightly, encrypted before it leaves the machine, and written to storage separate from the server it protects.
| What | What that covers |
|---|---|
| Your website | The files, the database, the media library, and the theme and plugin configuration, so a restore brings back the site as it was, not a blank install |
| Your content | Pages, posts and articles, and the images made for them, including what we publish for you on a schedule |
| Your asset library | Logos, brand images, graphics, templates, collateral, forms and brand standards held in asset management |
| Your domain records | The DNS record set we manage for you, so a cutover or a recovery starts from a known copy rather than from memory |
| Our engines | The systems that publish, route, answer and monitor for you, so the work carries on after a restore |
Not on this list: your office computers, phones and terminals. They are not on our systems, so they are not in these backups. If you want them covered, tell us and we will scope it.
Monitoring alerts us, and in most cases we are working on it before anyone tells us. If a bad update caused it, the nightly backup means a rollback rather than a debugging session.
Nightly, with a rolling window. If you need a longer retention period for a compliance reason, tell us and we will scope it.
No, and nobody honestly can. What we control is how hard it is to get in, how fast we notice, and what state the recovery starts from.
No. These backups cover what runs on our systems: your site, your content, your asset library, your domain records and the engines that work for you. Office computers, phones and terminals are yours. If you want them covered, tell us and we will scope it.
Most people have never tried. We will tell you what yours would look like.