Blog

Field notes from people who run the infrastructure.

Not product announcements. What we learn operating a Dutch cloud platform — where hyperscaler bills actually come from, what data residency means once a lawyer reads it, and what happens to the heat a rack produces. Written by engineers, for the people who have to make the call.

  • Cloud economics
  • Sovereignty & GDPR
  • Sustainable infrastructure

Three articles · No gated PDFs · No "download the whitepaper" wall

Written by
The GRN.CLOUD engineering team
Published
When we have something worth saying
Topics
Economics · sovereignty · sustainability
Audience
Platform engineers, CTOs, MSPs, DPOs
Format
3–5 minute reads, no registration

Latest

The most recent thing we wrote down.

Cloud economics·16 April 2026·5 min read

You probably don't need AWS (and that's okay)

Hyperscalers are engineering marvels — if you are Netflix, or training a model on ten thousand GPUs. But most European companies running a web application, a handful of APIs and some background jobs are paying for scale they will never reach and complexity nobody asked for. A candid look at what that bill is actually buying, and what a right-sized platform looks like instead.

Read the article →

All articles

Short, specific, and written from the operator's side of the rack.

Sustainability·2 April 2026·4 min read

Our servers heat greenhouses. No, seriously.

Offsets, renewable energy certificates and a tree per signup are accounting magic. Datacentres consume 1–2% of the world's electricity and turn nearly all of it into heat — so the interesting question is not how you buy it, but what you do with it afterwards. What we do with ours, and why that dictates the size and shape of our sites.

Read the article →

Sovereignty·19 March 2026·3 min read

Why your data belongs in Europe (and why it matters more than you think)

A founder's German client flagged that user data was being routed through US servers. Nothing shady was happening — but under GDPR that is a problem, and it cost three months of migration, rewritten policies and apologies in meetings. The lesson: "where does the data actually live?" is a question to ask before you build, not after.

Read the article →

We publish when we have something specific to say rather than on a content calendar. If you want to be told when the next one lands, say so.

What we write about

Three subjects we know first-hand, and one we refuse to publish.

Cloud economics

Where a cloud bill actually comes from: egress, cross-zone traffic, IOPS tiers, idle over-provisioning. How to size a platform for the load you have instead of the load a reference architecture assumes.

Sovereignty & compliance

What GDPR, Schrems II and the Cloud Act mean once procurement reads them properly — and the difference between an EU region and an EU provider.

Sustainable infrastructure

Grid congestion, peak shaving and heat reuse as engineering constraints rather than marketing claims. What it changes about how you design a datacentre.

What we don't publish: launch posts dressed as insight, benchmarks tuned until we win, and anything that needs a form before you can read it. If an article isn't useful to someone who never becomes a customer, it isn't worth writing.

Go deeper

The reference material behind the articles.

Platform features

Every component of the stack, named and explained.

Browse →

Security

The control set, and where our responsibility stops.

Read →

FAQ

87 answers about how the platform works.

Open →

About us

Why GRN.CLOUD exists and who is building it.

Meet the team →

Reading about it is the slow way to evaluate it.

Start on the Alpha and put a real workload on the platform — or bring us the migration you are weighing up and we will tell you honestly whether it fits.

100% renewable energy · Dutch jurisdiction · No egress charge