Kaidera OS
Security, troubleshooting, and operations
Operate Kaidera OS safely: local access, secret handling, project boundaries, remote access, health checks, and common failure modes.
Public-safe summary of Kaidera OS security architecture, Settings guide, and operational docs.
Security posture
Kaidera OS should be treated as an operator control plane. It can dispatch workers, access project files, hold provider credentials, and write project memory. Run it on a trusted machine and expose it only through an approved access pattern.
Secrets
Provider keys and operational secrets should never be stored in source control or rendered back to the browser. Settings should show masked secret state and preserve existing secrets when non-secret fields are edited.
Local access
For local use, bind the console to localhost unless you have deliberately configured a secure remote-access path. Do not place the local console directly on the public internet.
Remote access
For VM or remote operation, use a controlled private access layer such as a VPN, authenticated tunnel, or equivalent enterprise network control. The design direction includes stronger service-to-service and hosted auth patterns for remote and managed deployments.
Project boundary checks
When behavior looks wrong, first check the selected project, workspace root, project key, worker identity, and Cortex health. Many apparent model or worker problems are actually project-boundary problems.
Common troubleshooting flow
Check the runtime from the outside in: console reachable, Cortex healthy, app database connected, provider configured, project root correct, worker route valid, dispatch mode expected, then inspect the run-state evidence.
Operational safeguards
Keep high-impact changes approval-gated. Use propose mode for new projects, review run evidence, avoid broad filesystem roots, rotate provider keys when needed, and back up project-critical Cortex and app database state.
Website context
Connect this guide back to the product story
The technology docs map links this page to the public technology narrative and helps buyers move from a capability overview into the right operating guide.
Open technology docs map →