Roadmap
Three maturity states, one commitment boundary
Current POC, coming next, and design-partner roadmap are deliberately distinct. No roadmap item carries a delivery date.
Promotion requires evidence and approval; ordering is not a contractual commitment.
Maturity
Capability, status, and the promotion boundary
- Available for POC
Platform Core
Core
Promotion boundary Maintain verified policy, role, and event-record scope.
- Available for POC
GenAI Prompt DLP
Sentry
Promotion boundary Evaluate deterministic detection; endpoint capture remains simulated.
- Coming next
AI Usage Observability
Cartographer
Promotion boundary Prove live-source integration, coverage, and completeness.
- Design-partner roadmap
Email & Channel DLP
Postmaster
Promotion boundary Validate workflow, first connector, and acceptance criteria.
- Design-partner roadmap
Private SOC Copilot
Analyst
Promotion boundary Define human review, model boundary, and evaluation corpus.
- Design-partner roadmap
Security Log Intelligence
Correlator
Promotion boundary Define source contract, findings, and evaluation method.
- Design-partner roadmap
AI Application Security
Reviewer
Promotion boundary Define review workflow and approved evidence.
- Design-partner roadmap
Data & Identity Security
Steward
Promotion boundary Define governed sources, access boundary, and outcomes.
- Design-partner roadmap
AI Governance & Compliance
Scribe
Promotion boundary Define approved report evidence and review ownership.
- Design-partner roadmap
Threat, Phishing & Malware Intelligence
Forager
Promotion boundary Define local analysis boundary and ground truth.
Bring evidence to the roadmap
A design-partner discussion starts with a real workflow, acceptance criteria, dependencies, and an accountable owner.