100% Cloudflare

Cloudflare runtime for three production games

This lobby keeps the same AcmeToCasino visual language, but the runtime path is now Cloudflare-native. The page, the three game flows, the session state, and the read-model pipeline run on Pages, Workers, Durable Objects, D1, and KV.

In the current production scope, the surface is 100% functional for roulette, blackjack, and video poker.

Runtime
Detecting environment…
Stack
Pages + Workers + DO + D1 + KV
Pages host
API health
Checking…
Proof statement

Each button below creates a live session, launches the selected game, executes one round on the Cloudflare stack, and prints the production Worker response.

Checking Cloudflare API health...
deployed_code 100% Cloudflare stack
tactic 3 games: roulette, blackjack, video poker
Last check: --
sports_esports

Cloudflare Lobby

Lobby Status

Three games on one Cloudflare lobby

This section is the dedicated lobby for the Cloudflare deployment. The three games below run on the same session, compliance, balance, RNG, and betting foundation.

100% Functional In Production
Architecture
Roulette

Launches through the API Worker and settles through the roulette Durable Object with session and balance control on the Cloudflare path.

Blackjack

Deals, actions, and final hand resolution are maintained in the blackjack Durable Object with the same auth and compliance pipeline.

Video Poker

Draw flow and round completion run on the Cloudflare runtime, using the shared session and wallet model.

Game 01

Roulette

Roulette running with live launch, balance, RNG, bet settlement, and session-control enforcement on the Cloudflare path.

casino
Open game
Result
Idle

          
Game 02

Blackjack

Blackjack running with live deal, action handling, settlement, and the same compliance-aware session control used across the lobby.

style
Open game
Result
Idle

          
Game 03

Video Poker

Video poker running with live draw flow, round completion, balance update, and session-control enforcement on Cloudflare.

playing_cards
Open game
Result
Idle

          
hub

System Architecture — Cloudflare Edge Stack

Every layer of bet-brazil runs on Cloudflare infrastructure. No origin servers, no VPS, no Kubernetes — the entire stack is serverless edge.

devices
Browser / Player Device
Layer 1
Static HTML + JS / Tailwind / WebSocket — zero framework overhead
arrow_downward
language
Cloudflare Pages — bet-brazil.cloud-acmetocasino.com
300+ PoPs
Static assets, HTML lobbies, game clients
HTTP/3 + QUIC · Brotli compression · Automatic TLS · 0ms to nearest edge
arrow_downward
bolt
Cloudflare Workers — Edge Compute
V8 Isolates
cfgp-prod-api
/api/v1/auth · /api/v2/gal/* · /api/v1/wallet · /api/v1/compliance
cfgp-prod-backoffice
Read-model queries · Reality checks · Compliance overview
arrow_downward
account_tree
Durable Objects — Stateful Edge Storage
Strong consistency
RouletteTableDO
Spin RNG · Lightning numbers · Payout settle
BlackjackSessionDO
Deal · Hit · Stand · Double · Split
VideoPokerSessionDO
Hand · Hold · Draw · Paytable
PlayerSessionDO
JWT · Reality check · Self-exclusion state
WalletSessionDO
Balance · Bet debit · Win credit · Audit log
arrow_downward
database
Edge Data Layer
Globally replicated
D1
Read models · Stats
KV
Sessions · Config
R2
Audit rounds
Queues
Event stream
vs. Traditional Stack (new.acmetocasino.com)

The same product would traditionally require: Nginx + FastAPI/Go microservices + PostgreSQL + Redis + Kafka KRaft + K8s orchestration, running on dedicated hosts in 2-3 regions. This Cloudflare stack replaces all of it — zero origin servers, global distribution out of the box, compliance (SIGAP reality checks, reality-check polling) runs at the edge via Durable Object methods, and deployment is a single wrangler deploy.

hub

Why This Counts

Frontend
Cloudflare Pages

This UI is served directly by Cloudflare Pages on the `cfgp*` hostnames.

Gameplay
Workers + DO

Each action runs against stateful Workers infrastructure and returns a real production response.

Read Models
D1 + Backoffice

The same Cloudflare-side sessions and rounds feed the monitoring data exposed elsewhere in the platform.

Deployment
100% Cloudflare

Frontend, gameplay, session state, and read models are all running on the Cloudflare stack for this proof, and the three production games are fully operational.