Ekur
One stack of four capabilities beneath every Enkidu programme — and the ecosystem that keeps every implementation current inside the client’s own enclave.
Ekur is the technology stack beneath Enkidu’s two programmes. Four capabilities, one codebase, every sector. Each answers a system-level question shared across sectors. The duties stay separate by design: the component that defines a boundary, the one that verifies a crossing, the one that distributes what crosses and the one that proves who is crossing are never the same.
Enkidu builds two programmes — Baru and Nabu — on one stack, Ekur; each programme serves sectors through named implementations, and Enkidu keeps every implementation current through continuous supply.
Sector-specific work enters as artifacts: modules, personas, skills, policies and zones. The core stack stays the same.
A model produces a proposal; a deterministic committer or a person turns it into an effect. Automation only ever narrows.
The implementation runs on client hardware inside a client enclave under client roots. Publishers stay outside.
Every capability is specified for a node that may go dark or be taken.
No claim without a chain of custody. Data, models, control actions and security events enter one signed, hash-linked record.
The four capabilities are application-independent; sector-specific work is artifacts and declarations, with no change to the stack.
A fielded artifact is current or superseded, never finished.
A firewall vendor supplies an appliance once and threat definitions continuously. Ekur follows the same basic pattern. The stack and programme arrive once, customised to the client’s sector. The supply continues: model variants, modality specialists, security definitions, personas, skills, agents, tools, connectors and policies.
Nothing activates without a person, or a lane a person declared. No live channel enters the enclave. Nothing flows back unless the client chooses to contribute.
There can be multiple publishers: Enkidu first, partners such as Carleton University and the University of Waterloo under their own roots, and the client’s own pipelines. Every artifact enters the same registry, carries the same lineage and passes the same gate. The gate is the client’s. Large and frontier models such as Claude, Gemini and Microsoft Copilot, and AI-enabled services such as LexisNexis, are reached from inside the enclave under contracts the client holds. Every call is decided before it leaves.
kind of thing that ever crosses from a publisher into a client enclave — a signed bundle, verified at the node, admitted by policy, activated by a person. Source: Enkidu (S1).
Enkidu supplies the hardware with the stack, built on NVIDIA’s edge and desktop line. Jetson Orin and Jetson Thor at the node; Jetson Thor and IGX Thor at the hub; DGX Spark as the single-node reference; DGX Station and Blackwell-class systems at the centre. Two builds follow the site. Ruggedised for military, mining, agriculture and manufacturing. Non-ruggedised for pharma, education, legal and intelligence. A single node and a fleet of thousands use the same four capabilities and supply process. Model size bands are defined by the tier that runs a model.
Each capability and the ecosystem are specified in a technical paper.
Specification documents; no availability, customer or performance claims.