The marketing site is not your problem until somebody leaves the company and you discover their WordPress login was never connected to anything you control.
Your objection to WordPress is rarely technical. It is that it sits outside every process you already run.
Every site authenticates through your provider, so accounts are created and removed where you already manage them rather than in a plugin nobody audits.
A leaver's access disappears when their directory account is disabled. Local WordPress accounts survive offboarding indefinitely, which is how former staff keep publishing rights for years.
Who changed what and when, retained and exportable. Answering that from a WordPress install after the fact is usually not possible at all.
A dozen departmental sites on a dozen credit cards is a procurement problem before it is a technical one. It consolidates to one account and one renewal.
Updates are applied at the platform on a stated cadence, so WordPress stops being the exception in your vulnerability reporting.
Somebody in marketing bought hosting four years ago. It is now business-critical, on a personal card, with a login belonging to a contractor nobody can reach.
The measurement here is not milliseconds. It is whether the platform answers the questions your own audit already asks of everything else.
Almost none of this is performance. It is making WordPress answerable to the controls you already operate.
| Setting | What we do | Why |
|---|---|---|
| Authentication | Delegated to your identity provider for every site | Local WordPress accounts exist outside every control you run, so the one system nobody can audit becomes the one holding publishing rights. |
| Offboarding | Access revoked when the directory account is disabled | A local account survives an employee leaving indefinitely, which is how former staff and past contractors keep write access for years. |
| Change history | Retained and exportable rather than session-scoped | An audit asks who changed what and when, and a stock install cannot answer that once the person has gone. |
| Billing | Consolidated to one account and one renewal | Departmental sites bought individually on personal cards are a procurement and continuity problem well before they are a hosting one. |
| Patch cadence | Applied at the platform on a stated schedule | Vulnerability reporting needs a policy it can cite, not an assurance that somebody in marketing usually clicks update. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Move the estate across — migration is free, consolidation included.