BONITSThink · Do · Achieve
Services

Managed Services

The applications, cloud platforms and data pipelines we build do not stop needing attention at go-live. This is that attention, offered as a subscription with named people, agreed response times and a report you can hold us to.

A round-the-clock operations cycle of monitor, detect, respond, resolve and report, alongside three service tiers: essential, advanced and critical, each with its response commitment.
The same loop every month, with the report at the end of it being the part clients judge us on.
Scope

What we take on

You can hand over a single application, a cloud platform, or the whole estate. Most clients start with the workload that wakes someone up at night and widen the scope once the reporting has proved itself.

Monitoring & alerting

Metrics, logs and traces collected in one place, alerts tuned against real thresholds rather than defaults, and synthetic checks that test the journey a customer actually takes.

Patching & updates

Operating systems, runtimes, container images and dependencies kept current on an agreed cadence, tested in a lower environment first, with an emergency path for a critical vulnerability.

Service desk

A single place for your people to raise an issue, with tickets triaged, tracked to resolution and reported on, rather than requests arriving as messages to whoever is remembered.

Incident management

A defined severity scale, a named person on the bridge, communication while it is running and a written review afterwards that changes something. Not a ticket closed in silence.

Cost & capacity

Monthly review of cloud spend against budget, rightsizing recommendations, commitment planning and an alert when something anomalous starts costing money.

Backup & recovery

Recovery objectives agreed with the business, backups verified rather than assumed, and a restore rehearsed on a schedule so the first real test is not the real thing.

Service tiers

Pick the cover the workload actually needs

Not everything deserves round-the-clock cover, and paying for it everywhere is how managed services get a bad name. We scope tier by workload.

Response times are measured from the alert or the ticket, whichever comes first. Target resolution times are agreed per workload during onboarding.
Tier Cover Priority one response Typically used for
Essential Business hours, US Eastern Next business hour Internal tools, reporting, non-revenue applications
Advanced 24×7 monitoring and on-call One hour Customer-facing applications and the platforms behind them
Critical 24×7 with a named service manager Fifteen minutes Revenue-carrying or regulated workloads where downtime is counted in money

Transparent reporting

A monthly pack covering availability, incidents by cause, work completed, spend against budget and the risks we think you should act on next.

Continuous improvement

A share of every month goes to removing the cause of recurring tickets, so the service gets cheaper to run rather than more expensive.

No lock-in

Runbooks, infrastructure code and monitoring configuration are yours and stay in your repositories. Exit is a handover, not a rebuild.

How it starts

Onboarding takes a few weeks, not a quarter

We do not take on a workload we cannot see. Onboarding exists to get monitoring, access and documentation to a state where the commitments in the table above are honest.

  • Discovery of what is running, what it depends on, who owns it and what has broken before.
  • Instrumentation so that failures are detected by us rather than reported by your customers.
  • Runbooks for the known failure modes, written with your team so nothing lives only in one person’s head.
  • Access and separation agreed, with our activity logged against named accounts, never shared credentials.
  • A rehearsal of one incident and one restore before the service formally starts.

Local managers, global delivery

Project and service managers are locally available and work closely with our clients in the USA, with engineering following the sun so overnight work happens overnight.

The team that built it

Where we delivered the platform, the people who operate it already know it. Where we did not, discovery is how we earn that knowledge before making promises.

An extension of your team

The same working model as our project engagements — in your stand-ups and your ticket queue, not a supplier you email and wait on.

What is currently keeping someone on your team awake?

Tell us about that one workload. We will scope the tier it needs, what onboarding would involve and what it would cost each month, before you commit to anything wider.