# Kambi Group procurement pack

Review path: /review/kambi

Primary procurement model: Sportsbook platform

This is an editable procurement record, not a readiness score, contract commitment, market permission or launch approval.

## Recorded position

| Field | Current position |
|---|---|
| Named product or module records | 7 |
| Product responsibility kinds | Sportsbook · Trading & risk · Odds feed · Front-end & apps · Esports · Other |
| Recorded permission markets | Alberta · Denmark · Malta (MGA) · Michigan · New Jersey · Pennsylvania · UK (UKGC) · West Virginia |
| Recorded permission kinds | B2B supplier approval · Product / transaction approval |
| Pricing transparency | Not recorded |
| Operational history | Incident history unavailable for a complete count |
| Included deployment records | 0 |
| Included current-live deployment records | 0 |
| Interpretation boundary | These are records included in this review. Counts, zero values and empty lists do not establish absence, package inclusion, the supplying entity, market availability or a current deployment. |

## Applicable procurement scopes

| Scope | Inclusion basis |
|---|---|
| Turnkey iGaming platform | Turnkey |
| Modular PAM / API platform | PAM / API |
| Sportsbook platform | Recorded sportsbook capability |

## Product and responsibility map

| ID | Product or decision subject | Kind | State | Recorded position | Responsibility | Boundary | Accept when |
|---|---|---|---|---|---|---|---|
| product:kambi:sportsbook | Turnkey Sportsbook · Sportsbook | Sportsbook | recorded | Turnkey Sportsbook is recorded for Kambi Group as sportsbook. The record establishes the named product-to-provider relationship only. | The bet and market lifecycle assigned to the named sportsbook product, including its connected operating components. | Trading ownership, event volume, PAM inclusion, market permission, latency or operator-specific configuration. | Bet-state tests covering offer, acceptance, rejection, cash-out, cancellation, settlement, correction and resettlement. |
| product:kambi:trading-risk | Managed Trading · Trading & risk | Trading & risk | recorded | Managed Trading is recorded for Kambi Group as trading & risk. The record establishes the named product-to-provider relationship only. | Price, limit, exposure, suspension and trader-decision controls assigned to the named module or service. | Feed independence, profitability, automatic liability protection, staffing level or market coverage. | Price-and-exposure scenarios covering limits, overrides, suspension, escalation, audit history and loss controls. |
| product:kambi:odds-feed | Odds Feed+ · Odds feed | Odds feed | recorded | Odds Feed+ is recorded for Kambi Group as odds feed. The record establishes the named product-to-provider relationship only. | Delivery of event, market, price and status data into a betting or trading system. | Trading responsibility, price quality, latency, data rights, liability management or settlement authority. | A feed contract and test pack for taxonomy, timestamps, sequencing, suspension, correction and resettlement. |
| product:kambi:front-end-apps | Front End (Shape Games) · Front-end & apps | Front-end & apps | recorded | Front End (Shape Games) is recorded for Kambi Group as front-end & apps. The record establishes the named product-to-provider relationship only. | The player-facing presentation, navigation and interaction layer for the named channel. | Backend system authority, device coverage, accessibility, security or parity between web and native clients. | A supported-browser and device matrix with accessibility, degraded-mode, session and release-rollback tests. |
| product:kambi:esports | Esports (Abios) · Esports | Esports | recorded | Esports (Abios) is recorded for Kambi Group as esports. The record establishes the named product-to-provider relationship only. | Esports event, market and bet-product handling within the named module. | Data rights, event integrity, trading ownership, market permission or the treatment of abandoned matches. | An event-to-settlement test pack covering feed identity, suspension, cancellation, correction and dispute states. |

## Five priority questions and acceptance gates

### 1. TK-02 — Prime delivery perimeter

