# Maintenance and managed support

> Maintenance aims to reduce how often failures happen, rather than fix them once they've occurred. It means regular follow-up on the shop: updates applied methodically, checked backups, and monitoring outside one-off jobs.

- Source canonique : [https://allaux.fr/en/services/maintenance](https://allaux.fr/en/services/maintenance)
- Langue : EN
- Dernière mise à jour : 2026-08-03

## What a maintenance plan includes

- **Updates applied methodically** — Platform, theme and modules updated on a test environment before production, to limit the risk of regressions.
- **Backup checks** — Confirming backups exist, are recent and restorable, not just generated automatically with no check.
- **Monitoring proper operation** — Periodic checks on critical journeys: ordering, payment, transactional emails.
- **Small routine fixes** — Minor adjustments that don't need a separate quote every time.
- **Monitoring external dependencies** — Checking that third-party services connected to the site keep working correctly after their own changes.

## How a follow-up plan runs

1. **Initial assessment** — Inventory of what's in place: versions, modules, hosting, before defining what the follow-up will cover.
2. **Regular check-ins** — Checks at a frequency agreed with you, matched to the shop's criticality and activity.
3. **Report** — A written summary of what was done, what was found, and what needs more substantial work.
4. **Switching to troubleshooting if needed** — If a problem goes beyond routine maintenance, it's handled as a separate job, with its own quote.

## What maintenance doesn't guarantee

> Maintenance reduces the risk of an incident, it doesn't eliminate it. I don't quote an uptime percentage on this site: a commitment like that requires a written contract with precise terms, not a generic promise. An incident remains possible even with regular follow-up in place.

## FAQ

### What's the difference with managed hosting?

Hosting concerns the server, maintenance concerns the application: its updates, its modules, how well it runs. The two are often combined, but remain two separate services.

### Is there a contractual response time commitment?

Not stated on this site without a contract. A precise response time is defined case by case within a written agreement, not as a general promise.

### What happens if a problem goes beyond the scope of the plan?

It's handled as a full troubleshooting job, with its own quote. Maintenance doesn't cover development or a redesign.

### Can the plan be stopped at any time?

Duration and termination terms are set out in the initial agreement. I don't lock a client into a commitment they don't understand from the start.

### Does the plan cover several sites?

Yes, that's possible if you manage several shops. Scope and frequency adjust to the number of sites involved.

### What happens if I have no plan in place and an update breaks the site?

It's handled as standard troubleshooting, billed separately. That's exactly the kind of situation regular maintenance aims to prevent, by testing updates before applying them in production.