SteboCare
Your website, maintained for you
Choose a defined maintenance scope for your website or WordPress application. Confirm the current plan inclusions, access requirements and recovery responsibilities before work begins.
- Define scope
- Agree access
- Test recovery
- Confirm ownership
Care plans
Compare current care plans
From basic maintenance to a fully managed web presence. Pick the level of involvement that suits your business.
Scope boundaries
What is included — and what is not
Clear boundaries mean no surprises. Here is exactly where care ends and a project begins.
Content changes vs redesign
Confirm which text, image and page changes are included in the selected plan. Treat a redesign, new feature or application integration as a separate scope unless explicitly included.
Plugin licensing
List premium plugins and themes, licence ownership and renewal responsibility. Confirm any included licensing rather than assuming maintenance pays for every component.
Pre-update recovery point
Agree which files, data and configuration must be captured before a change, who verifies the copy and what approval is needed to restore it.
Rollback
Define rollback conditions and acceptance checks before changing a live application. Recovery may require data reconciliation and cannot be guaranteed from a plan name.
Remediation escalation
Ask how out-of-scope incidents are handled, which response window applies and when a separate quotation or authorization is required.
Scope transparency
Use the current catalogue feature list and a written agreement. Confirm responsibilities for any task that is not explicitly listed before ordering.
Why managed care
Maintenance you do not have to remember
Running a website is not a one-time task. Care plans turn it into a process — handled by people who do this every day.
Define an update cadence
Agree which components are covered, how changes are approved and which checks determine that an update is acceptable.
Test a recovery path
Confirm retention, access and restore responsibilities. A successful backup job is not evidence of a completed recovery test.
Choose alert ownership
Specify which checks are monitored, who receives an alert and how an unresolved incident is escalated under the chosen service.
Specify useful reporting
Confirm the reporting scope and frequency, including completed changes, failed checks, exceptions and recommended follow-up work.
Plan for a failed change
Define the recovery point, rollback authority and handling of data changed after a release. Do not assume every change can be instantly reversed.
Keep responsibilities clear
Record the service owner, authorized contacts, access handover and tasks retained by your own application or business team.
SteboCare FAQ
Care plan questions, answered
Scope, updates, rollback and what happens when something breaks.
Not sure which care plan fits?
Tell us about your site and we will recommend the right level of care — no obligation.