01Specification
Gaming licenses
The technical side of the application, done properly. iGaming licensing support from the people who run the platform. Regulators ask detailed questions about the system behind a licence application; we answer them with system descriptions, hosting and security evidence, RNG certification coordination and policy templates. Your legal adviser files; we make sure the technical file holds up.
- Not a law firm: we work alongside your legal adviser
- Curaçao, Anjouan, Kahnawake, MGA, Isle of Man, EU/EEA national
- Documentation pack included in turnkey projects
- Regulator follow-up questions about the platform answered in writing
Index → Licence routes · Before you apply · Timing · Turnkey · White label
02What we actually do
The parts of a licence file that are about the platform.
A gaming licence application has a corporate part, a financial part and a technical part. The technical part is ours. Everything below is delivered as documents your lawyer can attach to the application as filed.
Technical documentation and system description
Architecture, components, data flows, environments, change management and backup procedures in the format the regulator expects.
RNG and game certification coordination
Game content arrives already certified by the studios and aggregators. Where the regulator requires platform-level testing, we work with the testing lab you appoint and provide the access they need.
Hosting and data-residency evidence
Where the platform runs, who the hosting provider is, encryption, access control, logging and retention. For jurisdictions with in-country hosting rules we plan the deployment accordingly.
AML and responsible-gaming policy templates
Templates that describe what the platform actually enforces: KYC states, limits, self-exclusion, screening, suspicious-activity records. Your lawyer finalises the wording for the jurisdiction.
Regulator questions during review
Follow-up questions about the platform come back to us and are answered in writing, with your adviser copied.
Not legal advice
Corporate structuring, which licence to choose and the application itself sit with your legal adviser. We describe what each route requires of the platform so you can decide together.
03Licence routes compared
Six routes operators ask us about.
Timelines are indicative and regulator-dependent. They describe what we have seen on complete, well-prepared applications, not what any regulator commits to.
| Route | Typical timeline | Suitability | Platform requirements | Notes | Deployment |
|---|---|---|---|---|---|
| Curaçao (LOK regime) REGULATOR-DEPENDENT | 4–10 weeks indicative | Start-ups and international grey-market brands; the usual first licence | Player protection tooling, reporting access, hosted anywhere with documented controls | The new Curaçao Gaming Authority regime replaced master/sub-licences. Direct application, more documentation than before. | White label or turnkey |
| Anjouan REGULATOR-DEPENDENT | 4–10 weeks indicative | Fast, low-cost start for crypto-leaning and international brands | Standard KYC, RG and AML tooling; hosting evidence | Common partner licence for white-label launches. Limited PSP acceptance in some markets. | White label or turnkey |
| Kahnawake REGULATOR-DEPENDENT | 8–12 weeks indicative | Operators wanting a longer-established jurisdiction without an EU process | Hosting with an approved provider, certified games, defined RG controls | Well regarded by some PSPs and partners; hosting arrangements are part of the licence. | Turnkey only |
| Malta (MGA) REGULATOR-DEPENDENT | 4–6 months indicative | EU-facing operators who need bank and PSP acceptance across Europe | System audit, compliance audit after go-live, strict reporting, data and backup rules | Substantial corporate and financial requirements. Turnkey deployment; not a white-label route. | Turnkey only |
| Isle of Man REGULATOR-DEPENDENT | 3–6 months indicative | Operators prioritising reputation, player-fund protection and banking | Approved hosting, player-fund segregation evidence, certified platform components | Designated official and local presence required. Turnkey deployment. | Turnkey only |
| EU/EEA national (Estonia, Romania, others) REGULATOR-DEPENDENT | 6–12+ months indicative | Operators targeting one regulated market with its own licence | Country-specific reporting, often in-country or EU hosting, regulator data access, local RG rules | Each country differs. We have worked with Estonian and Romanian requirements; others are scoped case by case. | Turnkey only |
04Before you apply
What should be ready on your side.
Most delays in licensing are not caused by the regulator or the platform. They are caused by a file that is submitted incomplete and then goes back and forth. This is the list we go through on the first call.
Company structure
The operating entity, its jurisdiction, directors and any group companies. Some regulators require a local company or local director.
UBO documentation
Identity, source of funds and background for every ultimate beneficial owner. This is where applications most often stall.
Bank and PSP readiness
A bank account for the operating company and preliminary conversations with PSPs. Many PSPs will only onboard once the licence is issued, so start early.
Responsible-gaming and AML policies
We provide templates that match the platform; your lawyer adapts them to the jurisdiction and signs them off.
Server location decided
Some regulators require in-country or approved hosting. The decision affects architecture, cost and timeline, so it is made before deployment, not after.
Target markets and content
Which countries you will accept players from and which game studios you want. Studios restrict content per licence.
05Licensing and the implementation timeline
The licence usually sets the pace, not the platform.
The platform can be configured in weeks. The licence decides whether you launch under someone else's or wait for your own. Either way, contracts signed by third parties set the calendar date.
White label: partner licence
You operate under the licence of a partner (typically Curaçao or Anjouan). No application on your side, so the launch is driven by KYC on your company, payment onboarding and content agreements.
- Our implementation time
- 8–12 weeks from a signed agreement
- Licensing work
- KYC on your company and UBOs for the licence holder
- Sets the date
- PSP and studio contracts under the partner licence
Turnkey: your own licence
The platform is deployed under your licence, in your cloud or data centre. The licence application and the deployment run in parallel; the documentation pack is produced from the actual architecture being built.
- Our implementation time
- 6–9 months
- Licensing work
- Full technical documentation pack, certification coordination
- Sets the date
- Licence approval, your infrastructure, PSP and content contracts
06Questions
What operators ask before applying.
Licensing questions. For legal questions, bring your adviser to the call. For platform questions, book 30 minutes with us.
Book a 30-minute callDo you obtain the gaming licence for us?
Which gaming licenses can the platform run under?
How long does licensing take?
Can I launch before my own licence is approved?
What does licensing support cost?
07Get a quote
Licensing
Technical file
Tell us your route. Get the list the regulator will ask.
Tell us your route and get a list of what the regulator will ask about the platform. One form, one engineer, one business day. The reply says which documents your route needs from the platform, which are part of a turnkey project and which are quoted separately, and what should be ready on your side before filing.
- Reply within one business day, from an engineer
- Document list per route, with what is included in the project
- Your adviser copied on request
- NDA on request, no newsletters