Overview
What Kilimanjaro is and how it is put together. One API gateway in front of Keep, Pulse, Gate, Kibo and the Governed Database, with Firelock running your agents and functions and an audit trail behind every call.
Sovereign Stack
What kind of platform Kilimanjaro is — the integrated layer above sovereign-cloud substrate where data, security, control, compute, and identity compose under one customer-controllable boundary; the four-persona claim no existing category meets first-class without compromise.
Identity-Aware Kernel
Gate as the platform's hardened ingress and structural identity decision — the two consumption paths (Standalone and Native), cryptographically verified tokens, identity-provider federation, MFA, and the handoff to authorisation.
Governed Database
The operational data engine where governance — audit, data-residency, access, and provable erasure — is a property of the substrate, enforced structurally at the engine layer rather than assembled from application logic. The Forensic Identity loop, the four pillars, and the auditable-and-erasable reconciliation that is the category's genuine innovation.
Data architecture
How the project is the isolation unit, how three Postgres schema families segregate user data from platform internals from extensions, and how collections are queried through a single chainable surface.
Unified Policy
One JSON-policy language for attribute-based access control (ABAC) and policy-based access control (PBAC) compiles to row-level security on collections, access-control on storage, gates for irreversible actions, and Maker-Checker auto-approval predicates — a single authoring surface where every layer reads the same expressions.
Custody architecture
The custody architecture as an architectural decision — Platform-Managed, SKR (Secure Key Release, the integrity mode), BYOK (Bring Your Own Key), and HYOK (Hold Your Own Key). SKR is a hardened-PM overlay, not a step toward sovereignty. BYOK and HYOK are the sovereignty modes. Climb without code change because the SDK call surface is identical across all modes.
Extensions
How an extension is deployed and secured. It runs in Firelock, and everything it sends out passes through one audited channel to the Decision Oracle, the Credentials Oracle and the egress allow-list.
Agentic compute
How agentic workloads run on Kilimanjaro — the compute model, how per-project compute budgets bound cost, the four Trailblazer-class extensions, and where agents end and human operators begin.