One path in.
No path around.
The kernel is the part of Emeron that makes every other promise credible — a single governed execution path that every request, human or machine or AI-generated, must travel. It cannot be switched off, because there is nothing to switch to.
Watch a request
earn its answer.
Any request
UI · API · query · AI assistant — however it arrives, it arrives here.
Compiler boundary
AST · QL · EL — only governed queries and expressions ever reach your data. Raw SQL never does.
Row-level security
Only the rows this identity may see — injected into the query itself, fail-closed.
Field-level security
Only the fields this role may see — enforced everywhere, including exports and reports.
Audited result
The action, the identity, the rule that allowed it — on a tamper-evident trail.
Not policies.
Properties.
A policy is something a developer follows. A property is something the platform enforces whether anyone remembers or not. The kernel gives you properties.
One write path
Every mutation flows through the same governed pipeline — there is no side door for batch jobs, admins or integrations.
Fail-closed
Undefined access is denied access. A misconfiguration hides data — it never exposes it.
Security injected, not appended
RLS and FLS are woven into the compiled query — not filtered afterwards in application code that can forget.
Administrators audited too
Privileged actions are scoped, logged and reviewable — the trail covers the people who hold the keys.
Identical in every posture
Cloud, on-premises or air-gapped — the kernel’s guarantees are properties of the platform, not the hosting.
AI obeys it
Generated systems inherit the same enforcement — the AI engine cannot ship an ungoverned app, by construction.
Below everything.
Above nothing.
The kernel sits between every generated system and your data — the one layer nothing can route around. Definitions live in the metadata core; enforcement lives here.
The full architecture →Try to get around it.
Our favourite technical walkthrough: your security team proposes bypasses, and we show why each one dies at the boundary. Bring your hardest people.