Skip to main content
OpenCluster uses safe defaults for server addresses, local authentication, logs, telemetry, investigation limits, concurrency, retention, retries, request timeouts, and shutdown. A normal installation supplies the database, bootstrap, AI, and encryption files plus its public URL. Environment values that end in _FILE name mounted files; they never contain the credential itself. YAML settings ending in _file follow the same rule.

Minimal YAML

Pass the file with --config /etc/opencluster/opencluster.yaml or OC_CONFIG_FILE. Environment variables override YAML. Unknown YAML fields and additional documents stop startup, so misspelled configuration is never silently ignored.

Optional YAML

Local authentication is the default. oidc adds the configured provider while local Admin recovery remains available. Relay is optional and listens separately from HTTP; customer Relays initiate outbound connections and pin the configured control-plane key.

Model provider

OSS v0.1 supports deployment-level Anthropic or Z.AI credentials. Set OC_AI_PROVIDER to anthropic or zai, set OC_AI_MODEL to an exact model identifier accepted by that provider, and set OC_AI_API_KEY_FILE to the mounted credential file. Organization-level BYOK is not part of the OSS v0.1 contract. Restart the control plane, wait for /readyz, and run one bounded Investigation. Startup proves that the file is readable; only a completed Investigation proves that the selected provider and model satisfy the structured result contract. For authentication, quota, rate-limit, or unsupported-model errors, correct the provider account or model and start a new Investigation. OpenCluster sends bounded Investigation context, Tool summaries, and the structured result contract. It does not persist or expose model chain-of-thought. Review the security model and the provider’s retention, regional processing, and training terms before production use.

Environment reference

The OSS binary uses one mounted AI deployment for every Organization. The resolver keeps Organization explicit so a separate hosted composition can select managed or encrypted Organization BYOK without changing investigation behavior. This is a pre-release clean break. Existing databases and configuration from earlier builds must be recreated rather than migrated through compatibility settings. The shared HTTP server allows 10 seconds for headers, 30 seconds to read a request, 30 seconds to write a response, and 60 seconds for an idle connection. Restart after a change, then verify /healthz, /readyz, sign-in, Organization selection, Integration verification, and one bounded Investigation.