Engines for platforms that already exist

Casino, payments and CRM as standalone services. Integrate one over gRPC and events without replatforming.

Three engine modules with glowing amber cores linked to a circuit grid

The open-source game core

Casino Engine

Provider and aggregator integrations, session orchestration, betting logic, freespin mechanics and full round lifecycle. Production-grade Kotlin, released under Apache 2.0 so your team can audit it, fork it or drop it into an existing stack.

View on GitHub
  • Kotlin + Ktor, gRPC APIs
  • Apache 2.0, source on GitHub
  • Runs moonbet.casino and 2k.ua in production

The financial hub

Payment Engine

Every movement of money between the outside world and player wallets: deposits, withdrawals, approvals, refunds. Owns the operation history and emits events that analytics, CRM and bonuses consume.

  • Nine business operations, no scope creep
  • 76 provider integrations
  • Event-sourced history for every operation

Analytics and player journeys

CRM Engine

ClickHouse-backed ingestion of every player event, plus journey orchestration that reacts in real time: segments, triggers, bonuses and messages driven by actual behaviour.

  • ClickHouse analytical store
  • Real-time journey orchestration
  • Consumes events from every other engine

Built to be integrated, not adopted wholesale

No mandatory migration. Keep your platform and connect the piece you need.

gRPC contracts

Typed client libraries published per engine. Integrate from Java, Kotlin, Go, Rust or Node without guessing at payloads.

Event streams

Every engine publishes domain events over RabbitMQ. Your analytics, accounting or risk stack subscribes and stays in sync.

Deploy anywhere

Docker images run in your Kubernetes, your bare metal, or an AWS account we provision at distributor rates.

One engine can change the economics.

Tell us which part of your stack hurts. We will map the integration on a technical call.