Which game formats fit the lobby?
Start with the full catalogue, then use the focused game pages to examine format-specific player and integration questions.
Platform overview
Evaluate the whole path,
not isolated features.
A supplier decision connects product fit, wallet ownership, round handling, verification, operations and commercials. This page keeps those workstreams in one map and sends each reviewer to the detail needed for a defensible decision.
Decision map
Six questions, six accountable answers.
Each area has a separate page because a buyer should be able to share one stable URL with the responsible product, engineering, QA or commercial owner.
Where does responsibility change hands?
Map requests, wallet calls, environment boundaries, failure handling and the evidence required before production approval.
What can a reviewer reproduce?
Separate a fairness statement from the inputs, commitments and revealed values needed to verify a historical result.
What makes a build acceptable?
Agree pass criteria for contract behaviour, retries, limits, round evidence and operational ownership before launch.
What exactly is priced?
Record included scope, the billing definition, optional work, review points and change control in the commercial proposal.
Are alternatives measured equally?
Use the same evidence request and operating assumptions for every supplier instead of comparing slogans or catalogue screenshots.
A usable evaluation
Give each team a clear review boundary.
Product owners can shortlist formats through the full catalogue and the game decision library. Engineering can inspect the integration brief. QA and operations can turn the testing criteria into an acceptance plan. Compliance and technical reviewers can use the fairness review to request reproducible evidence. Commercial owners can structure a quote with the commercial policy.
The point is not to make every team read the same sales page. It is to preserve one connected decision while letting each owner assess the part they are accountable for. Open questions should stay visible until supporting evidence or contract language resolves them.
- Declare the intended audience and production environment.
- Record the exact game set and configuration being reviewed.
- Attach evidence to each technical or commercial assertion.
- Keep unresolved questions in the launch decision, not in private notes.