Skip to content

Operations, hosting and maintenance

You should be looking after your business, not after updates and backups. We take on operations — and we are reachable when it matters.

What you get out of it

There is a backup, but nobody has ever restored it

A backup that has never been tested is an assumption. The day you need it is the wrong day for the first test.

The dependencies are two years old

Not updating is a decision you make again every day without noticing — until a vulnerability is published and the jump spans four major versions.

Nobody knows whether it is up

The first person to notice an outage should not be the customer.

How it works

  1. Take over and write it down

    What runs where, with which credentials, in which version. Operations without an inventory is guesswork with an invoice attached.

  2. Back up and test the way back

    Set up the backup, restore it once, note the date. Only then does it count.

  3. Monitor and keep current

    State, load, errors. Updates in small steps, so no jump builds up that nobody dares to take.

What you receive

  • An inventory a third party can read
  • Backups with a dated restore test
  • Monitoring that reports before anyone phones
  • An exit path that is written down, not merely intended