IDSENTRASeparate authority. Explicit data movement.
IDSENTRA separates the public evaluation surface, protected operational authority, and commercial distribution control plane so each can be secured and governed according to its actual responsibility.
Public evaluation surface
Product education, trust resources, implementation guidance, and approved contact conversion.
No operational authority or protected patron/case payloads.IDSENTRA-CORE
Protected operational plane for identity verification, watchlists, alerts, cases, evidence, responsible gaming, occupancy, reporting, users, integrations, and local policy enforcement.
Operational identity and case data remains inside the protected deployment boundary.IDSENTRA-DISTRO
Commercial control plane for customer/site records, deployment identity, signed licensing, entitlements, releases, activation, and privacy-minimized health telemetry.
No patron search payloads, self-exclusion records, protected documents, or operational PII.Commercial connectivity should not become an operational single point of failure.
CORE verifies signed distribution state locally and can use a bounded cached verified lease. Exact production grace periods and policies remain deployment configuration, not public promises.
Review licensing architecture →