EKKA DEVELOPER GUIDE
AI workflows with governance built in¶
An agent is the AI equivalent of a human expert. It holds plans: the things that expert knows how to do, in the order they belong in. You write the plans. EKKA runs them in your own environment and proves what happened.
Every action an agent takes is authorized before it happens and signed after. You can check the record yourself, offline, on the machine that produced it.
EKKA is an AI workflow platform with governance built in. Experts write plans anyone can run, and every action is authorized first and proven after. Gates check each action, grants say who may do what, and receipts record what happened.
Governance is built into how your agent runs. Every allowed action comes back with a signed receipt you can verify offline. Anything without a Grant stops before any I/O (before anything is read, sent or run), and that decision is recorded too.
Private prompt templates and step results stay in your environment, and EKKA's records hold signed digests of them. Plan definitions and the inputs you submit do reach EKKA, and your chosen AI model sees the prompt it is sent. What leaves your machine lists each one, with the command that checks it.
Get started¶
-
Build a governed AI application →
Five acts, about fifteen minutes: get a runtime you control, meet your agent, give it a job, point it at your own API, then verify the proof.
-
Multi-step plans and schedules →
Several governed steps in order, then the same plan on a schedule. A timer is not a less-governed path.
-
The four words that are EKKA: Gate, Grant, Gate Token, and Receipt, plus agents, plans, and the Enclave: what you build, and how EKKA governs it.
Governance and proof¶
-
The principles your organization writes down to govern its AI agents, kept immutable and versioned with a fingerprint anyone can check. You write the words. EKKA supplies the courtroom.
-
A rule EKKA checks before a plan runs: office hours, a spend ceiling, a rate limit. Every rule watches before it blocks, so you see what it would have stopped before it stops anything.
-
One operation, slowed right down: refused with no Grant, authorized, allowed, and returned as signed proof.
-
Nothing moves without permission, and every claim on the page ships with the command that proves it. Grants, deny before I/O, what stays on your machine, and proof you verify offline.
-
What the signed audit chain proves, how to read it, and how to verify it yourself, offline.
-
Field by field: what EKKA receives, what stays on your machine, and where your AI model reads your data.
Build with EKKA¶
-
A folder on your own disk that is the agent's memory, a plan that adds to it on a schedule, and a weekly memo written with a prompt that stays in your Enclave. Our flagship worked example.
-
Work written once and called from any plan in one step. A version is never rewritten, and nothing you write reaches your organization until a person accepts it.
-
Any HTTP API, one operation at a time. Slack, Sentry, and Jira are in the catalog; your own goes in beside them.
Run it in production¶
-
An Enclave that keeps working when the laptop is closed.
-
Developer includes 1,000 runs a month, and no card. On EKKA Enterprise, each governed operation is one cent.
-
Every command you'll use, from
ekka logintoekka receipts verify.
Evaluating EKKA for a team?
This site is written for people building agents. The governance model, the trust story and how EKKA fits an organization live on ekka.ai.