Platform
SentraMind is designed for self-hosted and air-gap-capable operation. The current POC keeps deterministic detection and policy authoritative, records reviewable events, and makes every stand-in visible.
Current offer first. Future modules remain visibly separate.
Current product boundary
A verified package does not make a whole capability production-ready, and a roadmap direction never borrows the visual language of current product.
Evaluate deterministic policy, role enforcement, immutable policy versions, and a tamper-evident event record in a controlled POC.
Identity uses a development provider; evidence-sealing primitives are verified, but the live verdict pipeline does not yet invoke the sealer.
Evaluate deterministic detection and governed verdicts before an approved client submits text to an AI destination.
Endpoint interception is simulated and model classification is disabled. The browser demo is not evidence of fleet capture.
The engineering build validates normalisation and projection behaviour using synthetic scheduled-file and CEF/syslog-shaped observations.
Not in the current POC offer. Live source integration, coverage, and completeness are not proven.
| Capability | Module | Availability | Evidence boundary |
|---|---|---|---|
| Platform Core | Core | Available for POC | Identity uses a development provider; evidence-sealing primitives are verified, but the live verdict pipeline does not yet invoke the sealer. |
| GenAI Prompt DLP | Sentry | Available for POC | Endpoint interception is simulated and model classification is disabled. The browser demo is not evidence of fleet capture. |
| AI Usage Observability | Cartographer | Coming next | Not in the current POC offer. Live source integration, coverage, and completeness are not proven. |
Governed decision path
A POC decision follows a legible sequence: simulated input, deterministic detection, policy resolution, governed outcome, and an event record.
POC-POLICY-EXAMPLEPOC architecture
The overview names what current code supports and where production integrations remain acceptance criteria.
Role enforcement is implemented at POC depth through a disclosed development identity provider. Real AD, Kerberos, SPNEGO, PIV, and FIDO2 are absent.
Governed control planeThe same policy engine drives enforcement, dry run, and effective-policy explanation. Immutable versions make the applied rule set inspectable.
Deterministic decisionStored canonical events form a hash chain with signed checkpoints and can be independently verified. SIEM acknowledgement remains emulated.
Canonical eventEvidence-sealing and custody primitives are test-vector verified. The live verdict-to-sealing pipeline is incomplete and POC custody is software-based.
Evidence custodyThe same deterministic policy engine drives enforcement, dry run, and effective-policy explanation in the tested POC code.
This verifies policy consistency, not endpoint capture, production identity, model quality, rated latency, or customer deployment readiness.
Material limitations
These limitations define the evaluation boundary.
No endpoint agent or browser extension exists; capture is simulated.
The model classifier is disabled and no model-quality or language-coverage claim is permitted.
Real AD/Kerberos authentication and hardware-backed evidence custody are absent.
Rated-QPS latency, production capacity, HA, and failover have not been measured.
Runtime zero-egress is a design and acceptance objective, not a proven appliance claim.
Fit by operating need
These are paths through the same current POC, not separate products or claims of production coverage.
Test deterministic detection and policy outcomes against approved synthetic or reviewed text samples.
Current POC: Core + Sentry. Endpoint interception remains a disclosed stand-in.
Examine a self-hosted design where policy remains authoritative and model-shaped work cannot silently replace a governed decision.
Air-gap-capable design; runtime zero-egress still requires evaluation proof.
Inspect versioned policy outcomes and tamper-evident event-chain behaviour while keeping pipeline limitations explicit.
Policy and audit-chain packages are verified only at their stated scope.
Portfolio horizon
The remaining modules are design-partner roadmap directions. They do not emit live verdicts, receipts, metrics, or customer outcomes.
A private evaluation starts with architecture, data-boundary, and test-case review. It does not ask you to upload sensitive material through this public portal.