Security

Who holds what.

Daevix is an execution-time control plane. The parts that matter for a risk review are where sovereign data lives, what the platform can see, and what happens when something is refused.

Enclave · sovereignSovereign data stays in enclaves inside your own cluster. It never transits the controlplane — the controlplane carries metadata and desired state only.
Attribution

Agents hold no keys.

An agent never authenticates. Every action is attributed from signals below the workload, and any credential it needs is presented by the gateway on its behalf — never handed to it.

Mediation

Default-deny, every call.

All egress leaves through a gateway the agent does not control. A call outside policy is refused at the boundary and written to the record. Refusal is the platform working, not an outage.

Custody

You can hold the key.

Key custody runs a spectrum from platform-managed to fully bring-your-own, across two trust domains that do not cross. At the far end, the operator holds that key and decrypt is fail-closed without it.

What the controlplane can see.

The honest numbers here are structural, not benchmarks. Daevix is alpha and has no production fleet to quote.

ThingControlplaneYour enclave
Agent prompts and outputs never local only
Audit records never sealed, local
Data-encryption keys never you can hold them
Agent names and desired state metadata pulled
Enclave registration one identity attested

Put your agents under governance.

Daevix is alpha and open source. Read the source, run it against one agent you already have in production, and tell us which question it still cannot answer.

AGPLv3 · CLA required for contributions