Providers block by geography and refuse to be embedded. GetMyGames serves the game through your own subdomain instead — every asset and every live call routed through you.
Free plan, no card required.
See how it worksProviders restrict games by the address the request comes from, and send headers that forbid embedding. From the wrong region the game simply does not load — the content is there, but unusable.
The request arrives from an address the provider does not serve, and the game never starts.
Frame-blocking headers stop the game from loading inside your page at all.
Rewriting links is not enough: the game builds new addresses while it runs, and those escape a plain proxy.
Your page embeds the game as it always did. Our script rewrites the frame address into a subdomain of your own root, and the proxy takes it from there.
Dots become hyphens, hyphens double. One wildcard record covers every host at once, so nothing is registered per game.
It matches your game iframe by CSS selector, so the game host does not matter.
The host is encoded into a single label under your root domain.
The request reaches the provider from an address you control.
Links in the markup are rewritten, and calls the game makes at runtime are intercepted in the page.
This is where a plain reverse proxy stops working. A game does not only load files listed in its markup — it builds addresses while it runs.
Markup, stylesheets, scripts and JSON are rewritten on our side, so every reference already points through the proxy.
HTML attributes · CSS url() and @import · addresses inside scripts · JSON payloads
A small script injected into the page catches the calls the game makes at runtime and routes them through the proxy too.
fetch and XHR · WebSocket · EventSource · dynamically created elements
No changes to the game, no SDK to compile, no build step. Paste the tag, and the frame is routed from the next page load.
<script src="https://sdk.getmygames.online/gs.js"
data-key="YOUR_KEY"
data-wildcard-root="getmygames.online"
data-selector="iframe.game-frame"
defer></script>
Every game open is recorded: which game, which country, and whether it succeeded. Export the raw events whenever you need them.
Illustration — figures are examples, not live data.
An open is one game launch. Assets and live traffic that follow are not counted separately.
Paid plans are confirmed manually while online payment is being connected.
No. One wildcard record covers every possible host at once, so a new game works the moment its address appears on your page.
They are proxied as well. Live connections a game opens are rewritten to run through the same subdomain.
One extra hop is added between the player and the provider. Static responses are cached, and the proxy sits close to the provider rather than the player.
A single wildcard certificate covers every game subdomain, issued and renewed automatically. There is nothing to do per game.
The key only works from the domains you list, and it is stripped from the request before it reaches the game server.
Only game opens. Assets, scripts and live traffic that follow an open are not counted.
Create an account, copy one tag, and watch the first open appear in your dashboard.
Get started