Intelligence at the edge.
Secured to the core.
Enkidu builds on-device AI and zero-trust security for systems that can’t wait for the cloud — real-time inference and hardened defence, on one stack.
Two programmes. One stack.
Long description
Four layers. At the foundation, Ekur, the shared technology stack, holds four capabilities: Anshar (zoning & observability), Kittu (trust assurance), Nusku (fleet control), Shedu (security control plane). Above it sit two programmes — Baru, the trusted intelligence-fusion platform, and Nabu, the trusted investigation and discovery platform. Above them sit the sector implementations: under Baru, Enlil for Defence, Lamassu for Urban and Public Safety, and Ninkarrak for Medical, in development; under Nabu, Dinanu for Legal and Misharu for Law Enforcement, in development. Massartu, for Intelligence and in development, spans both programmes and is drawn as two separate boxes — a Baru-side fusion box and a Nabu-side discovery box — held apart by a human-held gap.
Built for the edge that matters
From the mine face to the operating theatre, Enkidu runs where the network can’t reach.
Six verbs, one of them human.
Sense
Ingest signal from sensors, networks and devices, in real time.
Fuse
Many sources into one picture, each keeping its provenance.
Reason
Investigate, cite and draft; every claim traced to its source.
Assure
Verify each step against policy and evidence before it proceeds.
Commit
A person or deterministic code turns the proposal into an effect.
Release
Record what was known, what changed, who handled it and what left.
Ekur — one stack beneath both programmes.
Every Enkidu system runs on Ekur, one shared technology stack.
Anshar
What is this operation, and where are its boundaries?
Kittu
May this step proceed, and why should anyone believe the result?
Nusku
What runs where, under whose authority, and how does it stay that way, connected or not?
Shedu
Who is every principal, and can anything be read, forged, replayed or tampered with?
Models propose; deterministic code or humans commit.
The boundary is architectural, not a matter of policy or good intentions. Inference can suggest; only deterministic code or a person can commit a change.
Sovereign operation, connected or not.
A site keeps its own picture when the link drops, and reconciles when it returns. Nothing waits on a network that may not be there.
