TOPIC

Cloud architecture, audited rather than assumed

2 journal posts on Cloud, newest first.

Most cloud estates were never designed — they accreted, and the bill is the last place that shows up honestly. These posts cover the parts worth measuring: idle and untagged spend, egress paid at list price, how much of the estate is genuinely in code, and whether "our data is in Frankfurt" survives contact with the CLOUD Act.

NEWESTJuly 28, 2026Cloud

Five things a cloud architecture audit finds, and why 2027 is the year to look

Cost drivers, sovereignty exposure, IaC coverage and exit readiness — what a read-only cloud audit turns up, and why the Data Act makes 2027 the year.Oleks Saloid · 7 min read July 14, 2026Cloud

A US hyperscaler's EU region keeps your data in Europe physically — not legally. Here's when Hetzner genuinely wins, when AWS EU is still the right call, and how to decide.

A Frankfurt region on a US hyperscaler is not sovereignty. When Hetzner wins on economics, when AWS EU is still right, and a decision framework for DACH.Oleks Saloid · 11 min read

Want this in your inbox?

Regulatory & Architecture Radar

One note per month for mid-market data teams. Only when there's something worth reading.

or write: hello@saloid.com · gräfelfing · de