- Procurement context: Turnkey iGaming platform
- Current state: unknown
- Recorded position: Kambi Group: PAM / core platform is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Which platform modules and third parties sit inside the supplier's accountable end-to-end service?
- Request: Product bill of materials; responsibility matrix; subcontractor register; integration ownership; escalation and service-boundary diagrams.
- Accept when: Every launch dependency has one accountable party, an interface owner, an acceptance test and a remedy without gaps between supplier and subcontractor obligations.
- Stop when: The supplier markets a turnkey service but excludes a launch-critical dependency from both delivery accountability and buyer-controlled ownership.
- Contract destination: Services, subcontractors and responsibility schedule

| Owner | Supplier response | Exception | Sign-off |
|---|---|---|---|
|  |  |  |  |

### 2. PAM-02 — Interface contract

- Procurement context: Modular PAM / API platform
- Current state: unknown
- Recorded position: Kambi Group: Headless API is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Can the PAM operate as a modular service across the required synchronous APIs, events, exports and administrative workflows?
- Request: Versioned specifications; event catalogue; idempotency and ordering rules; error model; limits; sandbox parity; deprecation policy; sample logs.
- Accept when: Buyer tests cover success, duplicate, late, out-of-order, timeout, partial-failure and version-change paths with deterministic recovery.
- Stop when: A critical state transition depends on a private manual process, undocumented interface, non-replayable event or change policy the buyer cannot test.
- Contract destination: API, event and lifecycle schedule

| Owner | Supplier response | Exception | Sign-off |
|---|---|---|---|
|  |  |  |  |

### 3. SB-04 — Feed and event integrity

- Procurement context: Sportsbook platform
- Current state: unknown
- Recorded position: Kambi Group: incident history unavailable for a complete count. This does not establish poor reliability.
- Question: How are event identity, feed conflict, latency, suspension, correction and abandonment controlled across suppliers?
- Request: Feed inventory; event mapping; freshness thresholds; conflict precedence; monitoring; suspension tests; correction workflow and audit output.
- Accept when: The system detects stale or conflicting data, suspends deterministically, records overrides and reconciles every correction to bets and balances.
- Stop when: A feed failure or event-identity conflict can continue accepting bets without a bounded automated or supervised control.
- Contract destination: Data feeds, integrity and monitoring schedule

| Owner | Supplier response | Exception | Sign-off |
|---|---|---|---|
|  |  |  |  |

### 4. TK-03 — Wallet and control authority

- Procurement context: Turnkey iGaming platform
- Current state: unknown
- Recorded position: Kambi Group: Reporting & BI is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Which system is authoritative for identity, balances, bonus liability, limits, exclusions, transaction history and regulatory reporting?
- Request: System-of-record map; wallet sequences; control precedence; reconciliation output; access model; witnessed failure and replay tests.
- Accept when: One authority is named for every state, conflict resolution is deterministic, and debit, credit, rollback, limit and exclusion tests reconcile end to end.
- Stop when: Competing systems can independently alter player eligibility or financial state without a deterministic authority, audit trail and reconciliation path.
- Contract destination: Architecture, controls and reconciliation schedules

| Owner | Supplier response | Exception | Sign-off |
|---|---|---|---|
|  |  |  |  |

### 5. TK-04 — Launch product set

- Procurement context: Turnkey iGaming platform
- Current state: unknown
- Recorded position: Kambi Group: Live casino is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Are the exact casino, live, sportsbook, bonus, CRM, fraud and reporting modules production-ready for this configuration?
- Request: Versioned module inventory; environment and market availability; configuration register; certification delta; acceptance scripts and results.
- Accept when: Every required module and substitute integration passes the buyer's exact market, version, data-flow and control tests in the proposed environment.
- Stop when: A launch-critical module is roadmap, demo-only, tied to another product version, or dependent on an integration with no accepted owner and test result.
- Contract destination: Product scope and acceptance schedule

| Owner | Supplier response | Exception | Sign-off |
|---|---|---|---|
|  |  |  |  |