Partners
Build and deliver with the DebugInit ecosystem.
Partner with DebugInit across implementation, industry expertise, cloud, infrastructure, models, integrations and customer success.
Public claims must match implemented controls and verified operational evidence.
Overview
This page is for organisations considering delivering, extending or reselling alongside us, and for customers asking who else is involved in their engagement.
The ecosystem is deliberately small and deliberately explicit. Where a partner is involved in your engagement, you are told which one and what they are accountable for.
Capabilities
Implementation partners
Industry and process specialists
Cloud and infrastructure partners
AI model and tooling providers
Integration partners
Security and compliance specialists
Training and adoption partners
Referral and strategic alliances
Evidence and documentation
Each item below is published here when it exists, with its scope, its date and who produced it. Nothing on this list is claimed today.
- pendingArchitecture and data-flow notes
- pendingPolicies, with their scope and review dates
- pendingThird-party test and audit summaries
- pendingSubprocessor list, with location and purpose
- pendingCompleted security questionnaires
- pendingService status and incident history
Shared responsibility
Where the boundary sits. Agreed before an engagement rather than discovered during one.
| Area | DebugInit | You |
|---|---|---|
| Delivery | We remain accountable for the engagement | One relationship to hold accountable, not several |
| Partner work | We define scope and quality gates | Visibility of who is doing what, on request |
| Third-party software | We state what we depend on | Accepting those terms where they reach you |
| Data | We define what a partner may access | Approving that access before it is granted |
Scroll the table sideways to see every column.
Procurement information
Deployment options, support terms, ownership and exit rights, data location, subcontractors and contract documents are provided during evaluation, scoped to the engagement you are considering.
Where your review requires evidence we cannot yet provide, we will say so in writing rather than answer around it. That is a more useful basis for a decision than a confident questionnaire.
Bring your review to us
Send the architecture question, the security questionnaire or the procurement constraint you have to satisfy, and we will answer against what is actually implemented.