We built Riskbit because we were tired of heat maps.

The founding story

Riskbit started in a post-incident review in late 2024. A mid-market retailer had just spent three weeks quantifying a 48-hour outage. The number — £4.6m — landed in a board pack already two weeks old. The actionable insight had decayed to a footnote.

Our founders had lived that moment too many times. They had also, separately, sat inside banks and insurers where cyber risk lived on one spreadsheet and business continuity on another — and where no one could say, on any given day, what either cost the business.

So we started building. Not another GRC tool. Not a repository. A live quantification platform driven by the asset taxonomy itself. If you know what applications run on what systems in what locations, supported by what staff on what suppliers, you can model almost any failure — and price its consequences.

What we believe

Risk is rhythmic, not static. A heat map is a photo. Riskbit is a pulse. Real risk moves every hour — supplier outages, control drift, market conditions — and your tooling should reflect that.

£ beats colours. Every exec decision is ultimately a financial one. Tools that can't output pounds can't inform those decisions.

Cyber and continuity are one domain. The artificial split between them is an organisational accident, not a real distinction. A datacentre fire and a ransomware attack both end with the same thing: critical capabilities offline and £ bleeding.

Procurement shouldn't gatekeep rigour. If a £30bn bank can try Linear for £8/month, a £300m retailer should be able to try Riskbit without signing an NDA.

The team

We're a small team of ex-CISOs, ex-CROs, actuaries, and engineers. Based in London and Manchester. Backed by a patient seed investor who cares more about board-grade output than MRR slide geometry.

We're hiring — see careers.