Skip to main content

Sovereign Stack

Kilimanjaro is a Sovereign Stack — a category-defining position above sovereign-cloud substrate. This page covers what that means as an architectural choice: where the Stack sits relative to existing platform categories, what compositional property makes it structurally different, and the four-persona claim that orients every other architectural decision documented in this category.

1. Stack, not Cloud​

Sovereign Cloud — OVHcloud, T-Systems, Bleu, Gaia-X-aligned providers — refers to the IaaS layer: compute, storage, and network within a chosen jurisdiction. The substrate is sovereign; what runs on top is the customer's problem.

Kilimanjaro is not Sovereign Cloud. It is the Sovereign Stack — the integrated platform layer that sits above sovereign-cloud substrate and composes data, security, control, compute, and identity under one customer-controllable boundary. Customers comparing Kilimanjaro to an existing sovereign-cloud vendor are comparing different layers: the Stack consumes that substrate; it competes with multi-vendor stacks built on it.

The relationship is complementary. The Stack runs on sovereign-cloud (Hetzner-EU, OVHcloud sovereign regions); it is not itself sovereign cloud. The substrate handles compute, storage, and network within the customer's chosen jurisdiction; the Stack handles every layer above that — the database, the auth surface, the policy plane, the audit ledger, the compute runtime, the extension framework, the agentic-execution model.

Sovereign Stackone customer-controllable boundarydatabaseauth surfacepolicy planeaudit ledgercompute runtimeextension frameworkagentic-execution modelthe Stack consumes the substrateSovereign-cloud substrate (IaaS layer)compute, storage, and network within the customer's chosen jurisdictionHetzner-EU, OVHcloud sovereign regions
The substrate supplies compute, storage and network in a chosen jurisdiction; every layer above it is the Stack, composed under one boundary.

2. Why an integrated Stack instead of a multi-vendor stack​

The conventional approach to building a sovereign data platform is multi-vendor: pick a sovereign-cloud IaaS, pick a database, pick an auth vendor, pick a secrets manager, pick a workflow engine, pick a BI tool, integrate them, audit them individually, and hope the seams do not leak. The result is operationally sovereign in pieces but compositionally fragile — every cross-component flow re-implements identity, policy, and audit at the application layer, and the audit trail fragments across vendor surfaces.

Kilimanjaro composes the layers structurally. One identity model carries from sign-in through every API call. One JSON-policy language compiles to row-level security on collections, access checks on storage, approver constraints on irreversible actions, and auto-approval predicates on Maker-Checker workflows. One audit ledger captures every layer's contribution under a single request ID. One custody ladder governs key material across the entire data plane. The compositional integrity is the structural property the multi-vendor stack cannot reproduce.

The trade-off is not between capability and integration; it is between fragmented commodities and structural asset custody. A multi-vendor stack assembles isolated, software-only point solutions that remain structurally blind to the underlying infrastructure layer. Kilimanjaro delivers hardened, infrastructure-native primitives that outclass legacy point solutions precisely because their security boundaries are etched into the silicon. For missions where security, structural multi-tenancy, and absolute jurisdictional control are non-negotiable, the integrated Stack is the logical architecture.

3. The four-persona claim​

The most distinctive architectural claim is the four-persona coverage. Every customer organisation that adopts a data platform has four roles to support:

PersonaRoleWhat they need first-class
Developer (Architect)API surface, schemas, queries, functionsBaaS-grade developer experience — SDKs, migrations, real-time, semantic search, the four-pillar API
Governance (Warden)Compliance, audit, residency, approvals, policyIdentity-bound audit attribution, JSON-policy authoring, custody ladder, Maker-Checker, region-pin sovereignty
Business-author (Pathmaker)Visual authoring of forms, workflows, dashboards, policiesConsole authoring surfaces that compile to platform primitives — no code-vs-no-code drift
Business-consumer (Scout)Workflow execution, dashboard consumption, capture surfacesOperational surfaces consuming the same data the developers and authors build against

No existing platform category holds all four first-class without compromise. BaaS platforms (Supabase, Firebase) target developers but leave governance and business roles as integration work. Identity vendors (Auth0, Clerk) target one slice. No-code platforms (Retool, Airtable) target business roles but compromise on the developer surface. Sovereign-cloud providers handle infrastructure without addressing the application-layer composition.

The four-persona coverage is the Stack's organising principle. Each pillar earns its place by serving one or more personas without forcing the others into second-class status.

4. Structural sovereignty as a property​

Most platforms treat sovereignty as a deployment posture — where the compute and storage live. Kilimanjaro treats sovereignty as a structural property — who holds the keys, who can compel access, who holds the audit trail, what guarantees survive a vendor failure.

Three architectural decisions establish the structural sovereignty:

DecisionMutabilityEffect
Region pinImmutable post-creationData plane stays inside the chosen jurisdiction for the project's lifetime; re-pinning is operationally a project recreation, not an API call
Custody modeBidirectional with attestationKeys live where the custody mode is set — Platform-Managed, SKR (Secure Key Release, integrity mode), BYOK (Bring Your Own Key), or HYOK (Hold Your Own Key). Moving between modes is a custody-policy update; descending to a weaker mode requires IRREVERSIBLE_ACTION_GATE attestation
Control-plane regionImmutable post-org-creationThe org's metadata, audit log, and admin Console live in a region distinct from any data-plane region — the org operates audit and ops centrally while every project's data stays inside its own jurisdiction

The immutability is the structural property. A platform that lets you PATCH region is one API call away from moving customer data across a sovereignty boundary; a platform where region-pin requires recreation is one where the boundary holds because the system literally cannot violate it. The same shape applies to control-plane region.

Custody mode is the exception — it is bidirectional because it concerns key location, not data location. The same data can be re-keyed across custody modes without moving. The downgrade friction (the IRREVERSIBLE_ACTION_GATE attestation) is the structural protection: moving keys from a stronger custody mode to a weaker one is a conscious decision, not an accident.

The mechanics of region pin live in Regions & residency; the custody ladder is documented in Custody architecture; the operational guide for setting sovereignty on a project lives in Guides → Sovereignty.

5. What the Stack refuses to be​

A coherent architectural posture is defined as much by its constraints as its capabilities. Kilimanjaro enforces three absolute boundaries:

We are not a Sovereign Cloud IaaS. Kilimanjaro does not lay physical fiber or rent bare-metal racks. The Stack operates as the software substrate that consumes and hardens sovereign hypervisors, translating raw infrastructure into a unified secure perimeter.

We are not an à-la-carte Platform-as-a-Service (PaaS). Kilimanjaro is one integrated stack, not a patchwork of parts. We do not allow customers to swap out our identity kernel or audit ledger for third-party commodities. To break the core layers apart is to re-introduce the integration seams and identity blind spots we exist to eliminate.

We are not a borderless commodity backend. Kilimanjaro does not tax your growth through variable user pricing, nor do we abstract away data borders for soft convenience. We provide structural asset custody under your absolute jurisdictional control.

6. See also​