Documentation / Security
Security begins with separation.
Rodon separates authenticated identity from provider credentials, proposed actions from approval, and isolated execution from trusted infrastructure.
Authenticated user and tenant context is established before resource access; files and durable objects remain owner-scoped.
Provider and integration credentials remain server-side and are never returned to browsers or inserted into model context by default.
Consequential actions can require explicit, narrowly scoped, single-use approval with an audit record.
Untrusted code runs in configured sandboxes, not in trusted Codex workspaces or application containers.
Background work exposes state, cancellation truth, errors, correlation, and retention rather than disappearing into a spinner.
Privilege boundaries
No silent privilege escalation.
A degraded provider, unsupported cancellation mechanism, missing isolation feature, or unavailable backend produces an explicit state. Rodon does not preserve the appearance of success by quietly choosing a more privileged path.
- No automatic fallback from Compute to Codex.
- No false “cancelled” state until termination is confirmed.
- No public provider credentials or raw internal identifiers.
- No enabled production compute backend without its required isolation controls.