TreeCasino

A gaming platform must join identity, player and administrator authorization, external game-provider operations, wallet transfers, and immutable financial records without exposing service credentials or identity tokens to browser code. Those boundaries become especially important when provider outcomes are delayed or uncertain.

The platform uses a React frontend and a server-side authentication boundary backed by independently containerized Go services. PostgreSQL records application and workflow state, Keycloak controls identity, TigerBeetle remains authoritative for financial accounts and transfers, and durable idempotency and reconciliation records protect provider and wallet operations.

The current platform foundation brings together a React/Nginx frontend and five Go services, with public, player, wallet, and administrator interfaces represented. Provider catalog, game-launch, wallet, balance, and transaction-processing paths are implemented alongside ordered database migrations and broad backend workflow tests. The product remains in active development, so public impact claims are intentionally limited to implemented capabilities.