HPC-AI Advisory Council UK 2026, the national compute

Conference
HPC-AI Advisory Council
The UK’s new public compute infrastructure, as presented at the HPC-AI Advisory Council 8th Annual UK Conference, the national systems that came up, and the instability of funding behind them.
Author

Kolen Cheung

Published

October 16th, 2026

NoteSeries: HPC-AI Advisory Council UK 2026
  1. Summary: a map of the talks, the highlights and the people
  2. The national compute: the new structure, its systems and its funding
  3. Day 1, 13 October
  4. Day 2, 14 October
  5. UK HPC systems

AI tools, Claude and ChatGPT, helped me digest the material: unpacking a talk’s slides, explaining a term I didn’t know, and researching the systems. I’ve checked what they said against the sources linked.

Unpacking the new public compute infrastructure

The keynote presented a new structure on public compute infrastructure. Here’s a digestion on that.

Before: the tiers, sorted by size

The keynote’s “Vision for the UK’s public compute infrastructure” slide (p. 5) lumps “PRACE, DoE, ARCHER2, DiRAC, EPSRC Tier 2” together under current structures as “tiers 0–2”, with institutional systems as “Tier 3”, and AIRR’s Isambard-AI and Dawn in a row of their own.

Slide: Vision for the UK's public compute infrastructure. On the left, current structures: current UKRI and international systems and users (PRACE, DoE, ARCHER2, DiRAC, 'tiers 0-2', EPSRC Tier 2), current institutional systems and users ('Tier 3'), AI Research Resource systems and users (Isambard-AI, Dawn), and new users. In the middle, the transformation programme of BIST and UKRI investments: compute, data storage and network infrastructure; data curation and management, including TREs; expansion of the AI Research Resource; a new national supercomputing service at Edinburgh; software and tooling; people and communities; National Supercomputing Centres; Compute Roadmap initiatives. On the right, the vision for the future ecosystem: EuroHPC and international partnerships; a UK R&I Compute Federation of the NNSS, the AIRR and National Compute Resources; and, locally, institutional and specialist disciplinary compute.

The usual meaning of each tier is:

Tier What it is Examples
0 International, beyond one country PRACE (now EuroHPC), and DoE’s machines in the US
1 National services ARCHER2 (EPSRC/NERC) and DiRAC (STFC)
2 Regional or specialist systems, funded by EPSRC and hosted by a university or a consortium Isambard 3, Baskerville, Cirrus, CSD3, JADE, Kelvin2…
3 A university’s own cluster QMUL’s Apocrita, Exeter’s own

In this model, each research council funded and allocated its own systems, and the Compute Roadmap calls the result “fragmented and uncoordinated”. Tier 2 was a series of fixed-term EPSRC grants. That is why Isambard 3’s grant ends in March 2027 for example.

After: three national services, sorted by purpose

The keynote’s next slide, “Where to go” (p. 6), puts three services under a “UK R&I Compute Federation”:

  • NNSS: “mission driven modelling and simulation workflows at the largest scale”. This is the successor of tier 1’s ARCHER2.
  • AIRR: AI workflows, with “strategically managed access driven by Government priorities”. AIRR started in 2023 (Isambard-AI and Dawn) and was never part of the tiers.
  • NCRs: “accessible for all workflows at a smaller scale”, on a range of hardware. The NCR slide (p. 26) calls them “an evolution of support for ‘tier 2’”. UKRI funds the infrastructure, and the platform and access layers are built together with the sites. The NCRs come in a “rolling programme of phased investment” rather than as one-off grants to each centre.

What stays the same:

  • EuroHPC is still the international layer.
  • A university’s own cluster is still there, as “institutional and specialist disciplinary compute”, the local layer on the right of p. 5.

What’s new around the three services:

  • Users apply through one portal, the “single pane of glass”, for the NCRs, AIRR and the NNSS.
  • Community Centres of Excellence (CCEs) give user support for each research domain, separate from the systems themselves.

How the old systems move

Slide: UK R&I Compute Provision: A time of transition. A timeline from 2019 to 2029: ARCHER, then ARCHER2 with an extension to the end of 2026; DiRAC to the end of 2027; other tier-2 to 2025; NCRs, phased, from 2026; the NNSS from 2028; AIRR from 2024; EuroHPC from 2022. A dashed box marks transitional arrangements from late 2026 to the end of 2027.

