Layer stack · Kandev · doc-inline · balanced
Startup configuration has one clear precedence
Kandev resolves embedded defaults, the first existing configuration file, and environment variables at process start; web settings follow a separate persistent lifecycle.
Startup configuration has one clear precedence
A layer stack shows embedded profile defaults, the first existing config.yaml, environment variables as the final startup override, and the resulting backend process. Persistent web settings are shown separately in the database-backed product surface.
STARTUP SOURCES
LATER WINS
L1
Embedded defaults
production profile · built-in fallback
L2
First existing config.yaml
cwd → home → /etc/kandev · no merge
L3
Environment variables
deployment values · secrets · final override
OUT
Backend starts
read once · restart after changes
PERSISTENT PRODUCT SURFACE
WEB UI
Settings
agents · executors · workflows
SAVE
Database
STARTUP PRECEDENCE
WEB SETTINGS ARE STORED SEPARATELY