How to choose a Datadog partner in the UK

What the partner tiers actually tell you

Datadog's partner network has several tiers. At the time of writing, the programme includes Trial, Partner, Advanced, and Premier levels. These tiers measure commercial activity and engagement with Datadog's go-to-market programmes. They tell you that a firm is a registered, active part of the Datadog channel. They do not, on their own, tell you how deeply a firm actually runs Datadog in live production environments.

Advanced Partner status - which Critical Cloud holds - means Datadog has recognised our technical capability and customer success track record. It sits below Premier, so it would be inaccurate to call it the highest tier. What it does mean is that we have demonstrated depth in implementation and ongoing managed operations, not just resale.

The credential that matters most - and the one worth asking about specifically - is "Powered by Datadog" accreditation.

What "Powered by Datadog" accreditation actually means

"Powered by Datadog" is not a partner tier. It is a separate accreditation that Datadog awards to MSPs whose managed service is genuinely built on the Datadog platform. To receive it, Datadog's engineering teams conduct a formal technical review of how the provider actually operates - not just whether they sell or configure Datadog, but whether they use it as the operational backbone of a managed service that runs 24/7.

Critical Cloud is the world's first organisation to receive this accreditation. We hold it because our entire Critical Support service runs on Datadog - every customer environment is instrumented through Datadog, every alert fires through Datadog, every incident is managed and documented through Datadog, and every customer has direct access to their own Datadog environment at all times. Datadog is not a layer we put on top of a proprietary monitoring system. It is the operational foundation.

Operational depth vs project delivery

Most Datadog partners fall into one of two categories: consultancies that configure and implement, and MSPs that operate ongoing. Both are legitimate, but they are different things, and the one you need depends on what you are actually trying to solve.

If you need Datadog set up properly and want to run it yourself afterwards, a project partner is probably the right fit. They configure instrumentation, build dashboards, set up alerting, and hand over. The engagement has a clear end date.

If you need Datadog to be part of how someone else is running your cloud environment on an ongoing basis - alert triage, incident response, monthly improvement work, tuning that keeps pace with your platform as it evolves - you need an MSP that operates Datadog rather than just implements it. The difference shows up in how they describe the service. Listen for whether they talk about running environments versus configuring them.

The questions worth asking

When evaluating a Datadog partner in the UK, these questions separate operational depth from project capability. The answers should be specific and concrete, not generic.

Do I keep direct access to my Datadog environment?

A traditional MSP often puts a proprietary monitoring layer over your infrastructure and gives you a customer portal. You see what they decide to show you, which may be a simplified view of the underlying data. An MSP that genuinely runs Datadog should give you direct, unrestricted access to your own Datadog environment. If the answer is anything other than "yes, always, full access," ask why.

How do you operate Datadog day-to-day, not just configure it?

Ask for specifics: how do they maintain alert hygiene as the environment changes, how do they tune thresholds over time, what does their monthly improvement work look like, and how do they use Datadog in incident response. A firm that only configures at the start will answer with implementation steps. A firm that operates will talk about ongoing backlog management, regular tuning, and Datadog as the evidence layer for improvement work.

How is the service structured around incident response?

Ask about their severity model, response time commitments, and what happens during a SEV-1. Ask whether they use Datadog Incident Management for tracking, and whether you will receive a postmortem after a serious incident. Ask who specifically is on call and what the escalation path looks like. Vague answers to these questions are a reliable signal.

Can you show me a reference from a customer whose environment you operate, not just implement?

This is the most direct filter. Implementation references are easy. References from customers whose 24/7 production environments are being operated ongoing are much harder to manufacture. If the reference only covers a project engagement, note that distinction carefully.

What "good" looks like in practice

A good Datadog MSP will have a structured way of describing the split between their responsibilities and yours. They should be clear about what they own (monitoring configuration, alert management, incident response, improvement backlog) and what remains yours (application code, business decisions, access approvals). This shared responsibility model should be documented, not vague.

They should also be able to talk specifically about the improvement work they deliver - not just maintaining the status quo, but measurably improving signal quality, reliability, security posture, and cost over time. If a partner is only describing a maintenance arrangement, that is not the same as an MSP that is actively working your environment's backlog every month.

Finally, look at their security posture. ISO 27001 and Cyber Essentials Plus are the baseline for any MSP operating UK cloud environments with access to production infrastructure. Absence of these certifications should prompt questions about how they manage access, change control, and data handling.

A note on the UK market specifically

Most Datadog partners with UK presence are either global SIs with a UK office or UK-native boutique firms. The global SIs typically bring broad Datadog knowledge but may rotate consultants and lack continuity. The UK-native firms typically offer more consistent relationships but vary widely in operational depth.

For regulated sectors or businesses where data residency matters, it is worth confirming that the MSP understands the difference between Datadog's EU site (data stored in Frankfurt) and the US site, and can configure your environment accordingly. GDPR and sector-specific regulations affect how observability data should be handled, and a partner who cannot answer those questions confidently is probably not operating at the level you need.