Do DevOps consultants need professional indemnity insurance?

Yes. If you are advising on architecture, writing infrastructure code, or making changes that touch production, you can be held liable if that work causes a client financial loss — that is exactly what professional indemnity (PI) insurance covers.

For DevOps and infrastructure consultants specifically, the risk is not hypothetical: a bad Terraform apply, a misconfigured deployment pipeline, or advice that leads to an outage or a large cloud bill can all translate directly into a client's financial loss. PI insurance covers your legal defence and any damages if a client claims your work (or advice) caused that loss.

A few things worth checking when you take out or renew a policy:

• Cover matches what you actually do — infrastructure and cloud work is a different risk profile to generic "IT consulting," so make sure the policy wording covers hands-on production changes, not just advice.
• Retroactive date — so you stay covered for work done under a previous policy if a claim surfaces later.
• Cover limit — sized to the scale of the systems you touch, not just your day rate.

Most contracts (and many agencies/clients) will require proof of PI cover before you can start, so treat it as a cost of doing business rather than optional overhead. Public liability and cyber insurance are the other two policies worth having alongside it — see Contractor Insurance: Your Essential Safety Net for the wider picture on all three.

As a reference point, UK-based providers commonly used by IT contractors for this specific cover include Kingsbridge, Markel Direct, and PolicyBee — it is worth comparing at least two quotes, since PI premiums vary significantly by declared day rate and whether infrastructure/cloud work is explicitly listed on the policy.