Access to your brand
On launch the PWA checks the addresses and connects to a working one.
Give players an easy way in from their phone and a reason to come back. We connect a PWA to your platform: a working mirror picked on every launch, system push notifications and an interface in your brand.
A link can become unreachable, an app may be missing in the target geo, and the way back gets lost among browser tabs.
On launch the PWA checks the addresses and connects to a working one.
An icon on the home screen and its own window once installed. An extra path to iOS players where your brand has no app.
System push notifications once the user allows them: news, offers and a tap straight back into the PWA.
We prepare a pool of your brand's addresses. Domains come from you or from KIT MORU on agreed terms.
On launch the PWA receives the published list and checks which addresses are reachable from the player's network.
It opens a working address. The player connects to your platform directly; game and payment traffic never passes through KIT MORU.
The check on the phone reflects what the player's carrier lets through. If an address is blocked mid-session, the PWA needs a restart. Staying logged in across addresses is agreed separately.
Discuss integrationThe PWA is a mobile shell; casino, sports, accounts and payments come from your platform's agreed services. The integration method is chosen after a technical review.
PWA interface and branding; install flows; rotation; push; shell events.
Game content, betting, account and balance, payments and sub-agents; available APIs and permitted embedding methods.
Can provide domains; preparing, replacing and maintaining the pool is agreed in advance.
May use their own domains; provides access and a technical contact for the setup.
Setting up the chosen integration method and measurement.
Confirmed registration, deposit and bet events; authentication requirements.
We start by reviewing your platform: which modules connect through an API, permitted embedding or a redirect, and what the pilot covers.
Once the player agrees, messages appear in the system notification centre, and a tap brings them back into the PWA.
Demo notification: a new offer is waiting in the app.
Brand, platform, geo, domains and available integrations. We agree the pilot scope and success criteria.
Branding, address pool, install, push and events. We test the user journey on real phones.
We run an agreed share of traffic, measure access and returns, and decide on the full launch.
Pricing and timeline follow the platform review and the agreed scope.
No, it connects to in-house platforms and WL after a review.
You or KIT MORU, as agreed.
On the next launch the PWA checks the other addresses in the published pool.
That depends on how authentication is integrated.
Yes, when the platform shares confirmed events.
Tell us about your platform and target geo — we'll show the demo and propose a pilot.