Skip to content

Vendor Orchestration

Definition

Vendor orchestration routes verification requests across multiple eKYC vendors based on rules — optimizing for cost, accuracy, speed, and reliability through multi-vendor strategies.

Orchestration Patterns

graph TD
    A[Verification Request] --> B{Orchestration Router}

    B -->|Primary vendor| C[Vendor A<br/>Jumio]
    B -->|Fallback| D[Vendor B<br/>Onfido]
    B -->|Cost-optimized| E[Vendor C<br/>HyperVerge]
    B -->|A/B testing| F[Split traffic 50/50]

    C -->|Failure/timeout| D
    D -->|Failure/timeout| E

    C & D & E --> G[Normalized Result]

Routing Strategies

Strategy How It Works Benefit
Primary + fallback Route to primary; on failure, try secondary High availability
Best-of-breed Different vendors for different capabilities Highest accuracy per component
Cost-optimized Route to cheapest vendor that meets quality threshold Lower cost
Geographic Route based on document country of origin Best coverage
A/B testing Split traffic to compare vendor performance Data-driven vendor selection
Waterfall Try vendors in sequence until one passes Maximize approval rate

Key Takeaways

Summary

  • Orchestration avoids vendor lock-in and provides redundancy
  • Best-of-breed routing (e.g., Vendor A for docs + Vendor B for liveness) maximizes quality
  • Cost optimization can reduce per-verification cost by 20-40%
  • Orchestration platforms: Alloy, Persona, Sardine, Unit21