Compare the catalogue you can document and operate—not the catalogue advertised in a sales presentation. Our recommended purchasing sequence is permission first, relevant coverage second, tested delivery third, then total operating cost.
This month’s selection combines a dated aggregation announcement with current commercial documentation and standing regulatory checks. It does not imply that every item was announced in October.
1. Does another major aggregation deal improve your demo shortlist?
It creates a qualification lead, not a publisher licence. On 15 October 2026, EveryMatrix announced an aggregation agreement with Stake across regulated markets. The announcement describes a library exceeding 45,000 games across several categories, including live casino and table games—not 45,000 slot demos for independent publishers. It does not establish your website’s downstream demo rights. (everymatrix.com)
Buyer action: before commissioning integration work, ask whether the supplier serves independent demo-only publishers, which titles it can authorise for the intended audience, and what minimum commercial commitment applies.
2. What does a published demo-content subscription cost?
Slots Launch provides a useful price reference, but not a complete procurement budget. Its page displayed the following monthly plans when checked on 27 October 2026. The page defines a request as a game load and says plans support unlimited websites. (slotslaunch.com)
| Plan | Displayed monthly price | Included requests per month |
|---|---|---|
| Mars | $10 | 1,000 |
| Venus | $25 | 5,000 |
| Neptune | $45 | 12,000 |
| Saturn | $115 | 35,000 |
Supplier-published snapshot, not a negotiated quote. Confirm billing currency, taxes, quota treatment and additional-usage terms before budgeting. Platform-level site allowances do not resolve every underlying title’s rights or territorial restrictions. (slotslaunch.com)
Desk cost model: compare twelve-month supplier charges, setup, hosting, integration, maintenance, permission administration and exit work. Calculate a monthly cost per usable, authorised game only after defining and evidencing the denominator. Keep unresolved eligibility visible rather than assigning it a favourable assumption.
3. Can affiliates publish SlotCatalog API data?
The public evidence requires clarification rather than a categorical yes or no. SlotCatalog’s publicly accessible API commercial PDF says its data should not be published on affiliate resources. However, its Canada-facing About page invites affiliates and operators to discuss API data partnerships and integration options. (slotcatalog.com)
Buyer action: request current, product-specific terms that identify permitted fields, public display, domains, territories, attribution and post-termination use. Do not assume the PDF governs every newer arrangement—or that an invitation to discuss a partnership grants publication rights. The PDF’s current contractual status remains unconfirmed.
4. Is your catalogue import publishing too much?
Review the import rules before trusting the feed. Slots Launch documents a published filter but says its default response includes both published and unpublished games; it also provides an upcoming filter. Its API is intended for synchronising records into a local database rather than serving every visitor page load. (docs.slotslaunch.com)
Buyer action: ask engineering to demonstrate the actual publication logic. Maintain separate states for a catalogue record, an editorial page, permission evidence and observed launch availability. A supplier’s publication flag should not automatically make a game “approved” in your CMS.
5. Which holiday releases merit sourcing work now?
Use the studio roadmap to open conversations, not promise coverage. Pragmatic Play’s 24 September announcement placed Sugar Megarush in November and named Sweet Bonanza Xmas 2500 among its forthcoming releases. It also described further POP titles. These are supplier roadmap statements, not confirmed independent US demo deployments. (pragmaticplay.com)
Buyer action: rank requests against your editorial calendar. For every priority title, request the exact game identifier, configuration evidence, approved assets and supported launch route before scheduling a playable review.
6. Does a multi-site group need different licensing terms?
At least some suppliers explicitly distinguish single-domain and multi-domain rights. MarketJS says its standard HTML5 game licence covers one domain and offers custom multi-domain arrangements. It also distinguishes fixed-fee delivery of compiled files from subscription delivery of hosted links. (marketjs.com)
Buyer action: list production domains, staging environments and proposed delivery methods in the sourcing brief. Treat original HTML5 games as a separate content route; do not assume they replace the branded studio titles required by your reviews.
7. Is children’s privacy a future deadline or an existing review item?
The main compliance date for the amended COPPA Rule was 22 April 2026—not a forthcoming 2027 deadline. The Federal Register identifies that date for most requirements, with specified safe-harbour provisions treated separately. (govinfo.gov)
COPPA applicability depends on factors including child-directed services collecting personal information and actual knowledge of collection from children under 13 on general-audience services. FTC guidance also addresses collection through third parties. (ftc.gov)
Buyer action: have a privacy adviser assess audience, presentation and embedded data collection. Do not treat a “free demo” label as a substitute for that assessment.