01
Patching and dependency updates
Applied on staging first, regression-checked, then promoted. Updating a live site directly and hoping is how a Tuesday afternoon becomes an outage.
Managed operations
Someone whose job it is
Hosting, updates, backups, monitoring and performance, run to a service level agreement instead of whenever someone notices.
In short
Web management is the ongoing operation of a live website: security patching, CMS and dependency updates, backups with tested restores, uptime monitoring, performance work and content changes. Rynexor runs it to a defined service level with staged deployments: changes are applied to a staging environment and promoted to production only once checks pass.
What this covers
4 areas
02
Backups and tested restores
Daily automated backups held off the server, plus restore drills. An untested backup is not a backup, and you find out which at the worst possible moment.
03
Monitoring and incident response
Uptime, certificate expiry, error rates and Core Web Vitals watched continuously, with alerting that reaches a named person on call.
04
Content and small changes
A monthly allocation for the ordinary requests (a new page, a price change, a form field) so they do not queue behind a project.
How it runs
-
Stage 01
Takeover audit
What is running, on which versions, with which credentials and which forgotten access. Inherited sites almost always carry accounts nobody remembers issuing.
-
Stage 02
Stabilise
Backups working and restore-tested, monitoring live, TLS and DNS correct, obvious security debt cleared, before anything else.
-
Stage 03
Staging and release
A staging environment that matches production, and a release path that is one documented action.
-
Stage 04
Run to service level
Critical incidents inside 1 hour, high severity within 4 working hours, standard requests within 1 working day. Written into the agreement, not implied.
-
Stage 05
Report
Monthly: what was patched, what broke, what the performance numbers did, and what we recommend next, including the months where the answer is "nothing happened".
What you get
- Documented inventory of hosting, domains, certificates and access
- Daily off-server backups with a tested restore procedure
- Staging environment and a one-action release path
- Monitoring with alerting to a named person
- Monthly report covering patches, incidents and Core Web Vitals
Questions we get asked
Do you have to have built the site?
No. Most of this work is taking over sites somebody else built. The takeover audit exists precisely for that: we establish what is actually running before agreeing to be responsible for it.
What counts as a critical incident?
The site is down, checkout is failing, data is exposed, or there is an active compromise. Those carry the 1 hour response commitment. A broken layout on one page is not critical. Treating everything as urgent is how genuine emergencies get missed.
Does this include hosting?
It can, or we manage what you already have. We will say when your current hosting is the actual problem, but moving a site to solve something that is not a hosting issue only relocates it.
What happens if we leave?
You take everything: infrastructure access, documentation, backups and the release process. Nothing is held back to make leaving difficult.
Scope it properly.
Tell us what you need covered. We will reply with what the work actually requires, including when you do not need us yet.
Start a brief