Eruka
BUILTWhat an agent is allowed to say. Four states, provenance, one write gate, gap detection, a review queue, MCP and REST.
Eruka →Everything Dirmacs sells runs on the same three components. The engine reaches a client through one of three services, configured per industry, never rebuilt.
What an agent is allowed to say. Four states, provenance, one write gate, gap detection, a review queue, MCP and REST.
Eruka →Agents run here. Many model providers behind one interface, tools, MCP and per-tenant metering, in a small Rust binary.
ARES →The token supply: one API for many model providers, with failover, per-tenant wallets and a ledger.
Haimdall →The control room every client system runs behind: service health, one-click deploy, logs and restarts, per-tenant usage, run cost and budget alerts.
In daily use.
The platform is configured once per industry; every product in that industry draws on the configuration instead of rebuilding it. Education is the first, with Aidulearn.
We do not describe a design as a product, and no performance number leaves the company until it reproduces on a pinned harness.
Invoiced and delivered today.
Running and hardening. No public benchmark numbers until they reproduce on a pinned harness.
A completed design, a pipeline we run for our own research, and an idea. We do not offer them, and we do not price them.
Security and governance hardening for outside tenants is the current engineering programme. Eruka for developers is invite-only until it closes.