BH
Berrington Hunsbury
SYSTEMS NOMINAL · IR LINE OPEN
v.09 · 2026 Berrington Hunsbury Ltd · LDN // 001

We build the systems
that critical
organisations run on. // AND THE DEFENCES THEY DEPEND ON.

Berrington Hunsbury is a technology firm. We design, engineer and secure the platforms behind banks, regulators, operators and growth-stage companies — from cloud-native reference architectures to threat-led SOC programmes and zero-trust rollouts. Hands-on. End-to-end.

bh-control@ldn ~ engagement.sh
$bh status --all // 4 active builds · 2 IR retainers · 1 board brief $bh capabilities --list strategy: "target architectures, due-dil, board" architecture: "cloud · data · platform · integration" cybersecurity: "threat-led · zero-trust · IR · detection" $bh engage --client="..."
09y
// operating
47
// engagements shipped
24/7
// IR coverage
aws · azure · gcp kubernetes terraform zero-trust SOC 2 · ISO 27001 · NIS2 data platforms identity detection engineering threat modelling aws · azure · gcp kubernetes terraform zero-trust SOC 2 · ISO 27001 · NIS2 data platforms identity detection engineering threat modelling
// about

Engineers first.
Advisors when it helps.

We are a small team of architects, platform engineers and security practitioners. Most of us have shipped production systems at banks, regulators or scale-ups before joining the firm. We work alongside your engineers — not above them.

// principles.md 0x01
# core principle
def good_architecture():
  # a system is the sum of its
  # defaults — make them safe. Good architecture is opinionated. It decides what is easy and what is hard, and quietly forecloses a thousand future incidents. # — bh engineering handbook, §1

Berrington Hunsbury was founded in 2017 to do technology work properly: design with intent, build to a publishable standard, and stay close enough to delivery that the design survives contact with production.

We are technology-led, not slide-led. Every engagement produces working artefacts — reference architectures, infrastructure code, threat models, detection rules, runbooks — not just recommendations. Where strategy is needed, it is grounded in what can actually be built and operated.

Our team has run trading platforms, defended national infrastructure, designed identity systems for millions of users, and stood up SOCs from scratch. That perspective shapes how we engineer — pragmatically, in code as well as in prose, and with an eye on the operator who inherits the system on day 91.

// practices

Three capabilities,
one engineering org.v.9

Each capability stands on its own. Most clients use all three over time — strategy without architecture drifts, architecture without security cannot be trusted, and security without engineering is just paperwork.

P_01 · strategy

Technology Strategy

Target architectures, build/buy/partner decisions, and tech due-diligence — grounded in what can credibly be engineered, costed and operated.

  • target state & roadmap
  • cloud / platform strategy
  • tech due-diligence (M&A)
  • engineering operating model
  • board & CIO advisory
// outputs target arch. cost model roadmap board pack
P_02 · architecture

Systems Architecture

Reference architectures, platform design and integration patterns — drafted to a build-ready standard and shipped with the IaC, CI/CD and runbooks to back them up.

  • cloud reference architectures
  • data platforms & mesh
  • API & integration design
  • platform engineering (IDP)
  • SRE & reliability patterns
// stack aws azure k8s terraform kafka
P_03 · security

Cybersecurity

Threat-led security engineering — from architecture review and zero-trust rollouts to detection engineering and a 24/7 incident response retainer for when prevention runs out.

  • threat modelling & arch. review
  • zero-trust & identity programmes
  • SOC build / detection engineering
  • cloud security posture (CSPM)
  • 24/7 incident response retainer
// frameworks MITRE ATT&CK NIST CSF 2.0 ISO 27001 NIS2
// method

How we ship the work../run

A repeatable engineering rhythm. Each phase produces a working artefact — not a deck — that the client can act on without us in the room.

01 · scope

Investigate the system

Two weeks inside the codebase, the cloud accounts, the runbooks and the team. We read the architecture as it actually is — not as the wiki claims — and produce a written assessment with diagrams, risks and a prioritised backlog.

02 · design

Engineer the answer

Reference architectures, threat models and operating patterns drafted to a build-ready standard. Diagrams in structurizr, infra in terraform, controls mapped to MITRE. All version-controlled, all reviewable.

03 · build

Ship with the team

We pair with your engineers to land the work — writing code, configuring pipelines, tuning detections, running game-days. The design we drew is the design we help build. No throw-it-over-the-wall.

04 · operate

Hand over cleanly

Runbooks, ADRs, threat models and detection rules — handed over with a written ops review and a 90-day support window. Where retained, we stay on for incident response and quarterly architecture reviews.

// selected work

Engagements,
shipped.

Identifying details removed under NDA. The shape of the system, the technology and the measurable outcome are not.

// CN_037 · 2024 · SHIPPED Tier-1 Bank

Re-platformed a core integration estate onto an event-driven backbone.

16-week design followed by an 18-month build alongside the bank's platform team. We replaced 40+ point-to-point integrations with a Kafka-based event mesh, reduced critical run-time dependencies by two-thirds, and shipped the first slice into production at week 22.

kafka aws terraform datadog argo
£42m
// run-cost removed
68%
// fewer deps
22w
// to first slice
// CN_041 · 2024 · LIVE CNI Operator

Stood up an in-house SOC with detection engineering from day one.

Threat-led control design followed by a 12-month build of an in-house SOC for a critical national infrastructure operator. We engineered the detection backlog against MITRE ATT&CK, automated triage in Sentinel, and trained the operator's analysts to maintain it. Coverage now exceeds the regulator's benchmark.

sentinel MITRE ATT&CK SOAR azure
94%
// MITRE coverage
11m
// MTTD
0
// reportable inc.
// CN_044 · 2025 · LIVE Specialty Insurer

Built a data platform to underwrite three new lines of business.

8-week target architecture, then a 9-month build of a lakehouse-pattern data platform on Databricks. Real-time exposure and pricing models for three new lines now run on shared infrastructure, with quotation latency down from minutes to seconds.

databricks delta lake dbt azure
3
// new lines live
<2s
// quote latency
9m
// design → live
// CN_046 · 2025 · SHIPPED Public Sector

Shipped a zero-trust identity programme across 14 agencies.

Reference architecture, then a phased rollout of a federated zero-trust identity model across 14 agencies of a central government department. Conditional access, device posture and workload identity unified onto a single control plane. NCSC-reviewed; A+ rated.

entra id SPIFFE SCIM okta
14
// agencies onboarded
220p
// reference doc
A+
// NCSC review

Got a system to build
or defend?

bh engage --start
// engagements
dapo.adisa@berrington-hunsbury.com
PGP: 0x9A4F · keys.openpgp.org
// incident response · 24/7
+44 (0)7761 308 848