Managed WordPress hosting
A managed operating model for WordPress. Before access changes hands, we define the server boundary, backups and restore evidence, update approvals, monitoring path, incident decisions, and final handoff in writing.
Responsibility matrix
The proposal names the platform, Tenten and client owners for each boundary. If ownership changes, the matrix changes before access or production work does.
01
Tenten
Recommend an option and document the access needed for the agreed scope.
Your team
Own the commercial account and approve spend unless the proposal says otherwise.
Evidence retained
Account owner, billing contact, access boundary
02
Tenten
Record the runtime, configuration, dependencies and known constraints before change work starts.
Your team
Confirm the production site, business critical periods and people who can approve risk.
Evidence retained
Baseline inventory, scope, approver
03
Tenten
Assess compatibility, record versions and execute an approved change window. Use staging when it exists and is included.
Your team
Provide valid plugin licenses, acceptance criteria and a decision owner for functional risk.
Evidence retained
Change record, checks, rollback condition
04
Tenten
Run the agreed schedule and retain the job and restore evidence included in scope.
Your team
Confirm data criticality, retention needs and the acceptable recovery trade-off.
Evidence retained
Backup result, restore test, timestamp
05
Tenten
Configure the agreed checks, validate alerts and open the documented escalation path.
Your team
Keep business contacts current and decide when impact calls for customer communication or a trade-off.
Evidence retained
Signal, threshold, channel, decision owner
06
Tenten
Make only approved changes inside the agreed control boundary.
Your team
Retain ownership and recovery access for the registrar, DNS, email and connected services.
Evidence retained
System owner, recovery path, approved change
07
Tenten
Protect granted access and follow the data handling boundary written into the engagement.
Your team
Own lawful processing, content accuracy, retention decisions and regulatory approval.
Evidence retained
Data boundary, access list, client approval
08
Tenten
Record the timeline, contain the issue and recommend a forward fix or rollback from the available evidence.
Your team
Approve business trade-offs when recovery time, data loss or customer impact differs between options.
Evidence retained
Incident timeline, decision, recovery checks
Minimum evidence pack
These are minimum record shapes, not a claim that every item is already complete. The estimate states which artifacts Tenten will create, retain and hand over.
01
Required record
Can this site be recovered from a known point?
A successful backup job is not the same as a successful restore test.
02
Required record
Is this change understood, approved and reversible enough to run?
Updates are assessed changes. Custom code and plugins can make unattended updates unsafe.
03
Required record
Who receives the signal, validates impact and makes the next decision?
Monitoring can detect a symptom. It does not guarantee availability or resolve the cause.
04
Required record
Do we contain, fix forward, restore or roll back?
Rollback is conditional. Data changes and third-party failures may need a different recovery path.
05
Required record
Can the next owner operate the site without hidden access or context?
The client keeps recoverable ownership. Secrets stay in an approved credential store, not in the runbook.
Operating decisions
A runbook should make the stop, approve, escalate and handoff points visible. It should not turn every alert into the same answer.
01
If there is no named owner, required access or usable recovery point, resolve that gap before scheduling cutover.
Record: Owner list, access check, baseline and recovery point
02
Record the risk, approver, window, checks and rollback condition. Use an available staging path when it is compatible and included.
Record: Approved change record
03
Validate user impact and recent changes, then escalate through the agreed channel. Do not treat the alert itself as a diagnosis.
Record: Alert evidence and triage note
04
Contain first. Choose a forward fix, restore or rollback against the known-good state, data risk and business impact.
Record: Incident timeline and recovery decision
05
Transfer the inventory, open risks, access boundary and next maintenance window. Rotate or revoke access as agreed.
Record: Signed-off handoff pack
Infrastructure options
These are platform options, not performance promises. The proposal confirms the account owner, region, required services, support path, costs and exit requirements before a provider is selected.
Option 01
Amazon Web Services. Availability and fit are confirmed against the actual account and scope.
Option 02
Google Compute Engine. Availability and fit are confirmed against the actual account and scope.
Option 03
Microsoft Azure. Availability and fit are confirmed against the actual account and scope.
Provider decision inputs
Fit and trade-offs
Scope boundary
Scope the operating contract
We will identify the missing decisions, confirm what Tenten can own, and put the responsibilities, evidence and exclusions into the estimate.
Get a free estimate