You are reading the documentation for v1.3.0. The current release is v1.4.0.

Staged for 1.4.0

Both of these have shipped code in 1.3.0 and neither is ready to use. They are
here because the controller-side work landed this cycle and we would rather stage
the console against it now than build it all in one jump later — but treat them
as groundwork, not capability.

Capacity-tier session licensing

[controller] The controller gained capacity licensing in v1.3.0. The free
tier is capped at 1,000 concurrent sessions; a signed capacity licence raises the
cap to a per-customer limit and applies immediately on activation. Licensing
gates capacity only, never function — a missing, expired or tampered licence
reverts to the free-tier cap rather than blocking operation. GET /bng/health
sessions.max reflects the active cap. Activation requires a TPM 2.0 device;
the free tier requires neither a licence nor a TPM.

Activation is done on the box with quantum-license-fingerprint,
quantum-license-install and quantum-license-status.

[console] A Licensing page exists and shows the capacity in force. It cannot
yet operate activation — see Known issues. The evaluation appliance ships a
vTPM (state stripped at export, so each import seeds its own identity) so the
flow can be exercised there once the console side completes.

Nothing here changes what a 1.3.0 box does. Without a licence — which is
every box today — the free tier applies exactly as before.

Local CDR / usage records

[controller] Durable per-subscriber usage records, the local-AAA analogue of
RADIUS accounting, persisted on the box for operators who bill by usage.

[console] A Usage Records page lists them with CSV download and an
Acknowledge & prune action that permanently removes what it consumes —
download before acknowledging.

Marked a preview: records are held, downloadable and prunable, but RADIUS
accounting is not enabled in this release, so they are not produced from live
subscriber traffic. Full accounting arrives in 1.4.0.