WordPress hosting that clears vendor onboarding.
The technology is rarely what holds a hosting purchase up. It is the data protection agreement, the subprocessor list, the residency commitment and whether anyone can raise an invoice against a purchase order.
The questions on the vendor form, answered.
These are the items that stall a purchase in review, and the configuration behind each one rather than a reassurance about it.
Data stays where you committed it would
Site data is pinned to a chosen region, and that pinning is a configuration rather than a preference — so the answer on the form matches where the bytes actually are.
A subprocessor list you can attach
Every third party that touches data is named, with what it does and where it operates, so the review has a document rather than a conversation.
Retention set as a number
Backup and log retention are explicit periods you choose, which is what a records policy needs — not 'regular backups' with no stated horizon.
An SLA with remedies in it
Availability commitments in writing, with what happens when they are missed, rather than a marketing uptime figure that carries no obligation.
Billing that fits your process
Purchase orders, annual invoicing and named billing contacts, so the finance step does not become the longest part of the purchase.
What the review actually needs.
A hosting decision usually clears technically long before it clears commercially. These are the artefacts that close that gap.
- Data processing agreement ready to sign
- Subprocessor list with locations
- Retention periods stated, not implied
- Invoicing against a purchase order
Time to onboard, not time to first byte.
For this buyer the relevant number is how long the vendor takes to clear review, because that is the part that delays the project.
What we configure for a procurement review
These differ from a standard account on the same plan, and each is here because a review asked for it in writing rather than because it improves performance.
| Setting | What we do | Why |
|---|---|---|
| Data residency | Site and backup storage pinned to a named region at provisioning | A residency answer given on a form and never enforced in configuration is one deployment away from being untrue, and the discrepancy surfaces during an audit rather than during the purchase. |
| Retention periods | Backup and log retention set to your stated policy rather than a default | Records policies are expressed as specific durations, so a host that offers 'regular backups' without a horizon cannot be mapped onto the policy the buyer is obliged to follow. |
| Subprocessor disclosure | Maintained list with role and operating location, provided as a document | The review has to assess every party that touches the data, and a list that only exists as an answer in an email cannot be attached to the file the decision is recorded in. |
| Access model | Named accounts with roles, no shared credentials issued to the vendor relationship | Shared logins make it impossible to attribute an action to a person, which is the single thing an access review is trying to establish. |
| Billing arrangement | Annual invoicing against a purchase order with named contacts | Card-only billing fails the moment the purchase exceeds a threshold that requires a raised order, and the project then waits on finance rather than on anything technical. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Do you provide a data processing agreement?
Can we guarantee data stays in a specific region?
Can you invoice against a purchase order?
Do you publish a list of subprocessors?
Is your SLA contractual?
Hosting that gets through your vendor review.
A DPA ready to sign, residency you can point at, and invoicing that fits the process.