feat: CF_LICENSE_KEY env var for product license self-validation #26

New issue

Closed

opened 2026-04-04 22:38:59 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-04-04 22:38:59 -07:00

Owner

Context

Products need a way to validate their own Heimdall license key at startup — both for self-hosters supplying a purchased key and for the CF cloud stack verifying a provisioned key.

CF_ORCH_URL is already wired in llm/router.py. CF_LICENSE_KEY is the sibling env var that lets the product authenticate itself to Heimdall without needing a per-product secrets file.

Proposed

Add CF_LICENSE_KEY env var support to circuitforge_core.config (or tiers)
Document in each product .env.example alongside CF_ORCH_URL
Wire into Heimdall /validate endpoint call at product startup (optional — graceful if absent)

Raised from

Snipe issue #17 (cf-core wiring audit). This is the remaining open item after that audit.

## Context Products need a way to validate their own Heimdall license key at startup — both for self-hosters supplying a purchased key and for the CF cloud stack verifying a provisioned key. `CF_ORCH_URL` is already wired in `llm/router.py`. `CF_LICENSE_KEY` is the sibling env var that lets the product authenticate itself to Heimdall without needing a per-product secrets file. ## Proposed - Add `CF_LICENSE_KEY` env var support to `circuitforge_core.config` (or `tiers`) - Document in each product `.env.example` alongside `CF_ORCH_URL` - Wire into Heimdall `/validate` endpoint call at product startup (optional — graceful if absent) ## Raised from Snipe issue #17 (cf-core wiring audit). This is the remaining open item after that audit.