Kahnawake server hosting requirements oblige every licensed operator to run their main gaming equipment, game servers, and player databases inside a Kahnawà:ke-approved data centre. You cannot host the core platform on a public cloud of your choice. The Kahnawake Gaming Commission ties this hosting rule to the Client Provider Authorisation, and it applies alongside the operator licence. This guide sets out where the servers must sit and what the hosting fee actually covers. It also explains how long deployment takes, what the setup does not permit, and the technical points that stall an application.
Key takeaways
- Regulator: Kahnawake Gaming Commission (KGC), regulating interactive gaming since 1999
- Hosting rule: main servers and player data must sit in a Kahnawà:ke-approved data centre, operated by Mohawk Internet Technologies
- Authorisation: hosting runs under a Client Provider Authorisation (CPA), held alongside an Interactive Gaming Licence
- Indicative hosting cost: from a few hundred USD up to around USD 3,770 per month, plus a connection fee near USD 250 (verify with the provider)
- Scope: operators must geo-block the United States, the United Kingdom, and Canada
What the Kahnawake server hosting requirements mean
The rule is location-based. A licensed operator must place its primary gaming environment inside the Mohawk Territory of Kahnawà:ke. That means the servers that run the games and hold player accounts sit under the regulator’s direct reach. Because the equipment is on territory, the Kahnawake Gaming Commission keeps technical and legal oversight of the operation at all times.
This is a factual difference from several offshore frameworks that let operators host anywhere. Kahnawake does not. You cannot run the core platform from your own account on Amazon Web Services, Google Cloud, or Microsoft Azure. Instead, the primary environment lives at the approved data centre, and the Commission reviews the technical setup before you go live. The Commission sets out these principles in its Regulations concerning Interactive Gaming.
Why hosting sits inside the Client Provider Authorisation
Kahnawake splits the operator role from the hosting role across two permits. The Interactive Gaming Licence (IGL) lets a company run a public-facing casino, sportsbook, or poker room and accept player funds. The Client Provider Authorisation (CPA) covers the hosting of that platform inside an approved data centre. Most operators need both, because the IGL cannot go live without compliant hosting behind it.
In practice, the CPA is what pins your servers to the territory. The Kahnawake server hosting requirements run through this authorisation, so the Commission uses it to approve who hosts your equipment and how that hosting is controlled. For the internal roles the regulator expects you to appoint alongside these permits, our guide to key function holders in iGaming sets out the compliance, AML, and technical positions. You can review the full licence structure on our Kahnawake gaming licence page.
What the approved data centre provides under Kahnawake server hosting requirements
The Kahnawake server hosting requirements point to one approved facility. It is run by Mohawk Internet Technologies (MIT), which has operated a data centre on territory since 1999. Infrastructure partners such as Continent8 also provide managed connectivity into that environment. You either place your own hardware at the facility as colocation, or you rent dedicated physical servers from the provider. Both models keep the primary equipment inside the approved site.
What sits inside a hosting package varies with the size of the operation. A small casino needs less rack space, bandwidth, and storage than a multi-brand sportsbook, so the specification scales with your traffic and product mix. Before you sign, confirm the exact server hardware, rack allocation, bandwidth ceiling, and storage capacity in writing, because the headline monthly figure does not always spell these out. The provider can also quote the cost of adding capacity later, which matters once your player base grows.
Antigua applies a similar on-island rule, where the main gaming server must sit physically in the jurisdiction as part of the Antigua gaming licence application process.
Kahnawake server hosting costs beyond the monthly fee
The monthly hosting charge is only one line in the real budget. Kahnawake server hosting requirements bring several linked costs, and each runs on its own supplier and timeline. The table below sets out the components most operators budget for. Treat every figure as indicative and confirm the current price with the provider and the Commission before you commit.
| Cost item | Indicative figure (2026) |
|---|---|
| Data centre connection fee | Around USD 250, one-off |
| Monthly hosting (colocation or rented servers) | From a few hundred USD up to around USD 3,770, by scale |
| Client Provider Authorisation | Regulator fee, confirmed at application |
| RNG and platform certification | Independent lab fee, per scope |
| Bandwidth and storage scaling | Added as traffic and catalogue grow |
The certification line matters most, because operators often leave it out of a first draft. Random number generator testing is a live obligation, so a casino that adds new game studios arranges re-certification for those additions. For what the certificates need to show, our guide to RNG testing for online casino games covers the detail. The Commission accepts testing from approved laboratories, and firms such as eCOGRA handle this work.
Cloud, CDN, and disaster recovery under Kahnawake server hosting requirements
The Kahnawake server hosting requirements govern the primary environment, but they do not force every function into the data centre. Your live game servers and player database must sit at the approved facility. Secondary services can sometimes connect from outside, so operators often build a hybrid setup that links the local data centre to a public cloud for specific, non-core tasks. Confirm with the Commission and the provider which functions are allowed outside the territory before you design the architecture.
Content delivery and backups need the same planning. You cannot simply keep your preferred content delivery network, because the strategy has to work around the approved environment. Ask the provider which delivery networks integrate with the facility. For disaster recovery, check whether the operator may hold secondary or backup servers off territory, and what redundancy the data centre itself provides. Settle these points early, since they shape both the design and the cost.
How long server deployment takes
The overall Kahnawake licence commonly runs 2 to 4 months, but the Kahnawake server hosting requirements add their own steps. The headline timeline covers document review, not the days needed to provision and connect hardware. Plan the deployment as a separate track that runs alongside the application. The table below sets out a realistic sequence.
| Stage | What happens | Typical time |
|---|---|---|
| 1. Provider selection | Choose colocation or rented servers and agree the specification | 1 to 2 weeks |
| 2. Provisioning | The facility allocates rack space, power, and bandwidth | 1 to 3 weeks |
| 3. Hardware placement | Ship and install your own servers, or set up rented dedicated hardware | 1 to 4 weeks, by model |
| 4. Configuration | Configure the platform and any approved cloud connections | 2 to 4 weeks |
| 5. Technical sign-off | The Commission reviews the setup before go-live | Runs with licence review |
Colocation adds shipping and customs time, so a rented-hardware setup often deploys faster. Start the hosting track early, because a delay here holds up the whole launch. Our gaming licence acquisition timeline shows how the preparation stages connect.
What delays or rejects a hosting setup
Most technical delays trace back to the applicant, not the regulator. When you meet the Kahnawake server hosting requirements on paper but not in the build, the review stalls. The Commission checks the hosting architecture, the certification, and the data flows, and unclear answers in any of those areas slow the process. The common problems are consistent:
- An attempt to keep the primary environment on an external cloud rather than the approved facility
- Uncertified gaming software, or RNG evidence that does not cover the live catalogue
- A hosting design that does not show clear control over servers, data, and access logs
- Backup or recovery plans that ignore the territory rule
- Weak documentation of how approved cloud connections handle player data
The fix is preparation. Submit a hosting plan that places the core platform at the data centre, name your certification lab, and document every data flow. Because a clean file moves through review in fewer passes, resolve any weak point before submission rather than after. The Commission lists current authorisation holders on its permit holders register.
What the Kahnawake hosting model does not cover
State the scope plainly before you commit. The Kahnawake server hosting requirements give the regulator oversight, but the licence does not grant access to every market. Operators must geo-block the United States, the United Kingdom, and Canada, because those markets run their own regimes. The same applies to any regulated market that requires a national licence, such as several European Union states.
Local hosting inside the territory does not change that reach. It gives the regulator oversight, but it does not create market access on its own. So if your target players sit in a market that mandates a domestic licence, you add that licence alongside the Kahnawake base. When the right route depends on your budget, products, and target countries, our guide to choosing the right gaming licence sets out how cost and market reach trade off.
Is the Kahnawake hosting model right for your setup
The Kahnawake server hosting requirements suit operators who accept local hosting in exchange for regulator oversight and a recognised framework. The number that matters for planning is your full first-year hosting total once the connection fee, monthly hosting, the CPA, and certification are added, not the monthly figure alone. If you would rather keep servers under your own cloud, a different route may fit better. Our guide to the Isle of Man gaming licence application process sets out one such option. For a costed hosting and licensing plan mapped to your target markets, speak with the DD Consultus advisory team at contact@licencegaming.com or +356 99408536.
Frequently asked questions
Where must Kahnawake licensed operators host their servers?
Licensed operators must host their main gaming equipment, game servers, and player databases inside a Kahnawà:ke-approved data centre on the Mohawk Territory. This keeps the platform under the direct oversight of the Kahnawake Gaming Commission. The requirement is tied to the Client Provider Authorisation.
Do I have to use Mohawk Internet Technologies?
The approved data centre on territory is operated by Mohawk Internet Technologies, and infrastructure partners such as Continent8 provide managed connectivity into that environment. You host your primary platform through that approved facility rather than a data centre of your own choosing. Confirm the current approved providers with the Commission before you contract.
Can I use AWS, Google Cloud, or Azure with a Kahnawake licence?
Not for your primary gaming environment. The core platform and player data must sit inside the approved data centre, so you cannot run the live operation from your own public cloud account. Some secondary functions may connect from outside, but you confirm those with the Commission first.
How much does Kahnawake server hosting cost?
Indicative figures put local hosting from a few hundred USD up to around USD 3,770 per month, plus a connection fee near USD 250. The price scales with your rack space, bandwidth, and storage, so a larger operation pays more. Confirm the current tariff with the provider before you budget.
Do I need a Client Provider Authorisation as well as a gaming licence?
Yes, in most cases. The Interactive Gaming Licence lets you run the platform, and the Client Provider Authorisation covers compliant hosting inside the territory. Most operators hold both, because the operator licence cannot go live without approved hosting behind it.
How long does it take to deploy servers at the Kahnawà:ke data centre?
Deployment usually runs a few weeks once you select a provider, covering provisioning, hardware placement, and configuration. Colocation adds shipping and customs time, so renting dedicated hardware often deploys faster. Start this track early, because a hosting delay holds up the whole launch.
Can I keep backup servers outside Kahnawake?
The primary environment must stay inside the approved data centre, and backup or recovery design has to respect that rule. Whether you can hold secondary servers off territory depends on how the Commission and the provider treat those functions. Settle the disaster recovery plan with both before you build it.
Which markets does a Kahnawake licence not cover?
A Kahnawake licence requires geo-blocking of the United States, the United Kingdom, and Canada. It also does not cover regulated markets that mandate a national licence, including several European Union states. To serve one of those markets, you add its local licence alongside the Kahnawake base.