Licensed operator
You run the casino and want original content under your own brand, not the same catalogue as every competitor.
Who this is for
A slot of your own is not for everyone. Four buyer types get value here; the rest we send to a partner instead of selling them something they cannot use.
Platform or aggregator
You distribute content to operators and need an engine you can build and certify your own titles on.
Studio or brand
You have the art and the audience, but not the math, the RNG or the back office behind a slot.
Investor or new venture
You are building a games business and want an asset with the math and the trust layer inside — not a reseller account.
When this is the wrong product
- You have no gambling licence and no licensed operator partner, and you plan to take real money anyway.
- You need a sportsbook or a full casino platform with payments, KYC and a licence included.
- You need a guaranteed revenue number before you start.
- You want the RTP adjusted per player, the fairness check removed, or someone else’s brand in the skin.
- You only need an affiliate funnel or traffic arbitrage — an aggregator or network fits better.
What “your own” actually means
“Own” is the whole product, so it has to be defined in a table, not an adjective. This is the split we commit to in the contract.
| Layer | Yours | Ours |
|---|---|---|
| Domain | Your domain and brand; we never put our logo on your lobby. | Nothing after handover. |
| Server and hosting | Your infrastructure, your cloud account, your backups — or managed by us if you prefer. | Deployment support and the build artefacts. |
| Brand and art | Logo, palette, characters, promo; we produce the pack to your brief. | Production pipeline and source files of the art we make for you. |
| Source code and IP | An engine licence gives you the right to run and use the engine on your side; source access, escrow or transfer is a separate written term. | Ownership of the engine, the math core and the art pipeline stays with us unless the contract says otherwise. |
| Math and RTP target | The RTP and volatility band you need for your market, agreed in writing. | Calibration, simulation report and the fail-gate that blocks a release. |
| Player and round data | Players, rounds, sessions, reports — in your database when you host. | No access after handover unless you ask for support. |
| Back office | Full operator account: players, rounds, themes, RTP reports, leads. | Training and documentation. |
| API | Wallet, rounds, theme config, jackpot and reporting endpoints. | Versioned contract and support during integration. |
| Updates and new themes | You decide what ships and when. | Engine updates and the content subscription, if you take it. |
What is in the box
One server-side core powers every theme, so a new game is a new skin and a new configuration — not a new codebase.
Server-side math
Weighted reels, line and ways evaluation, cascade and cluster resolution, free spins, gamble, buy-bonus. Written and tested on the server, not in the browser.
Provably-fair by default
Commit-reveal with HMAC-SHA256 and no modulo bias. The server publishes the seed hash up front and reveals the seed after the round, so any spin can be recomputed independently.
Five mechanics on one core
Classic lines and ways, Megaways, cascades with multipliers up to ×5, cluster pays, plus buy-bonus and a three-tier progressive jackpot.
Operator back office
Players, rounds, sessions, theme management, RTP reports and the lead inbox — the same panel we run our own showcase on.
Integration API
Auth, wallet debit and credit, round start and result, theme configuration, jackpot contribution and reporting. A documented contract, versioned.
Brand pack
Symbols, background, lobby tile, promo art and logo treatment. The parametric pipeline produces a full visual package in days, and every theme is reviewed by a human before it is wired to the engine.
12 locales, server-rendered
English, Russian, Spanish, Portuguese, German, French, Italian, Dutch, Polish, Turkish, Japanese, Chinese — each with its own URL and hreflang, rendered in HTML before JavaScript runs.
Analytics and game moments
Round logs, RTP and volatility reports, near-miss and big-win markers, engagement heatmaps and A/B of mechanics.
How a project moves
Five steps, each with a deliverable you can check. Nothing starts on a handshake and nothing is invoiced without a written scope.
Discovery call
45 minutesYour market, licence, platform, hosting, languages and the target RTP. We tell you on the call whether we are the right supplier.
Written scope and quote
2–3 business daysWhat is included, what is not, the tier, the dates and the responsible person on each side.
Brand pack and theme
5–10 working days per theme · planning estimateArt brief, symbol set, background, lobby tile and promo. You review at two checkpoints before anything is wired.
Integration and staging
2–4 weeks · depends on your platformAPI keys, wallet calls, round flow, theme config, back office accounts, test rounds and a fairness re-check on staging.
Launch and handover
1 weekGo-live checklist, release notes, operator training, documentation and a named support channel.
Timelines are planning estimates for a standard integration; the contract fixes dates after the scope is signed. Custom mechanics or a new math model add a separate calibration stage.
The price ladder
Open prices, same as on the pitch page. You should be able to budget before the first call — the ranges are market anchors, not a public offer.
Design pack
$150–600
Art only, for a team that already has a theme and an engine.
- Symbol set or promo art
- Two revision rounds
- Source files
Not included: Math, engine, back office, integration.
Full theme
$800–3,000
A complete visual theme, ready to run on the engine.
- Symbols, background, lobby tile, promo
- RTP/volatility configuration
- Simulation report
Not included: Engine licence, hosting, integration.
Skin licence
$3,000–8,000
One published game white-labelled to your brand, on your domain.
- Brand skin and configuration
- Deployment assistance
- Back office access for one operator
Not included: Engine source, custom mechanics, multi-brand resale.
Engine licence
$15,000–40,000 + $1,000–4,000/month
Your own titles on our engine, on your server, with the API and the back office.
- Engine, back office and API
- Updates and new mechanics
- Integration support
- Fixes and security patches
Not included: Licence, KYC/AML, payments, lab certification, traffic.
Managed platform
from $40,000 + revenue share
You want the platform, the content flow and the operations run with you.
- Engine and platform operations
- Content pipeline
- Analytics and reporting
- Named support
Not included: Licence in your name, payments, your marketing spend.
Add-ons
- Content subscription — $2,000–6,000/month for an agreed number of themes or localisations.
- Sales and support automation — $1,000–4,000 setup + $300–1,500/month for site and Telegram bots, email replies, B2B FAQ and CRM pipeline.
- Analytics — $500–2,000 one-off report, or $500–2,500/month for a live dashboard.
Never included
- A gambling licence in your name — only you, or your licensed operator, can hold it.
- KYC, AML, responsible-gambling tooling and payment processing.
- Laboratory certification of the RNG or the game for your regulator — we support the process, we do not pay for it or invent it.
- Traffic, media buying and affiliate operations.
- A revenue guarantee. RTP is a long-run expectation and a calibration target, never a promise to a player or to you.
When a discount is fair — and when it is not
- Fair: a larger committed volume, a longer term paid up front, or a smaller scope (skin instead of engine, your hosting instead of ours).
- Fair: a public case study with your permission — traded as value, not given away.
- Not fair: “it is just expensive” with no scope change, a self-imposed deadline, or a discount requested before the demo.
What we can prove today
No client logos we cannot show and no revenue numbers we cannot source. These are the claims you can check yourself, with the method attached.
95.2%
RTP on 1,000,000 spins
Calibration run of the showcase theme. The fail-gate blocks a release when the simulated RTP drifts outside the agreed band.
1 call
to verify any round
Commit-reveal with HMAC-SHA256 and no modulo bias. After the round the seed is revealed and the outcome is recomputed via /api/fair/verify.
5
mechanics on one core
Lines and ways, Megaways, cascades up to ×5, clusters, buy-bonus — plus a three-tier progressive jackpot.
days
for a new theme
Parametric art pipeline: a full visual package generated and reviewed, then wired to the engine — days per theme, not months.
12
locales, server-rendered
Each locale has its own URL and hreflang cluster; text is in the HTML, not rendered by the browser.
$0
to check us first
Live demo, public design gallery and this page. No form wall before the proof.
The 15-minute demo
Every demo follows the same agenda, so a buyer can compare suppliers on the same script. The demo runs on virtual credits and shows the 18+ notice on screen.
- 0:00–2:00
Playback
We repeat your answers: market, licence, platform, RTP band. You correct us before we show anything.
- 2:00–5:00
Your brand on screen
The theme in your colours, your lobby tile, your promo — not a generic screenshot.
- 5:00–8:00
The mechanics you asked for
Cascades, Megaways, buy-bonus or the jackpot, whichever the brief needs.
- 8:00–10:00
You verify a round
You spin, copy the seed and recompute the outcome through the public verify endpoint. We do not do it for you.
- 10:00–12:00
Back office and API
Rounds, RTP report, theme management, then the wallet and round endpoints on one screen.
- 12:00–14:00
The tier and the scope
One recommended tier, what is in it, what is not, and the next date.
- 14:00–15:00
A dated next step
Technical call, written scope or a pilot theme — with a date, not “we will think about it”.
The script
This is the working part of the playbook: how we qualify, what we say to each buyer type, how we answer the twelve objections that actually come up, and how we follow up without pressure. It is public on purpose — a buyer who reads it knows exactly what to expect from us.
Qualification questions
- Which of the four buyer types are you — operator, platform, studio or investor?
- Do you hold a gambling licence, and in which jurisdiction? If not, who is the licensed operator taking the money?
- Does your regulator require lab certification of the RNG or the game, and who pays for it?
- Does the game plug into your existing platform through an API, or do you need the platform too?
- Where does it run: your server, your cloud, or managed by us?
- Which markets and languages do you launch with?
- How many themes on day one, and how many per month after that?
- What is your launch date, and what is holding it?
- Which budget band is realistic: under $10k, $15–40k, or $40k+?
- Who signs, and who else is in the decision — CTO, compliance, investor?
- Who do you work with today, and what is not working?
- Who owns KYC, responsible gambling and payments? (The correct answer is: the operator.)
Red flags that pause or end the conversation
- “We will get the licence later” or “everyone works grey”.
- A request to tune the RTP per player, hide the seed or disable the fairness check.
- A demand for a guaranteed return before launch.
- Player money accepted outside a licensed operator, or anonymous payments with no licence.
- Sportsbook-only or “just give us an aggregator feed” — a different supplier fits better.
- “Free pilot, then real money immediately.”
- Fake reviews, borrowed brands in the skin, or a competitor’s art.
- No decision-maker and no date — that is not a rejection, it is a nurture status.
Talk tracks by buyer type
Licensed operator
You run the casino and the licence.
- Pain
- The catalogue looks like everyone else’s, the brand dissolves into a shared lobby, and a third-party provider controls your roadmap.
- Say
- “The game runs under your brand, on your domain, on your server.”
- “A theme is a new skin and a configuration, so it ships in days, not quarters.”
- “Round history and RTP reports live in your back office, not in someone else’s cabinet.”
- Proof
- A theme already prepared in their palette, a live round verified through the public endpoint, and the RTP simulation report.
- Next step
- Technical call with their CTO on API and hosting, then a written scope for a skin or engine licence.
Platform or aggregator
You distribute to operators.
- Pain
- You need exclusive content or an engine your clients can build on, without hiring a math team.
- Say
- “Engine licence: the engine, the API and the back office run on your side.”
- “You release themes under your own operators’ brands.”
- “The content pipeline gives you ten to thirty themes or localisations a week.”
- Proof
- Published themes with live demos, the API contract, and the RTP fail-gate as a quality control.
- Next step
- Integration call and a one-theme pilot in their staging environment.
Studio or brand
You bring the art and the audience.
- Pain
- Beautiful art with no math, no RNG and no back office is a prototype, not a product.
- Say
- “The math and the engine are ours; the design is yours.”
- “Your art goes through the same pipeline that produces our themes.”
- “If your team is the bottleneck, take the content subscription.”
- Proof
- Mechanics list, calibration report and a pilot theme built from their own art.
- Next step
- Engine licence plus one pilot theme, reviewed at two art checkpoints.
Investor or new venture
You are funding a games business.
- Pain
- A reseller account is not an asset; a regulator or a buyer will ask what is actually owned.
- Say
- “The math core and the theme pipeline are the asset. The licence is the boundary of the model, not a gap in it.”
- “Real money only moves through a licensed operator.”
- “We will not forecast your revenue; we will show you the cost structure and the open prices.”
- Proof
- Calibration method, provably-fair implementation, open price ladder and this page’s “when it does not work” block.
- Next step
- Technical due-diligence session; financials only from real data, never from projections.
Affiliate or traffic owner
You have traffic; you want your own product.
- Pain
- Traffic rented to someone else’s brand leaves you with no asset and no data.
- Say
- “Your own game brand is possible, but player money still goes through a licensed operator.”
- “We can help you structure that link instead of routing around it.”
- Proof
- Demo on virtual credits, design gallery, and a whiteboard of the funnel with the licensed partner in it.
- Next step
- If there is no operator: nurture with a requirements list. If there is: a three-way call. Usually a skin licence or a design pack.
Objections and the answers that work
“It is expensive.”
“Compared with what: renting someone else’s content, or building your own engine? The prices are open. You can start with a theme at $800–3,000 or a skin licence at $3,000–8,000 and test the quality before a large commitment.”
“Why own it if renting works?”
“Renting gives you the same game as everyone else. Owning gives you the brand, the domain and the data. If the brand is not the point, an aggregator is honestly a better buy — and we will say so.”
“What about the licence?”
“Real money only moves through a licensed operator in its jurisdiction. We supply technology; we do not route around licensing. We will check your regulator’s certification requirements on the call and tell you what we have and what we do not.”
“How do I know the math is fair?”
“Commit-reveal on HMAC-SHA256 with no modulo bias. The seed is revealed after the round and the outcome is recomputed. Let us do it together in the demo — you spin, you verify.”
“How long does it take?”
“A theme takes days. Integration depends on your platform; we name the date after the scope, not before.”
“What support do we get?”
“Engine updates and fixes are part of the monthly licence. Channels and response times are written into the contract — we do not quote an SLA we have not signed.”
“Are we locked in?”
“Your domain, your server, an API integration, and the round data in your database when you host. What you need to receive on exit is written into the agreement.”
“We already work with X.”
“We are not asking you to replace them. Start with one branded theme next to X and compare it on your own numbers.”
“We only need content.”
“Then skip the engine: a design pack at $150–600, a full theme at $800–3,000, or a content subscription at $2,000–6,000 a month.”
“Can you do it cheaper?”
“Yes, by changing the scope: fewer themes, skin instead of engine, your hosting. Not by discounting the same scope. Prepayment or a longer term is a different conversation.”
“Who are your clients?”
“We do not publish client names without permission and we do not invent them. What you can check today: the live demo, the verify endpoint, the published themes and a technical call with the developer.”
“What if you disappear?”
“With an engine licence the game runs on your server. Continuity terms — access, handover, escrow — are negotiable and are written into the contract, not promised in a chat.”
“Do you guarantee RTP or revenue?”
“We calibrate RTP and prove it by simulation. We guarantee neither a player’s result nor your revenue — anyone who does is selling you something else.”
“Can you do it without a licence, on crypto?”
“No. That is the line we do not cross.”
Follow-up cadence
| D | Channel | Action |
|---|---|---|
| D0, within 2 business hours | Reply to the request and offer two call slots. | |
| D1 | Messenger they chose | One short reminder with the demo link. |
| D0 after the demo | Recap: what was shown, the recommended tier, open questions, next date. | |
| D3 | Messenger | Answer the question left open, with a demo link or a screenshot. |
| D7 | Give value: a new theme or their palette applied to a skin. | |
| D14 | The closing note: “open, postponed, or not a fit?” | |
| After | Consent only | A monthly theme digest. A refusal closes the sequence. |
One touch per 48 hours, maximum. A “no” ends the sequence; it does not move it to another channel.
Three templates
Email · first reply
Subject: Your own slot game under {brand} — reply to your request
Hi {name}, thanks for the request.
In one line: Luxoreel licenses the slot engine, the math and the design studio. The game runs on your domain and your server, under your brand; real-money play is accepted only by a licensed operator.
So we do not waste your time — two questions: (1) which licence or jurisdiction, (2) does the game plug into your platform through an API, or do you need the platform too?
The demo opens right now: {demo link}. A 15-minute call: {calendar link}.
Messenger
{name}, quick note from Luxoreel
Hi {name}, {manager} from Luxoreel — I replied to your request by email.
If this channel is easier: which jurisdiction are you in, and what launch date are you working to?
Demo, no sign-up: {demo link}.
Email · after the demo
Subject: Demo recap and the next step
Hi {name}, thanks for your time.
What you saw: the theme in your brand, a round verified through the public endpoint, the back office with rounds and the RTP report.
Recommended tier: {tier} at {price range}. Included: {…}. Not included: licence, payments, KYC/AML, traffic.
Open questions: {…} — answers by {date}.
Next step: {technical call / written scope / pilot theme} on {date}. Does that work?
Metrics that tell you whether the script works
Every number below comes from CRM fields, not from memory. If a metric cannot be computed, fix the CRM before changing the script.
| Metric | How to compute |
|---|---|
| Qualified-lead rate | Leads with a licence or a licensed partner and a fitting tier, divided by all leads. Split by source. |
| Time to first reply | Median hours from the request to the first outbound message. |
| Request → demo | Share of requests that reach a booked demo. |
| Demo attendance | Demos held divided by booked demos whose date has passed — no-shows and travel are recorded separately. |
| Demo → proposal | Share of demos followed by a written scope within 48 hours. |
| Proposal → signed | Win rate by tier, with the loss reason recorded. |
| Cycle length | Median days from request to signature, per tier. |
| Discount share | Deals with a discount, and the average discount — rising without a scope change is a warning. |
| Self-verified demos | Share of demos where the buyer ran the verify endpoint themselves. |
| Loss reasons | Top five, by field — the input for the next edit of this page and the FAQ. |
| Assistant-sourced leads | “How did you find us” plus the referrer — the practical AEO check. |
Why this script is not the 2020 template
The answer is the first paragraph
What it is, who it is for, the licence boundary and 18+ are in the first lines — not after a brand story.
Written to be quoted
Short claims with a number and a method (“95.2% on 1,000,000 spins”), one-paragraph FAQ answers, and a block that says when the product does not fit. Assistants cite that; they skip adjectives.
Structured data, not decoration
Service and offers with price ranges, FAQPage, HowTo for the process, BreadcrumbList and Organization — so the page is machine-readable, not only readable.
Proof the buyer runs, not proof we claim
The verify endpoint is the demo. A buyer who recomputes a round has already done the technical due diligence.
Open prices and honest exclusions
Ranges plus a “never included” list remove the two reasons B2B deals stall: unknown budget and a surprise invoice.
No pressure mechanics
No countdowns, no fake scarcity, a capped cadence and a “no” that ends the sequence. Qualification protects the buyer’s time as much as ours.
When this does not work
Read this before you buy. It is cheaper than discovering it during integration.
- Without a licence — yours or a licensed operator’s — real-money play is not possible, and we will not help route around it.
- A great game does not create traffic. If nobody sees the lobby, the launch fails for a marketing reason, not an engineering one.
- RTP is a long-run expectation, not a promise for a session. High volatility is a feature of the product, not a defect to fix on request.
- A custom math model or new mechanics need their own calibration and take longer than a skin. Expect a separate stage and a separate quote.
- Lab certification is per jurisdiction. We support the process with documentation and simulation reports; the certificate is issued to you by the lab.
- If you need payments, KYC and the licence in one contract, you need a full platform provider — not an engine supplier.
Where the numbers come from
Each claim on this page has a method attached, and the method is something you can run yourself. These are the primary surfaces to check before a call.
- Live demo with the verify panel →Spin a round, copy the server seed and recompute the outcome with /api/fair/verify.
- Specification →Engine mechanics, round flow and the API surface as a written document.
- Published themes →Games that are actually live, with their RTP and mechanics.
- Design gallery →Production art at the sizes we ship.
- Open price list →The same tiers, published on the partner page.
Claims here are dated. If a number is wrong or out of date, send the link and what you checked through the form — we correct the page and change the date. Nothing is edited silently.
Frequently asked questions
Can I really run the game on my own server?
Yes. The engine, the back office and the API can be deployed on your infrastructure, with your own database and backups. Managed hosting is optional, not mandatory.
Do I get the source code?
An engine licence covers deployment and use of the engine on your side; source-code access, escrow or full transfer is a separate commercial term and is written into the contract. A skin licence does not include the engine source.
What does it cost to start?
The smallest paid step is a design pack at $150–600; a full theme is $800–3,000; a skin licence is $3,000–8,000. An engine licence starts at $15,000 plus a monthly fee. The price ladder above lists what each tier includes and excludes.
How fast can we launch?
A theme takes 5–10 working days. Integration takes 2–4 weeks depending on your platform; the contract fixes the date after the scope is signed.
Is the game provably fair?
Yes — commit-reveal with HMAC-SHA256 and no modulo bias. The server commits to a seed hash before play, reveals the seed after the round, and anyone can recompute the outcome through the public verify endpoint.
Can I change the RTP?
You choose the target RTP and volatility band for your market and it is calibrated by simulation with a fail-gate. You cannot change the RTP per player or per session — that would break the fairness model.
Do you provide the gambling licence?
No. A licence is held by you or by your licensed operator in its jurisdiction. We provide technology, documentation and simulation reports for certification.
Which languages are supported?
Twelve: English, Russian, Spanish, Portuguese, German, French, Italian, Dutch, Polish, Turkish, Japanese and Chinese. Each has its own URL and hreflang; content is server-rendered.
Can I see it before paying?
Yes. The live demo, the public design gallery and the verify endpoint are open with no sign-up. The demo runs on virtual credits; 18+.
What happens if we stop working together?
Continuity is a contract term: what you keep, how access and handover work, and whether escrow applies. With an engine licence the game already runs on your server, which limits the exposure.
Start with the demo, not with a contract
Send the two facts we need — your licence or jurisdiction, and whether the game plugs into your platform or needs one. You will get a written answer with a tier and a date, or an honest “this is not us”.
Demo and showcase run on virtual credits: no real money is accepted or paid out. Real-money play is operated only by licensed operators in their own jurisdictions. 18+. Prices are market anchors, not a public offer.