A stack you can read, and a release process you can plan around.
Your risk is a black box: a vendor platform you cannot inspect, cannot extend and cannot leave. GameBridge is a modular Go core plus an AI worker, on PostgreSQL and Redis, behind Cloudflare on AWS, with a documented release process and a What's New feed for every change. We will also tell you what it is not.
Six things you would ask a vendor's engineers.
Modular core plus AI worker
One Go API gateway with domain packages, plus a separate worker for GameBridge Studios generation and the AI media loop. Not microservices, not Kubernetes, and we do not pretend otherwise.
Release process
Releases ship once for the whole network through a fixed sequence: automated gates, database changes in a planned window, pre-open money audits, then traffic. A What's New feed in the console for every release.
Integrity in the schema
The double-entry ledger carries its integrity constraints in the database, not in application code, so no code path can post an unbalanced movement. Automated test gates run on every release.
Integrations already wired
Alea, Iconic21, Altenar, payment partners for cards, bank transfers and crypto, ID verification, in-house fraud scoring, MaxMind, SES, Twilio, Firebase, Intercom, GTM, GA4, Meta CAPI, AppsFlyer, Everflow, Cloudflare, S3 and 11 AI providers.
Realtime with an outbox
WebSocket channels for player, global and admin, with a transactional outbox behind tier-up bonuses. The live winners feed, balance sync and presence come from the same registry.
Portable configuration
JSON import and export for bonuses, banners, packages, segments, campaigns and games; .slotpack for GameBridge Studios; dry runs on packages. Move configuration between brands and environments without tickets.
What it is not, in writing.
You will find out anyway, so here it is. GameBridge is a modular core, not microservices. It runs as containers on AWS, not on Kubernetes. Observability is structured logs, health and readiness probes, CloudWatch and in-admin Engine Diagnostics, without OpenTelemetry tracing. The player app is web plus Capacitor native shells, not a PWA.
- No Kubernetes: containerized Go services with PostgreSQL and Redis behind Cloudflare
- No OpenTelemetry tracing: structured logs, health and readiness probes, CloudWatch, and Engine Diagnostics with jobs, run history, heartbeats and a dead-letter queue
- No nSure, ClickHouse or Kafka in the stack
- No Web Push yet: iOS and Android push through Firebase
Where your team plugs in.
Data and APIs
- PostgreSQL with a canonical double-entry ledger and integrity constraints in the schema
- Redis alongside PostgreSQL, both checked before traffic is accepted
- Webhook step in CRM journeys to allow-listed hosts; Everflow server-side postbacks
- Advanced Report with custom columns and CSV or XLSX, built by background report jobs
- Deep links, direct, deferred and universal, plus AppsFlyer OneLink on the native apps
Games and content
- GameBridge Studios: 22 mechanic archetypes, immutable math definitions, .slotpack export and import, import-only production mode
- Certification package per math version: PAR sheet, definition JSON, a machine certificate bound to definition hash and engine version, reproducibility.json
- 20M+ round Monte Carlo validation with hard publish gates
- Model Registry with one active model per role, canary reports and audited switches; RNG test streams for Dieharder and NIST STS
- Games catalog import with preview, per-brand exclusions and nightly category sync
What engineering leads ask.
How is it deployed?
How do upgrades work across brands?
What does realtime look like?
Is there tracing?
Where engineering goes next.
Architecture and security
How the platform is built and secured: a modular core on hardened infrastructure, safe by default.
ПодробнееIntegrations
22+ vendors already wired in, from aggregators to payments to attribution.
ПодробнееCompare: build in-house
What you would have to rebuild, and what the platform already carries: ledger, cashier, risk, CRM, console and apps.
Подробнее