Skip to main content
Your game server is one Cloudflare Worker in your own Cloudflare account. The dashboard deploys it through Cloudflare’s API with the access you grant when you connect Cloudflare. Its code is a release that kinematic builds; your settings come from the dashboard.

​
What you see in Cloudflare

  • A Worker named og-rgs-<casino ID> unless you chose another name, for example og-rgs-lucky-star.
  • Its address: https://og-rgs-lucky-star.<your subdomain>.workers.dev, or a hostname of your own.
  • Its Durable Objects, which hold each player’s bets, the sandbox test balances, your VRF keys and the game server’s Solana key.
  • Its variables and secrets, which the dashboard sets on every deploy.
Your game server runs and stores its data in your account, under your agreement with Cloudflare and at your cost.
Change your game server’s settings in the dashboard, not in Cloudflare. Each deploy from the dashboard replaces the Worker’s code, variables and secrets. Deleting the Worker or its Durable Objects deletes your players’ bet records and your VRF keys.

​
Settings without redeploying

The dashboard signs your settings: allowed origins, session issuer, wallet URL, currencies and limits, games, return to player, appearance and whether new bets are allowed. Your game server checks the signature, applies them and keeps the last good settings. It fetches them about once a minute, and at once when you save. Your game server refuses settings it must not apply and keeps serving with its last good ones. On the Game server page, its card notes the refusal and Check now gives the reason. It refuses:
  • settings for the other mode, until you redeploy the game server in that mode;
  • a new decimal scale for a currency it already serves, because balances and receipts stay in the scale they were made in.

​
Routes

GET /health is the address to watch from your own monitoring:

​
What it reports

Every 60 seconds your game server posts counts to the dashboard: bets, settled rounds, refusals and errors by code, wallet round trips, the newest errors, the Solana record’s state, and totals wagered and paid by game and currency. The reports carry no player names or player IDs. Kinematic keeps them for 30 days. The dashboard’s Live page reads the newest bets from your game server’s memory while you watch it. Kinematic stores no individual bets: each bet’s records stay in your game server.

​
Updates

New releases deploy to your game server automatically: the dashboard checks every 5 minutes and updates each deployed game server that has Update automatically on, in the mode it already runs, so an automatic update never switches modes. You can turn automatic updates off for a game server on the Game server page, and update it yourself with Update to and the release. A failed automatic update to the same release is retried after an hour.

​
Solana address

When it records bets, your game server generates its own Solana key and keeps it in its storage. That address signs and pays for every record and registers your VRF keys on chain. Kinematic keeps the address funded: you never fund it.