Contact
All services Service

Ongoing operations and support

We take over day-to-day operations on a monthly plan: monitoring and alerts, a support portal, patching, certificate renewals, controlled releases, and backup and restore tests. A monthly overview shows what happened, what changed, what it cost and what needs attention next.

Describe what you need

What you get

  • Heartbeats and alerts for every system in scope
  • A support portal on Jira Service Management, with single sign-on and a full ticket history
  • A release pipeline with approvals, health checks and automatic rollback
  • A schedule for patching, certificate renewals, and backup and restore tests
  • A monthly overview of what happened, what changed, what it cost and what needs attention next
  • A written scope: what is covered, response times and what counts as a separate project

How it works

  1. 01

    Check the handover

    If we did not build or review the environment, a short handover check comes first: what runs today and who looks after it.

  2. 02

    Agree the scope

    We write down what is covered, how fast we respond and what counts as a separate project.

  3. 03

    Set up checks, portal and pipeline

    Heartbeats and alerts are set up for each system in scope, staff get access to the support portal, and releases move to the pipeline.

  4. 04

    Run it month by month

    Patching, certificate renewals, and backup and restore tests run on a schedule. Tickets and alerts are handled within the response times agreed in the scope.

  5. 05

    Report each month

    A monthly overview in plain language covers what happened, what changed, what it cost and what needs attention next.

Problems it solves

  • ProblemAfter go-live the project team moves on, and nobody is responsible for updates, alerts or requests.

    SolutionWe take over updates, alerts and requests on a monthly plan, with a written scope of what is covered.

  • ProblemMonitoring exists, but alerts go to a mailbox nobody reads, so users report outages first.

    SolutionEach system reports its status on a schedule, as a heartbeat that the monitoring watches. When one goes quiet or unhealthy, we are alerted and start troubleshooting.

  • ProblemSmall requests pile up in email and chat, with no record of what is waiting or for how long.

    SolutionRequests and incidents go into the support portal, with single sign-on for staff. The queue shows what is open and how long it has waited.

  • ProblemNobody tracks certificate and licence renewal dates, so one expires unnoticed and a service stops working.

    SolutionCertificate and licence renewal dates are tracked ahead of expiry, and operating systems, platforms and certificates are updated on a fixed schedule.

What it covers

  • For exampleAzure Monitor, Grafana
  • For exampleJira Service Management
  • For exampleGitHub Actions
  • Patching on a fixed schedule
  • Certificate and licence renewal tracking
  • Scheduled backup and restore tests
  • Monthly overview of changes and costs
  • Windows and Linux servers
Typical scope

A monthly plan, sized to the environment. It usually follows a review or an environment setup. An existing environment can also be taken over after a short handover check.

Next step

Send a short description of what you need and the systems involved. We reply with proposed next steps.

Describe what you need