Monitoring and alerting
Uptime, errors, slow pages, full disks, and expiring certificates, with alerts that reach a named engineer.
Managed hosting and monitoring
We watch the graphs so your team does not have to.
Overview
Uptime is a habit, not a promise. We instrument the things that break, set alerts that mean something, and respond on an agreed schedule, including the hours when nobody is at a desk.
What you get
- Alerting around the clock with a named responder
- Dashboards for latency, errors, and spend
- Patching and backup verification
- Quarterly resilience review
What we offer
Managed hosting and monitoring, in detail
Pick the parts you need. We scope them together, quote a fixed price, and build in two-week steps.
Incident response
An agreed response time, a person who picks up, and a written note after every incident on what happened and what changed.
Patching and upgrades
Operating systems, databases, and frameworks kept on supported versions on a regular schedule.
Backups you have tested
Automatic backups, plus regular restores to prove they actually work.
Cost control
A monthly look at the cloud bill, with unused resources removed and right-sized servers.
Resilience reviews
A quarterly review of risks, capacity, and what to improve next, in plain language.
Where it fits
Typical projects
- Running a web app after the original developer has moved on
- Watching an e-commerce site through a festive season sale
- Looking after servers for a business with no in-house IT team
- Keeping a SaaS product within its uptime commitments
Technology
What we use
Well-supported tools with a long runway, chosen for the project rather than for novelty.
- Grafana
- Prometheus
- Uptime Kuma
- Sentry
- AWS CloudWatch
- Azure Monitor
- Cloudflare
Where AI fits in
We use AI to group related alerts and summarise logs during an incident, so the engineer on call gets to the cause faster. Decisions about fixes stay with the engineer.
How it works
From first call to production
Every engagement follows the same shape, so you always know what happens next and what you will see.
- 01 · Week 1
Scope
We sit with the people who will use the thing. You get a written scope, a fixed estimate, and an honest note about what we would cut first.
- 02 · Weeks 2 to 10
Build
Two-week iterations against a shared board. You see working software every fortnight, not a status deck.
- 03 · Launch week
Launch
Staged rollout, real monitoring, and a rehearsed way back. We stay on the call until the graphs go flat.
- 04 · Ongoing
Run
Patching, alerts, and a monthly review of cost and reliability. Leave with your code and your documentation whenever you want.
Questions
Frequently asked questions
Can you manage systems you did not build?
Yes. We start with an onboarding review, document what we find, fix urgent risks, and then take over day-to-day running.
What are your response times?
They are agreed in the contract per severity level. Critical issues get a response around the clock.
Are we locked in?
No. Everything runs in your accounts with documentation, and the retainer ends with a notice period.
Related
More from Run
Have a project like this in mind?
Send a paragraph about what you need. An engineer replies within one working day, and you get a written scope with a fixed price within a week.