The transition slide (p. 15) shows:

  • ARCHER2 → NNSS. In between, the NCRs on CPU (Cirrus, and Charger from the end of 2026) fill the gap after ARCHER2 ends in November 2026 and before the NNSS goes live in Q4 2027.
  • DiRAC → the NNSS and the NCRs over 2026–2028, as the talk put it. DiRAC stops being a separate tier 1 service.
  • “Other tier-2” → NCRs, phased. Some of the tier-2 systems become NCRs: Isambard 3, Cirrus, and Baskerville as a new system. The slide ends the “other tier-2” bar in 2025, and the phase 1 list names no others.

A diagram from before to after. Before, tiers by size: tier 0, international (PRACE, DoE); tier 1, national (ARCHER2, DiRAC); tier 2, regional and specialist, funded by EPSRC (Isambard 3, Cirrus, Baskerville, CSD3, JADE, Kelvin2, Bede and others); tier 3, institutional; and AIRR, since 2023 (Isambard-AI, Dawn). After, by purpose: EuroHPC and international partnerships; a UK R&I Compute Federation of the NNSS, for modelling and simulation at the largest scale from Q4 2027, the AIRR, expanded with Zenith and a new £750m system, and the NCRs, for all workflows at a smaller scale, phase 1 being Charger, Cirrus, Isambard 3, Baskerville, Mary Coombs and Zenith; and local, institutional and specialist disciplinary compute. Tier 0 goes to EuroHPC; tier 1 to the NNSS, and to the NCRs as a stopgap after ARCHER2 and for DiRAC over 2026–2028; tier 2 to the NCRs, phased; AIRR to the expanded AIRR, twentyfold; tier 3 to local.

So the main change is that tier 1 and tier 2 stop being levels of size. Systems are grouped by what they are for instead: the largest simulations (NNSS), AI (AIRR), and everything else on a mix of hardware (NCRs). That is also why the NCRs are both a stopgap for ARCHER2 and meant to stay.

A map to national HPC systems

The HPC systems in the UK that came up over the two days, and the national services they are part of, are on UK HPC systems, with where each came up. It is a page I’ll keep adding systems to.

Three more came up from outside the UK and Europe:

El Capitan
At Lawrence Livermore, #1 on the TOP500 from November 2024 until June 2026, when it became #2, and a Starfish customer (Starfish).
Fugaku and FugakuNEXT
RIKEN’s Arm supercomputer on Fujitsu’s A64FX, #1 on the TOP500 from June 2020 to November 2021, and its successor, aiming at 100× its application performance with the MONAKA-X CPU (Fsas Technologies).
Eos
NVIDIA’s own supercomputer, 4,608 H100, which QMatter ran on alongside a quantum computer at LRZ (the venture scientist).

The instability of funding

A sysadmin from EPCC I met at the conference (meeting other people) and I discussed the instability around funding and maintaining HPC in the UK, including for the dRTPs (digital research technical professionals, UKRI’s umbrella term for the people working in this space). I said HPC in the UK feels unstable to me, without a guaranteed future: it often works by writing the next proposal, and planning on the assumption that it gets a green light.

He said that is exactly what happened to them. In 2023, under Rishi Sunak, Edinburgh was chosen to host the UK’s exascale supercomputer, about £800m. Keir Starmer’s government cut it in August 2024, a month after taking office, and brought it back in June 2025 at up to £750m, no longer called exascale. ARCHER2 is in room 3 of EPCC’s Advanced Computing Facility, and in anticipation of the new supercomputer, which room 3’s floor space and power could not take, they built room 4, a new £31m wing. During the uncertain period, from the cut until the system came back, all that work felt wasted.

We compared the UK situation with the US from time to time, as I had some experience there in the past. I don’t fully understand the big picture, but it seems the national lab model in the US, and its funding (e.g. through the DoE), are much more stable, so HPC facilities and their people can thrive there. And because of that stability, they can plan for the long term and collaborate: they are not in competition, at least not as cut-throat, and not as much in fire-fighting mode, so they can invest in the future. Notable technologies from there are ZFS on Linux and Spack from LLNL, and Shifter and Podman-HPC from NERSC. He also observed that the stack in the UK seems less of a joint effort reused across HPC centres, e.g. EPCC’s SAFE and Bristol’s AIRRPortal.

Let’s hope that the new structure provides a more stable foundation, both for planning the hardware and for the dRTPs, so that we can invest more in the future and collaborate more.