Security

Control the boundaries that touch code, credentials, and durable state.

Kala separates browser identity, agent state, model credentials, workspace execution, and deployment authority rather than collapsing them into one process or token.

Workspace execution

Executors dial out to the Host. They advertise an explicit tool and sandbox boundary, and the Dashboard never talks to an Executor directly. Approval remains Runtime authority.

Durable state

Session events are persisted before they are projected as completed work. Queue acceptance, planned restart continuation, deployment receipts, and route generations have explicit durability and fencing contracts.

Credential ownership

Provider credentials and deployment secrets remain server-side. They are not embedded in the Dashboard, Session events, public evidence, screenshots, or release metadata.

Supply-chain controls

Direct dependencies are pinned, the pnpm lockfile is immutable in CI, new releases observe a cooling period, and release assets carry manifests, checksums, scans, and signed evidence.

  • Exact dependency versions and reviewed lifecycle scripts
  • Privacy, license, vulnerability, and package-boundary gates
  • Immutable release revisions and digest-pinned Private Cloud images

Report a vulnerability

Do not open a public issue containing an undisclosed vulnerability, credentials, private installation data, or customer content.

Read the security policy