Partners
Partnership begins with a named role, qualification boundary, responsibilities, and a reviewable next step—not a logo wall or implied endorsement.
No organisations are presented as partners, customers, resellers, operators, or endorsers without written approval.
Bring a real workflow, acceptance criteria, and an accountable product owner. Roadmap participation informs discovery; it does not create a delivery date or product commitment.
Suitable for one of the seven design-partner roadmap directions.
Define approved test cases for Platform Core and GenAI Prompt DLP, then inspect results and limitations inside a controlled evaluation.
Current scope: Core + Sentry available for POC.
Channel, implementation, and support roles require separate validation of custody, access, data residency, tenant isolation, and escalation responsibilities.
No partner-operated or multi-tenant capability is claimed.
Any future programme should name territory, qualification, support boundary, security responsibilities, and approval status in writing before public representation.
We will clarify the intended relationship and current product boundary before describing any public partnership.
