Configuration
Configuring self-hosted Radicas — the abstract contracts, module flags, and tenancy mode. A structured draft tracking Phase 5.
Draft. Self-host configuration lands with Phase 5 of the platform roadmap; this page tracks it. The contracts below are settled; the full values reference is not written yet.
Configuration contracts
The application configures against abstract contracts, never against a named provider:
OIDC_ISSUER— the OIDC issuer URL; JWTs are verified via its JWKS. Swapping identity providers means changing this value, nothing else.POSTGRES_DSN— the control-plane Postgres connection.S3_ENDPOINT— any S3-compatible object store for the bronze layer.- Key-management settings — how tenant secrets are encrypted at rest.
TENANCY_MODE— see below.
Module flags
Some modules are decided at deploy time. Billing (Stripe) is off in self-host — the module is absent from the deployment, and no runtime toggle can enable a module that was not deployed.
Tenancy mode
TENANCY_MODE=single runs the platform for one tenant while keeping the tenant column in the schema. This is deliberate: the self-host code path stays identical to the SaaS instead of forking.
To be documented
The full Helm values reference, secret management, collector tuning, and resource sizing guidance.