Service 06 · Application Support

Help that arrives when production misbehaves.

When something is slow, down or just odd, a named engineer works the problem with you, and tells you what they find.

  1. Reportyou reach us
  2. Triagesize the problem
  3. Fixwork it with you
  4. Learnwrite it up
What you get

What lands on your desk.

A named engineer

Someone who knows your setup, not a ticket queue.

Honest updates

What we know, what we do not, and what happens next.

A written follow-up

A short post-incident note so the same problem does not return.

Agreed hours

Support times set out in advance, so you know when we are on.

How it works

Four steps, drawn as we go.

  1. 1

    Report

    You tell us what you are seeing.

  2. 2

    Triage

    We decide how urgent it is and who works on it.

  3. 3

    Fix

    We work the problem with your team until it is stable.

  4. 4

    Follow up

    A note on the cause and the change that prevents a repeat.

Tools we use

What is on the bench.

Engagement types

Three ways to work together.

We agree scope and price after a conversation, so there are no numbers on this page.

One-off

A defined piece of work with a clear end: a design, a build or a review.

Retainer

A set amount of senior time each month for changes, advice and reviews.

Managed

We run it day to day, with monitoring, alerts and support included.

Related blueprint 02

Prometheus and Grafana on ECS

A reference architecture: metrics scraped from every service, dashboards the team actually opens, alerts that reach a person.

Read the blueprint →
Sheet 06 · Start here

Got a messy cloud? Let's draw it out.

Tell us what's broken or what you're planning. We reply within 48 hours.

no sales script, just a drawing

What do you need?

We reply within 48 hours.

FILED

Thanks. Your note is on the sheet and we will be in touch.