Evenfire is an intelligence layer platform for running LLM agents that take real actions, on your infrastructure
UI Surfaces
evenfire's control plane is a set of clerum.io CRDs and APIs; humans never
touch that plane directly. Three UIs sit in front of it, each built for a
different person and each restricted to a different slice of the backend: the
Control UI governs the fleet, the Desktop App is how end users drive their
agents, and the Profile UI is the invited member's front door.
Which surface is for me?
| Persona | Surface | Talks to | Cannot reach |
|---|---|---|---|
| Platform admin | Control UI | control-api → CRDs, secrets, usage |
rpc-proxy, agent runtime |
| End user | Desktop App | external-rest-api (session, scoped tokens), rpc-proxy (agents) |
control-api |
| Invited member | Profile UI | external-rest-api |
control-api, rpc-proxy |
| Channel user (Telegram/Slack/Email) | no UI — the chat app they already have | channel-reader |
everything else |
Invitation signup no longer requires deploying anything extra: self-hosted
control-api can send the invitation email via evenfire's shared registration
hub in hosted mode — see Member invitations on
self-hosted. The Desktop App's
own handoff step still calls member-registration-service directly, which is
not in this repo — see the
member-registration-service gap
for what still works without it.
How the surfaces are wired
flowchart LR
ADM([Platform admin]) --> CU["control-ui<br/>(console)"]
USR([End user]) --> DA["desktop-app<br/>(client)"]
MEM([Invited member]) --> PU["profile-ui"]
CU --> CAPI["control-api"]
CAPI --> CRD[("clerum.io CRDs")]
DA --> ERA["external-rest-api"]
DA --> RP["rpc-proxy<br/>(scoped JWTs)"]
PU --> ERA
RP --> MH["mcp-host<br/>(agent runtime)"]
ERA -. "mints short-lived<br/>scoped RPC tokens via" .-> CAPI
Why this split matters
The Desktop App never holds a control-api service token. It authenticates
through external-rest-api, which mints a short-lived, scope-narrowed RPC
access token, and the app can only reach rpc-proxy with it (source:
desktop-app/README.md § Security Model). The Control UI is the inverse: it
reaches control-api and nothing else, and every dashboard page sits behind
an admin login — it is not an open dashboard (source: control-ui/README.md
§ Authentication). Neither surface can act as the other: an end user's
Desktop App session cannot reach secrets, cost records, or the admin control
plane — its only CRD read is the access-checked WorkflowRecipe passthrough —
and an admin's Control UI session cannot invoke agents through rpc-proxy.
Where the surfaces are not the answer
Channel users — people talking to an agent over Telegram, Slack, or email —
never touch any of these UIs. Their messages reach the platform through
channel-reader, and when a tool call needs a human decision, the approval
arrives right in that same conversation: a reply command (/approve /
/deny) on any channel, plus inline Approve/Deny buttons on Telegram and
Slack. See Configure approvals.
Next
- Control UI — the admin console
- Desktop App — the end-user client
- Profile UI — the invited member's front door