A first-ever national Code Red. For us, a non-event — because we were ready.

A credential you can't reach is a credential you don't have. For a vault, staying available — every time, from anywhere — isn't a feature; it's the whole job.

This week the Netherlands declared its first-ever national "code red" for extreme heat — a 40°C event the country had not faced since it began keeping records in 1901 [1][2]. By Friday the heat had climbed all the way to the layer almost nobody thinks about until it fails: the data center. Our provider in Amsterdam, Leaseweb, did exactly the right thing and warned us early — the facility was running hot, it had started powering down parts of its own infrastructure to shed heat, and the machine we keep there might be next. We checked it: healthy, serving normally. Then we went back to work. Not because we were certain Amsterdam would hold — because it does not have to.

A hot data center in Amsterdam is not allowed to be our problem

The box in Amsterdam is one of two anchors in our management system — the behind-the-scenes brain that runs and coordinates our fleet. And before anything else, the plain-language point that matters most: this is not the vault that holds and serves your credentials. Those run on a completely separate, independent plane — a different global system entirely — that this heat never went near. The management brain and the vaults your agents actually talk to are two different worlds: a bad day for one is simply not a bad day for the other. We just hold that management brain to the same standard as everything else — never a single point. So there are two anchors, on purpose — one in Amsterdam (Leaseweb), one in Osaka (Ablenet). Two continents. Two providers. Two power grids. Two climates. A 40°C afternoon in the Netherlands has no physical bearing on a machine in Japan: different weather, different grid, different failure domain entirely. (Fun fact: while Amsterdam pushed 40°C under a national code red, Osaka sat at about 29°C in the middle of its rainy season — eleven degrees cooler, half a world away, on a completely unrelated weather system. That gap is the design.) The two anchors stay continuously in sync, so neither is ever far behind the other. If a heatwave, a grid fault, or a provider incident took Amsterdam offline, the worst case is a short, bounded failover to the other side of the planet — not an outage.

Resilience isn't a feature of a credential vault. It's the product.

A credential vault is the most load-bearing thing in a stack: every app, pipeline, and agent authenticates through it. When it answers, everything works; when it cannot, everything stops at once. That asymmetry is why resilience is not something you bolt on later. You do not want to discover, on the hottest day in a century, whether your one data center, in your one city, on your one grid, can take the heat. You decide it on a cool day, by refusing to bet the company on a single climate. We made that call long ago: no single region, provider, grid, or weather system is ever allowed to be the whole story.

The honest version

Nothing makes infrastructure immune. Weather fails, grids fail, providers fail — and anyone who tells you otherwise is selling. What you actually get to choose is whether any one of them failing can take you down with it. We chose two hemispheres so the answer is no. This week tested that choice in the most literal way possible, and the test was boring: Amsterdam kept serving through the heat, and even if it had not, the design already had the answer waiting in Osaka.

Build for the disaster on the day it isn't happening

That is the whole discipline. The cool day is when you build for the hot one; the hot day is when you are quietly glad you did. This week was a hot day — a record one — and for us it was a non-event. That is exactly what it is supposed to be.

Credit where it is due: Leaseweb handled the heat the way good operators do — early warning, protective action, no drama. The best providers tell you before there is a problem. Our job is just to make sure that when one site has a bad day, it was never the only site.

Clavitor (@clavitorai) is the credential vault built for AI agents, and against them. clavitor.ai

Sources

[1] NL Times — Dutch heatwave now official; historic Code Red hot-weather alert (first-ever national code red for extreme heat; longest June heatwave since records began in 1901): https://nltimes.nl/2026/06/25/dutch-heatwave-now-official-historic-code-red-hot-weather-alert-debated

[2] DutchReview — NL temperatures to reach up to 40 degrees (peak inland temperatures approaching 40°C): https://dutchreview.com/news/netherlands-up-to-40-degrees-then-plummet-to-21-degrees-25062026/