# GR8 Tech procurement pack

Review path: /review/gr8-tech

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 · Player account management · Affiliate system · Game aggregator · Payments · Reporting & BI |
| Recorded permission markets | Not confirmed |
| Recorded permission kinds | Not confirmed |
| 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 |
| Casino game aggregator | Game aggregator |
| White-label operating platform | White-label |

## Product and responsibility map

| ID | Product or decision subject | Kind | State | Recorded position | Responsibility | Boundary | Accept when |
|---|---|---|---|---|---|---|---|
| product:gr8-tech:sportsbook | ULTIM8 Sportsbook · Sportsbook | Sportsbook | recorded | ULTIM8 Sportsbook is recorded for GR8 Tech 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:gr8-tech:trading-risk | Managed Trading Services · Trading & risk | Trading & risk | recorded | Managed Trading Services is recorded for GR8 Tech 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:gr8-tech:player-account-management | PAM & Seamless Wallet · Player account management | Player account management | recorded | PAM & Seamless Wallet is recorded for GR8 Tech as player account management. The record establishes the named product-to-provider relationship only. | Player-account identity, lifecycle, authentication, profile state and the account services assigned to the PAM. | Wallet authority, KYC coverage, bonus ownership, omnichannel continuity or inclusion of every adjacent service. | An account-state and data-authority model with registration, restriction, closure, recovery, audit and migration tests. |
| product:gr8-tech:affiliate-system | Aff.Tech · Affiliate system | Affiliate system | recorded | Aff.Tech is recorded for GR8 Tech as affiliate system. The record establishes the named product-to-provider relationship only. | Partner attribution, account structure, commission logic and partner reporting. | Tracking accuracy, payment entitlement, traffic compliance or the treatment of reversals and closed accounts. | Attribution and commission reconciliation cases covering adjustments, reversals, disputes and partner closure. |
| product:gr8-tech:game-aggregator | Infinite Casino Aggregation · Game aggregator | Game aggregator | recorded | Infinite Casino Aggregation is recorded for GR8 Tech as game aggregator. The record establishes the named product-to-provider relationship only. | The integration and routing layer between an operator platform and multiple game-content connections. | A current title count, commercial entitlement, certification, market availability or one uniform integration path. | A supplier-title-market route matrix with launch, rollback, round-state and reconciliation acceptance. |

## Five priority questions and acceptance gates

### 1. TK-01 — Permission chain

- Procurement context: Turnkey iGaming platform
- Current state: unknown
- Recorded position: GR8 Tech: no active credential relationship is recorded for this profile. This is not a finding that permission is absent; confirm the exact entity, product and market route before award.
- Question: Can the exact supplier entity, product and operating arrangement support every proposed market and vertical?
- Request: Current authority records; entity and product map; operator dependencies; term dates; approval and change-control plan.
- Accept when: Each launch entity, product and market maps to a current permission or to a buyer-owned approval action with an accountable owner and stop condition.
- Stop when: Any launch-critical entity, product or permission route remains assumed, belongs to an unconnected group company, or cannot be completed before the corresponding launch gate.
- Contract destination: Regulatory responsibility and conditions schedule

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

### 2. PAM-04 — Cross-supplier controls

- Procurement context: Modular PAM / API platform
- Current state: unknown
- Recorded position: GR8 Tech: Anti-fraud is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Do limits, exclusions, AML actions, fraud decisions and responsible-gambling controls propagate across every connected product?
- Request: Control precedence; event timing; fail-closed rules; product acknowledgements; exception queues; audit output; multi-product test results.
- Accept when: A control change reaches and is enforced by every required product within an agreed bound, with deterministic treatment during dependency failure.
- Stop when: A launch product can accept activity after a mandatory player restriction because propagation, acknowledgement or fail-closed behaviour is unresolved.
- Contract destination: Player-protection and financial-crime control schedule

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

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

- Procurement context: Sportsbook platform
- Current state: unknown
- Recorded position: GR8 Tech: 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. AGG-06 — Commercial chain

- Procurement context: Casino game aggregator
- Current state: unknown
- Recorded position: GR8 Tech: commercial terms are not recorded for this profile. This does not imply a price level.
- Question: Are aggregator fees, studio charges, minimums, jackpots, promotional tools, certification, data and exit treatment comparable?
- Request: Per-studio and platform rate card; calculation basis; minimums; pass-throughs; excluded tools; content removal; data retention; direct-integration exit plan.
- Accept when: Every scenario reconciles invoice logic to wallet and game data, while content continuity, data access and transition rights survive termination.
- Stop when: A material studio charge, calculation basis, minimum, liability, content-removal consequence or exit restriction remains undefined.
- Contract destination: Content charges, settlement and exit schedules

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

### 5. WL-03 — Market and brand perimeter

- Procurement context: White-label operating platform
- Current state: unknown
- Recorded position: GR8 Tech: no bounded deployment record is included in this review. This does not mean that the provider has no deployments.
- Question: Are domain, app, brand, product, language, payment, marketing and geographic boundaries approved and technically enforced?
- Request: Brand-market matrix; domain and app inventory; product eligibility; geo rules; payment routes; marketing approvals; release and change controls.
- Accept when: Only approved combinations can be configured or exposed, and every change requires the correct supplier, buyer and regulatory approvals.
- Stop when: A brand can accept players, payments or gameplay outside its approved entity, market, product or distribution boundary.
- Contract destination: Brand, territory, product and distribution schedule

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