Skip to content

Managed services · Operations

Your servers, held by a team.

We take over the day-to-day running of your infrastructure: what is up, what is backed up, what needs patching. Your developers get back the time they were spending on system administration.

Monitoring

24/7

Backups

Daily, encrypted

Restore test

Quarterly

Patching

Agreed window

On-call

Per contract

Report

Monthly

Indicative scope: it is settled service by service in the proposal.

The service

What we do while you ship.

Managed services are not a helpdesk. They are steady work — updating, watching, backing up, documenting, fixing — that only becomes visible on the day it was skipped. We write it into the contract so you know exactly what is covered.

Monitoring and alerting

Machines, services and certificates watched continuously. The alert reaches us, not you, and work starts before your first question.

Backups that restore

Encrypted backups, kept off the machine they protect, with restores tested at regular intervals. A backup never restored is not a backup.

Security patching

We track vulnerabilities in the components we run, apply patches in a window planned with you, and keep a way back.

Documentation kept current

Diagram, inventory, recovery procedures: your installation is written down, and the document is handed over whenever you ask.

Monthly report

A document a director can read: incidents, interventions, capacity, patches applied and what to watch next month.

On-call cover

For blocking incidents, out-of-hours cover can be written into the contract, with a stated response time.

What we take over

Inside the fee.

  • Operating systems, updates and baseline hardening.
  • Infrastructure services: databases, web servers, queues, containers.
  • Backups, retention and restores on request.
  • Monitoring, alerting and incident diagnosis.
  • Network, addressing and firewall rules for the machines in scope.

What we don't take over

Plainly.

  • Developing your application and fixing its bugs.
  • Supporting your end users.
  • Vendor licences, which stay in your name.
  • Workstations and office IT.

Taking over

Picking up an existing setup.

We don't insist on starting from scratch. The takeover runs in stages, with no unannounced downtime.

  1. 01Week 0

    Audit

    Inventory of what exists, a record of access, backups and weak points. You get the findings in writing, even if you don't sign.

  2. 02Week 1

    Takeover plan

    Scope taken over, service levels, urgent fixes to apply and the schedule. In one priced document.

  3. 03Weeks 2 to 4

    Under monitoring

    Access transferred, monitoring and backups connected, documentation rebuilt. Nothing moves until the watch is in place.

  4. 04Then on

    Operations

    The service moves to steady state: logged interventions, planned maintenance windows, monthly report.

Let's talk about your infrastructure.

Describe what you run today and what has to change. You get a priced proposal and the person who will follow the account.