ahimismito

Managing the server your system runs on

Once the operation depends on a system, the server stops being a technical detail. The question is not what it costs per month: it is who answers on a Monday at 8 a.m.

Schedule a call
Who it is forCustom and admin systems in production
How it worksCan be contracted separately from development

What's included

Backups someone has tested

A backup that has never been restored is not a backup. They get tested, and how long it takes to be back online after an outage gets written down.

Monitoring that speaks up

Disk space, memory, dead services, expiring certificates. The point is to find out before the customer does, not from the customer.

Access and updates kept current

Who gets in, with what permissions and from where. Plus security patches, which is the part everyone postpones until they cannot any more.

A named person responsible

When something goes down, there is someone to message. That is the service: it is not the server, it is that someone is watching it.

This is for you if

Frequent questions

Do you have to have built the system?

No. We can take over administration of a system another team built. What we do first is survey how it is set up, because taking responsibility blind helps nobody.

Do you provide the server?

It can be yours, one in the cloud, or the one you are already paying for. Administration is what you contract; where it lives is a separate decision driven by latency, cost and who needs access.

What if it goes down on a Sunday?

Response times are agreed in writing before we start, based on what the operation can tolerate. A system that bills seven days a week is not looked after the same way as one used Monday to Friday.

Further reading

Other services

Tell us which system needs looking after

Knowing where it runs and how critical it is defines the scope and the response time you need.

Schedule a call