Service
Maintenance and upkeep
So that what runs keeps running — and you hear about it before anyone else does.
What is included
- Updates. Applied, looked over and, in case of doubt, taken back — not merely triggered.
- Backups. With the question that makes the difference: has anything ever been restored from them? A backup never tried is a guess.
- Monitoring. Reachability, certificates, name resolution, email deliverability. The things that expire silently and are then missing on a Monday.
- Recurring audit runs. The same procedures as in a commissioned audit, only regularly — with the comparison against the last state: what was fixed, what is new, what remains open unchanged.
What gets reported
Not everything. A notice that arrives every week and never means anything stops being read after the third time — and then the one that counts stops being read as well. What gets reported is what is new or has grown worse. What is unchanged and open stands in the report, not in your inbox.
What does not happen
We change nothing in the content without being asked, and we build no dependency that makes switching harder. Credentials stay in your name; when the maintenance ends, our access ends — and you keep everything needed to keep it running.
What you get
- One named contact instead of a ticket system.
- A recurring report that includes the comparison against the last state.
- An overview of which system sits with whom and which credentials exist — the point where things most often come unstuck when it matters.
How it starts
With an inventory: what runs, on what, in whose accounts. From that it follows what maintenance even has to cover — for some it is less than they thought.
Scope, process and price are stated in the quote — once it is clear what the job is. All amounts net, plus VAT.
Before it is missing on a Monday
Tell us what runs and who has been looking after it so far. If the answer is “nobody, really”, that is the most common case — and no reason to be embarrassed.