Security & trust

A deliberately separated trust model.

The public website, operational application, and distribution control plane have distinct authority boundaries. Operational patron and case data never belongs in the commercial licensing plane.

01

Operational locality

Identity, search, case, evidence, local audit, and source credentials remain with the protected deployment.

02

Commercial separation

Customers, sites, licenses, entitlements, releases, deployments, and privacy-minimized fleet telemetry are handled separately.

03

Credential discipline

Secrets and protected payloads are not intended for public surfaces, URLs, analytics, or fleet telemetry.

04

Bounded resilience

Signed license state is locally verifiable so operational availability does not depend on a continuously reachable commercial control plane.