Knowledge base
Who did what, when, and from where — including what we did on your account.
Activity. Every privileged action on your organisation, kept in order.
Sign-ins, site creation and deletion, DNS changes, plan and payment changes, team changes, API key use, and support access. Each entry has the actor, the time, the object and — where it applies — what the value was before and after.
If a support engineer accesses your account, that appears in your log like any other action, with their name on it. It is not a separate system we can edit; it is the same log you are reading.
Three questions, all of which come up:
key you can revoke.
Filter to what you need and export. Auditors generally want a date range and the actions on one object, which is exactly what the filters produce.
Content changes inside an application — a WordPress post edited in WordPress is WordPress's business, and its own revision history is where that lives.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →