Evidence map · not an uptime leaderboard

iGaming platform reliability evidence

A provider-by-provider view of what can actually be observed: public status history, incident objects, scoped availability records, communications, and the gaps between marketing percentages and a buyer's enforceable SLA.

Open the evidence matrix Put reliability into the RFP

16 provider reliability reviews2 published histories reviewed8 profiles with scoped availability recordsDataset snapshot August 2, 2026

Public silence is not reliability evidence

“No public history located” never becomes zero incidents, 100% uptime, or proof that customers receive no private reporting. Even the UK Gambling Commission warns that its technical standards should not be used as a measure of reliability, quality, or security. See the official remote-sector guidance.

Four evidence layers

Do not collapse telemetry, history, measurement, and contract

Layer 1

Current component state

A point-in-time API or status-page state. It does not show when an event began, who was affected, or how long it lasted.

Layer 2

Incident history

Dated event objects with impact and timing. Completeness depends on the components and publication policy covered by the page.

Layer 3

Availability result

A percentage only becomes comparable with product scope, period, formula, measurement point, exclusions, and assurance.

Layer 4

Contractual SLA

The signed definition, reporting window, breach threshold, exclusions, service credits, termination rights, and dispute process.

Own review · source-scoped

Public reliability transparency matrix

A zero appears only when an incident array was explicitly recorded after reviewing a published history. “Not countable” means the project has no complete public incident population to count.

Public reliability evidence reviewed for each provider
Provider	History state	Review window	Published incident objects	Availability evidence types	Source roles checked
BetConstruct Reviewed 2026-08-02	Published history reviewed	2026-05-01 through 2026-08-02	37	first party status metric	status history, status current
EveryMatrix Reviewed 2026-08-02	Published history reviewed	2022-03-09 through 2026-08-02	0	No scoped public availability record stored	status history, status current
Aristocrat Interactive Reviewed 2026-07-14	No public history located	No countable public-history window	Not countable	No scoped public availability record stored	product page, audited report
Bragg Gaming Group Reviewed 2026-08-02	No public history located	No countable public-history window	Not countable	No scoped public availability record stored	product page
Delasport Reviewed 2026-07-14	No public history located	No countable public-history window	Not countable	No scoped public availability record stored	product page
Digitain Reviewed 2026-07-17	No public history located	No countable public-history window	Not countable	marketing claim	product page, status current
GiG (GiG Software) Reviewed 2026-07-17	No public history located	No countable public-history window	Not countable	marketing claim	product page, audited report
GR8 Tech Reviewed 2026-07-17	No public history located	No countable public-history window	Not countable	marketing claim	product page
Kambi Group Reviewed 2026-08-02	No public history located	No countable public-history window	Not countable 1 separate communication record	No scoped public availability record stored	product page, audited report, incident notice
Light & Wonder (iGaming) Reviewed 2026-08-02	No public history located	No countable public-history window	Not countable	marketing claim	status current, service level terms, audited report
NuxGame Reviewed 2026-08-02	No public history located	No countable public-history window	Not countable	marketing claim	product page
Pariplay Reviewed 2026-07-14	No public history located	No countable public-history window	Not countable	No scoped public availability record stored	product page
Playtech Reviewed 2026-08-02	No public history located	No countable public-history window	Not countable	No scoped public availability record stored	product page, audited report
Slotegrator Reviewed 2026-07-14	No public history located	No countable public-history window	Not countable 1 separate communication record	No scoped public availability record stored	product page, incident notice
Soft2Bet Reviewed 2026-08-02	No public history located	No countable public-history window	Not countable	marketing claim	product page
SOFTSWISS Reviewed 2026-08-02	No public history located	No countable public-history window	Not countable	marketing claim	product page

2 provider records currently expose an explicitly countable incident array in the project. Counts remain bounded by each review window and publication scope.

Provider-by-provider assessment and source boundary

These are not provider verdicts. Each card records what the reviewed public evidence can establish and the exact conclusion it cannot support.

BetConstruct

All unscheduled records published by the BetConstruct Statuspage across operator-facing, third-party, and internal components

BetConstruct publishes the strongest operational record in this comparison: 37 unscheduled incident records in the complete May 1 to August 2 review window, plus rolling 90-day component figures. The records span core platform, back-office, third-party provider, and internal-tool components, so the count is transparency evidence rather than a provider-to-provider failure rate; the uptime figures are first-party telemetry, not an independent audit or contractual SLA.

Limit: The incident API excludes planned maintenance and mixes core services, third-party integrations, and internal tools. Statuspage impact labels do not quantify affected operators or players, and the public telemetry provides no calculation formula, exclusions, independent assurance, SLA threshold, or contractual remedy.

Scoped availability records

99.99% over the published rolling 90-day view · first party status metric
Betting Software Products group · 2026-05-05 through 2026-08-02
Method: Rolling 90-day component percentage rendered by the official Atlassian Statuspage; its public calculation formula and exclusions are not disclosed.
vendor stated · vendor · reviewed 2026-08-02
Availability source
99.82% over the published rolling 90-day view · first party status metric
Casino Platform · 2026-05-05 through 2026-08-02
Method: Rolling 90-day component percentage rendered by the official Atlassian Statuspage; its public calculation formula and exclusions are not disclosed.
vendor stated · vendor · reviewed 2026-08-02
Availability source
99.99% over the published rolling 90-day view · first party status metric
Sportsbook · 2026-05-05 through 2026-08-02
Method: Rolling 90-day component percentage rendered by the official Atlassian Statuspage; its public calculation formula and exclusions are not disclosed.
vendor stated · vendor · reviewed 2026-08-02
Availability source
100% over the published rolling 90-day view · first party status metric
API BetConstruct · 2026-05-05 through 2026-08-02
Method: Rolling 90-day component percentage rendered by the official Atlassian Statuspage; its public calculation formula and exclusions are not disclosed.
vendor stated · vendor · reviewed 2026-08-02
Availability source
99.98% over the published rolling 90-day view · first party status metric
Payments System · 2026-05-05 through 2026-08-02
Method: Rolling 90-day component percentage rendered by the official Atlassian Statuspage; its public calculation formula and exclusions are not disclosed.
vendor stated · vendor · reviewed 2026-08-02
Availability source
99.65% over the published rolling 90-day view · first party status metric
BackOffice Panel · 2026-05-05 through 2026-08-02
Method: Rolling 90-day component percentage rendered by the official Atlassian Statuspage; its public calculation formula and exclusions are not disclosed.
vendor stated · vendor · reviewed 2026-08-02
Availability source
99.68% over the published rolling 90-day view · first party status metric
3rd Party Provider · 2026-05-05 through 2026-08-02
Method: Rolling 90-day component percentage rendered by the official Atlassian Statuspage; its public calculation formula and exclusions are not disclosed.
vendor stated · vendor · reviewed 2026-08-02
Availability source

Sources checked

status history · vendor · Public incident history reviewed for all unscheduled records in the stated window
status history · vendor · Latest-50 incident API fully covers the review window because its oldest returned record predates 2026-05-01
status current · vendor · Public component status and rolling 90-day availability figures captured on 2026-08-02
status history · vendor · Component uptime calendars reviewed for period and scope context

EveryMatrix

Public EveryMatrix status components covering CasinoEngine, GamMatrix, MoneyMatrix, OddsMatrix, and Backoffice endpoints

EveryMatrix publishes component-level status and uptime calendars, but its complete public incident history contains no incident objects. At the August 2 capture the summary API still reported a partial system outage and flagged 11 component records: eight OddsMatrix split-endpoint records plus the B3, D5, and F8 shard groups. No linked incident narrative was published, while separate unsuffixed Webapi OddsMatrix components were operational and had July 27 or July 31 updated_at values. Zero published records therefore cannot be interpreted as zero outages, provider-wide uptime, or MTTR.

Limit: Component updated_at values are not proven incident start, restoration, or state-change times, and unusually long-lived split-endpoint or shard-group states may describe disabled or legacy endpoints. The unlogged July component updates show that component timestamps are not a substitute for incident history. The public page provides no affected-customer narrative, root cause, resolution, measurement rules, provider-wide roll-up, or contractual remedy.

Sources checked

status history · vendor · All 18 available history pages were reviewed through July 17 and contained no published incidents; the current history page was rechecked through August 2 and also showed no July or August incident object
status current · vendor · August 2 component snapshot reported a partial system outage and 11 problem component records: eight OddsMatrix split-endpoint records plus B3, D5, and F8 shard groups. summary.incidents remained empty, while separate unsuffixed Webapi OddsMatrix components were operational with July 27 or July 31 updated_at values
status current · vendor · Unresolved-incident endpoint returned an empty incident array at review time
status current · vendor · Current incident-list API returned an empty incidents array at the August 2 capture; this is not proof of zero outages

Aristocrat Interactive

Aristocrat Interactive group products, including the former NeoGames, Aspire Global, BtoBet, and Pariplay businesses

No public component status history, measured availability series, or standard SLA terms were located. Aristocrat's FY2025 reporting describes technology-integration risk, cyber controls, and more demanding service-level obligations within the enlarged group, but it does not publish product uptime, incident history, or remedies.

Limit: The annual report describes controls and integration risk but provides no public control-audit report, product-level availability result, incident register, measurement rules, or breach remedy. No public history located is not evidence that no incidents occurred or that customers receive no private reporting.

Sources checked

product page · vendor · Current iGaming and sports product page reviewed for availability, incident-history, and SLA disclosures
audited report · audited-report · FY2025 group report reviewed for operational-risk, cyber-control, service-level, and assurance disclosures; its financial audit is not an uptime audit

Bragg Gaming Group

Bragg HUB and the wider Bragg platform portfolio

Bragg publishes architecture and product information but no component-level status history, measured availability series, incident register, or complete public SLA. Listed-company reporting and named deployments provide counterparty context, not operating-performance evidence.

Limit: No public history located is not evidence of zero incidents, a particular uptime level, or the absence of customer-only service reporting. Product architecture and client deployments are not substitutes for measured results.

Sources checked

product page · vendor · Current Bragg HUB page reviewed for availability, incident-history, and standard-SLA disclosures

Delasport

Delasport sportsbook, casino platform, and managed services

Delasport publishes continuous managed-service coverage and certification announcements, but no public status history, observed availability series, or complete SLA terms. ISO 27001 and GLI references concern security management or technical compliance; they do not establish uptime.

Limit: Public Delasport materials give conflicting ISO timing references and no current certificate record, status history, availability method, incident register, or contractual remedy. No public history located is not evidence of zero incidents or of absent private service reporting.

Sources checked

product page · vendor · Managed-services page reviewed for availability, incident-history, and SLA disclosures
product page · vendor · Certification announcement reviewed for assurance scope and dates; no certificate number, current surveillance record, audit result, or uptime measurement is published

Digitain

Digitain platform products, with a separate check of the Sports Data/API claim

Digitain's current Sports Data/API page simultaneously advertises a 99.99% uptime-SLA headline and a 99.9% availability SLA in its SLA section. The page does not reconcile the two targets or publish a measurement period, formula, exclusions, observed series, or remedy. The status.digitain.com endpoint could not be inspected through its Cloudflare challenge, so neither figure is platform-wide reliability evidence.

Limit: The product page does not explain whether its two SLA percentages cover different services or calculations, and supplies no public observation window or contractual mechanics. An inaccessible candidate endpoint is not a reviewed status history, and no public history located is not evidence that no incidents occurred.

Scoped availability records

99.99% uptime SLA headline · marketing claim
Sports Data/API headline card · no observation period published
vendor stated · vendor · reviewed 2026-07-17
Availability source
99.9% availability SLA (custom SLAs available) · marketing claim
Sports Data/API SLA section · no observation period published
vendor stated · vendor · reviewed 2026-07-17
Availability source

Sources checked

product page · vendor · Sports Data/API product page reviewed for its conflicting 99.99% uptime headline and 99.9% availability SLA section
status current · vendor · Candidate status endpoint returned a Cloudflare browser challenge; no public component history or incident records could be verified

GiG (GiG Software)

GiG CoreX, SportX, LogicX, DataX, and managed-service products

GiG advertises 99.9% uptime without a product boundary, observation window, formula, exclusions, independent monitoring, or public remedy. No public component status history was located, so the percentage remains a marketing claim rather than a measured provider-wide result.

Limit: Architecture, company reporting, and customer deployments do not establish measured availability. No public history located is not evidence of zero incidents or of absent customer-only service reporting.

Scoped availability records

99.9% uptime · marketing claim
Product scope not stated on the homepage · no observation period published
vendor stated · vendor · reviewed 2026-07-17
Availability source

Sources checked

product page · vendor · Current homepage reviewed for the uptime headline, component scope, public history, and SLA terms
audited report · audited-report · FY2025 report reviewed for operational availability and incident evidence; the financial audit does not audit product uptime

GR8 Tech

GR8 Tech Platform, GREAT_Turnkey, GREAT_SPORTSBOOK, GREAT_AGGREGATION, and Payment Gateway pages reviewed separately

GR8 Tech publishes product-scoped uptime figures: 99.95% for GREAT_SPORTSBOOK, 99.96% for the core Platform and Payment Gateway, and 99.99% for GREAT_AGGREGATION. GREAT_Turnkey conflicts internally by saying the product is designed for 99.96% uptime and later presenting 99.99% in its numbers section. Different figures across distinct products are not inherently contradictory, but the Turnkey pair is unreconciled. None of the pages supplies an observation period, measurement formula, sample definition, exclusions, public history, or remedy; the figures remain marketing claims and the response figures are not MTTR.

Limit: The pages do not define incident population, start and stop rules, measurement window, exclusions, or remedies. Different product figures cannot be blended into a provider-wide result, and the Turnkey page does not explain its own two different uptime figures. No public history located is not evidence of zero incidents, and 15- or 37-minute handling claims cannot be interpreted as mean time to recovery.

Scoped availability records

99.96% uptime · marketing claim
Core GR8 Tech Platform · no observation period published
vendor stated · vendor · reviewed 2026-07-17
Availability source
99.96% uptime · marketing claim
GREAT_Turnkey — design statement · no observation period published
vendor stated · vendor · reviewed 2026-07-17
Availability source
99.99% uptime · marketing claim
GREAT_Turnkey — numbers section · no observation period published
vendor stated · vendor · reviewed 2026-07-17
Availability source
99.95% uptime · marketing claim
GREAT_SPORTSBOOK · no observation period published
vendor stated · vendor · reviewed 2026-07-17
Availability source
99.96% uptime · marketing claim
GR8 Payment Gateway · no observation period published
vendor stated · vendor · reviewed 2026-07-17
Availability source
99.99% uptime · marketing claim
GREAT_AGGREGATION · no observation period published
vendor stated · vendor · reviewed 2026-07-17
Availability source

Sources checked

product page · vendor · Core Platform page reviewed for its uptime and critical-incident handling claims
product page · vendor · GREAT_Turnkey page reviewed for its internally conflicting 99.96% and 99.99% uptime claims and critical-incident handling claim
product page · vendor · GREAT_SPORTSBOOK page reviewed for its product-scoped 99.95% uptime claim and supporting measurement details
product page · vendor · Payment Gateway page reviewed for its product-scoped 99.96% uptime claim and supporting measurement details
product page · vendor · GREAT_AGGREGATION page reviewed for its product-scoped 99.99% uptime claim and supporting measurement details

Kambi Group

Kambi turnkey sportsbook and managed trading platform

Kambi's Q2 2026 report discloses credits related to unspecified operational issues in April 2026, but does not identify the affected component, partners, duration, cause, restoration time, or credit value. The same report cites a third-party World Cup uptime ranking without publishing the benchmark or methodology. No public component status history, numerical observed availability series, or complete SLA terms were located.

Limit: The Q2 report confirms that operational issues occurred but does not provide a service-level incident record. It also does not publish the Bettormetrics benchmark or methodology behind the cited World Cup uptime comparison. No public history located is not evidence of no other incidents or of absent private operator reporting.

Sources checked

product page · vendor · Turnkey sportsbook page reviewed for availability, incident-history, and SLA disclosures
audited report · audited-report · FY2025 reporting reviewed for operating-performance and incident evidence; the financial audit is not an uptime audit
incident notice · vendor · Unaudited Q2 2026 report reviewed for the disclosed April operational issues, related credits, and the externally attributed World Cup uptime claim

Light & Wonder (iGaming)

Light & Wonder iGaming systems, with the Infinity Gateway portal claim kept separate

Light & Wonder's Infinity Gateway login advertises a 99.99% uptime SLA for that partner portal, not for the whole iGaming stack. The underlying OGS SLA resource is access-controlled, and no public formula, exclusions, remedy, observed series, or incident history could be verified.

Limit: A current-status headline is not a historical observation. The 10-K's materiality disclosure does not mean no operational incidents occurred, and the private OGS page cannot support public SLA mechanics or remedies.

Scoped availability records

99.99% uptime SLA · marketing claim
Infinity Gateway partner portal only · no observation period published
vendor stated · vendor · reviewed 2026-07-17
Availability source

Sources checked

status current · vendor · Public Infinity Gateway partner-portal login reviewed for its current-status and 99.99% uptime-SLA headline
service level terms · vendor · OGS SLA resource exists but is password-protected, so target scope, formula, exclusions, and remedies are not publicly inspectable
audited report · audited-report · FY2025 Form 10-K reviewed for material cyber incidents and resilience controls; its financial and ICFR audit is not an uptime audit

NuxGame

NuxGame platform, Casino API, Sports Betting API, Sportsbook product page, and published infrastructure description

NuxGame publishes different and partly contradictory availability figures: approximately 99% for the platform on its About page, 99.9% for the Sports Betting API, and approximately 99.999% on the Casino API page. The current Sportsbook page itself uses a 99.999% headline and a 99.9% FAQ answer. The scopes differ or are not defined, and its architecture descriptions do not prove any result. No public status history, observation period, measurement method, exclusions, SLA remedy, or independent benchmark was located.

Limit: The About, Casino API, Sports Betting API, and Sportsbook figures appear in different or undefined product contexts. The Sportsbook page conflicts with itself, and none defines a period, formula, measurement point, exclusions, or remedies. Architecture can explain how availability is pursued but does not prove the published results. No public history located is not evidence of zero incidents or of absent private service reporting.

Scoped availability records

Approximately 99% platform uptime · marketing claim
Provider-wide platform scope as described on the About page · no observation period published
vendor stated · vendor · reviewed 2026-08-02
Availability source
99.9% uptime · marketing claim
Sports Betting API · no observation period published
vendor stated · vendor · reviewed 2026-08-02
Availability source
Approximately 99.999% platform uptime · marketing claim
Casino API page and product context · no observation period published
vendor stated · vendor · reviewed 2026-08-02
Availability source
99.999% headline / 99.9% FAQ · marketing claim
Sportsbook product page · no observation period published
vendor stated · vendor · reviewed 2026-08-02
Availability source

Sources checked

product page · vendor · About page reviewed for the approximately 99% platform-uptime claim and supporting measurement details
product page · vendor · Infrastructure article reviewed for architecture, monitoring, failover, and operational-result evidence
product page · vendor · Sports Betting API page reviewed for its product-scoped 99.9% uptime claim and supporting measurement details
product page · vendor · Sportsbook page reviewed for its conflicting 99.999% headline and 99.9% FAQ figures and supporting measurement details
product page · vendor · Casino API page reviewed for its approximately 99.999% platform-uptime headline and supporting measurement details

Pariplay

Pariplay Fusion aggregation platform

Pariplay publishes continuous support coverage for Fusion but no public component status history, measured availability series, incident register, response target, or complete SLA terms. Named deployments show adoption, not operating reliability.

Limit: The public page describes support availability but gives no service-result evidence or contractual mechanics. No public history located is not evidence of zero incidents or of absent private operator reporting.

Sources checked

product page · vendor · Fusion page reviewed for availability, incident-history, response-target, and SLA disclosures

Playtech

Playtech PAM and wider B2B platform services

Playtech's FY2025 reporting describes a 24/7 security operations centre, incident response, backups, and continuity testing, but no public product status history, observed availability series, or standard SLA terms. Financial and control reporting must not be treated as an uptime audit.

Limit: The annual report names control activities and audit frameworks but does not publish their reports, product scopes, results, availability periods, incident records, or SLA remedies. No public history located is not evidence of zero incidents.

Sources checked

product page · vendor · PAM page reviewed for availability, incident-history, and standard-SLA disclosures
audited report · audited-report · FY2025 report reviewed for cyber controls, continuity testing, incidents, and assurance; its financial audit does not establish product uptime or security-control effectiveness

Slotegrator

Slotegrator platform and integrated game-content delivery

No public Slotegrator status history or measured availability series was located. A dated April 2026 statement addresses AMATIC game content and says the Slotegrator platform was operating normally, but it omits event timing, affected operator or sessions, resolution, and a final root-cause analysis; it is a limited first-party communication, not an incident metric.

Limit: The statement reports Slotegrator's understanding and platform status at publication; it does not provide a complete event record or independently verified attribution. No public history located is not evidence of zero incidents.

Sources checked

