Skip to content

Architecture

Reference architectures and design guidance for building on GRN.CLOUD. Product pages tell you what exists; this section tells you how to put it together and why one shape is better than another.

Platform overview

flowchart TB
    subgraph Site["Regional site — Netherlands"]
        subgraph AZ1["Zone A"]
            N1["Worker nodes"]
        end
        subgraph AZ2["Zone B"]
            N2["Worker nodes"]
        end
        subgraph AZ3["Zone C"]
            N3["Worker nodes"]
        end
        CP["Hosted control plane<br/>HyperShift"]
        CEPH[("Ceph<br/>replicated across zones")]
    end
    CP --- N1 & N2 & N3
    N1 & N2 & N3 --- CEPH

Three independent availability zones per site, each with its own power, cooling, uplinks and network fabric. The control plane runs as pods rather than on dedicated nodes.

Design principles

One control plane. A VM, a container, a function and a served model are all objects in the same API. There is no boundary between "VM infrastructure" and "container platform" to design around.

Isolation is per workload. Namespace, dedicated cluster or dedicated bare metal is a placement decision rather than an account decision. The manifests do not change.

Everything is in Git. Network policy, storage claims and workload definitions are the same kind of artifact as your application code, reviewed the same way.

Portable by construction. The APIs are CNCF-conformant throughout, so what you build here runs on another conformant cluster.

Reference architectures

Planned entries:

Architecture Covers
Isolated private network UDN private subnets with gated egress — see the worked example
Multi-zone HA application Topology spread, PDBs, replicated storage
AI inference platform Gateway, self-hosted models, GPU partitioning, observability
Agent platform Gateway plus MCP servers plus sandbox, and the trust boundaries between them
Hybrid connectivity Submariner, BGP EVPN and site-to-site VPN

Account and compliance

How a cloud account is created, paused, deleted and restored, and how GRN.CLOUD meets its sanctions obligations along the way.

Page Covers
Account lifecycle Sign-up in the shop or at the console, the compliance check, what provisioning builds, the 10 minute grace, the pause and its three reasons, deletion 10 minutes after the pause, restore within 30 days
Sanctions screening What is screened and against what, the match threshold and country risk levels, who decides and how it is recorded, what a block does, and the review procedure for GRN staff