Company
How implementation, referral and technology partnerships are intended to work for the Baobyte AML Suite — and, plainly, the fact that no partner has yet been appointed.
Programme design
These are not tiers of the same relationship. They involve different work, different accreditation and — in one case — a data-protection assessment before anything is signed.
Consultancies and systems integrators that deliver a Baobyte installation end to end: discovery, source-system mapping, rule and risk-model configuration, data migration, user acceptance testing and go-live. The work is substantial — transaction mapping and idempotency semantics alone are a real workstream — so this track expects demonstrated competence rather than a logo exchange.
Advisers, compliance consultancies and industry bodies that introduce institutions for which the platform is a genuine fit. A referral track only works if the referrer understands what the product does not do, so this one is deliberately paired with the same training the implementation track uses.
Providers of identity verification, sanctions, politically-exposed-person and adverse-media data, and core banking or payment platforms the suite ingests from. Each integration is built against the provider adapter specification, which requires explicit timeout and failure semantics — a provider that cannot distinguish “no match” from “did not answer” cannot be integrated.
Directory
Empty, and the reasons each track is not yet open are recorded rather than glossed.
Placeholder — no partner has been appointed in any track, and the accreditation criteria, commercial terms and data-protection assessments for each track have not been decided. Replace with sourced, approved content before this page is made public.
| Track | What the partner does | Status | Outstanding |
|---|---|---|---|
| Implementation | Delivery of installations, configuration and go-live support. | Not established | TODO — accreditation criteria, training requirement and commercial terms undecided |
| Referral | Introductions to institutions the platform suits. | Not established | TODO — referral terms, attribution rules and conflict-of-interest policy undecided |
| Technology and data | Identity, screening, core banking and payment integrations. | Not established | TODO — adapter certification process, data-protection assessment and subprocessor determination undecided |
Working with us
Written now, while it is a design rather than a negotiation, so that the terms are not invented per deal later.
Competency evidence, not a certificate mill. The platform ships a role-based curriculum with demonstrated-competency criteria per persona — an implementation consultant should be able to replay a source batch and reconcile the accepted, duplicate and quarantined totals, not merely have attended a session. The same assessments would gate accreditation.
No access to customer tenants by default. A partner works in the institution’s tenant under the institution’s own user administration, with the institution’s permissions and the institution’s audit trail. Support impersonation is time-bound, tenant-scoped, reason-coded and visible to the tenant; it is not a partner access route.
Honest scoping. The implementation work an institution actually faces includes source-system field mapping, clock and currency rules, duplicate and correction semantics, reconciliation reporting, key escrow rehearsal and a restore drill. A partner that scopes a deployment without those is scoping a failure.
Partner enquiries
The programme is not open yet, but the conversation is worth having early — particularly for integration partners, where the data-protection assessment takes longer than the engineering.