product page · vendor · Platform page reviewed for availability, incident-history, and SLA disclosures
incident notice · vendor · Dated first-party statement about AMATIC game content reviewed for incident timing, impact, attribution, resolution, and root cause

Soft2Bet

Soft2Bet iGaming platform

Soft2Bet advertises 99.99% uptime for its iGaming platform and describes continuous monitoring, but no public status history, observation period, formula, exclusions, complete SLA, remedy, or independent benchmark was located. The percentage remains a scoped marketing claim.

Limit: The public percentage has no reproducible measurement method or contractual mechanics. No public history located is not evidence of zero incidents or of absent private service reporting.

Scoped availability records

99.99% uptime · marketing claim
Soft2Bet iGaming platform · no observation period published
vendor stated · vendor · reviewed 2026-08-02
Availability source

Sources checked

product page · vendor · iGaming platform page reviewed for its uptime claim, monitoring description, public history, and SLA terms

SOFTSWISS

SOFTSWISS Game Aggregator and Casino Platform reviewed as separate products

SOFTSWISS publishes different availability headlines for distinct scopes, including 99.999% for Game Aggregator and 99.99% in a Casino Platform retrospective. Its July 2026 Oracle Kubernetes Engine update documents first production casino deployments and a continuing rollout, but architecture and migration evidence do not validate either availability figure. No public status history, reproducible method, exclusions, complete SLA, remedy, or independent series was located.

Limit: Product-specific percentages do not create a provider-wide observed result or contractual promise. The Kubernetes migration describes architecture and rollout state, not an independent resilience result or measured uptime series. No public history located is not evidence of zero incidents or of absent customer-only reporting.

Scoped availability records

99.999% uptime-SLA headline · marketing claim
SOFTSWISS Game Aggregator · no observation period published
vendor stated · vendor · reviewed 2026-08-02
Availability source
99.99% uptime · marketing claim
SOFTSWISS Casino Platform retrospective · no observation period published
vendor stated · vendor · reviewed 2026-07-14
Availability source

Sources checked

product page · vendor · Current Game Aggregator page reviewed for its uptime-SLA headline and supporting terms
product page · vendor · Casino Platform retrospective reviewed for its separate availability headline and scope
product page · vendor · July 2026 production-migration update reviewed for deployment scope and whether it provides measured availability or incident evidence

Convert reliability claims into acceptance tests

Freeze the service map

Name every production component, dependency, region, environment, measurement point, and owner. Provider-wide uptime is not a test scope.

Recalculate the percentage

Obtain raw numerator, denominator, clock source, maintenance treatment, exclusions, degraded-state rules, and customer-specific calculation.

Sample incident evidence

Match detection, public notice, customer notice, impact, restoration, root cause, corrective action, and SLA report for the same events.

Exercise dependency failure

Test wallet, game, sportsbook, PSP, KYC, geolocation, feed, and cloud dependency failure plus retry, rollback, and reconciliation behaviour.

Prove recovery

Run backup restoration, regional failover, queue replay, open-round recovery, ledger reconciliation, and RTO/RPO acceptance with retained output.

Write the remedy

Attach the exact report, dispute window, service credits, chronic-breach rights, termination assistance, and evidence-access obligation to the contract.

Reliability evidence questions

Which iGaming platform has the best uptime?

The public data does not support a defensible provider-wide leaderboard. Suppliers publish different products, periods, formulas, components, exclusions, and marketing or SLA percentages. We compare transparency and evidence scope rather than blend incompatible numbers.

Does zero published incidents mean zero outages?

No. It can mean the reviewed public history contains zero incident objects in a defined window, or that no public history was available to count at all. Those are different states and remain separate on this page.

Is a status page the same as an SLA?

No. A status page is communications or telemetry. An SLA needs a service definition, measurement point and window, exclusions, breach threshold, reporting process, and remedy in the contract.

Does GLI, ISO, or regulator approval prove uptime?

No. Testing, security controls, and market approval answer different questions. They can support diligence, but they do not establish measured availability, incident recovery, or the buyer's contractual remedy.

What should a buyer test before signing?

Request component-level availability data, incident exports, maintenance treatment, synthetic and real-user measurements, recovery tests, RTO and RPO evidence, dependency mapping, communications samples, and the exact SLA formula and remedy for the proposed product and environment.

Scoring methodology Pricing evidence Research updates