Casino CRM,
built by people who built casinos.

Anything that can send a webhook + serve a REST endpoint. The PlatformAdapter contract is documented end-to-end at docs.casinocrm.io/adapter-integration. A reference adapter (Adapter Zero) ships with the codebase as a starting template; a real-platform integration is typically a ~200-line file implementing the contract.

Every monetary amount is stored DUAL: original (player wallet currency) + base-converted (tenant reporting currency), with the FX rate locked at event time. Reports always denominate in tenant base; the player profile shows native wallet balances. Crypto is treated as another currency code with its own scale (BTC = 8 decimals, USDT = 6); FX rates are fetched hourly from CoinGecko + ECB.

Self-hosting is supported on commodity infrastructure — the full stack runs on a single mid-tier VM. Talk to us about source access — it's available case-by-case for serious operators.

Smartico and Optimove are mature, enterprise-grade platforms. They have features and integrations we don't match yet — we're new. For tier 2-3 operators they're often overpriced and over-engineered. We focus on the 80% of features tier 2-3 actually needs, deliver them well, and price for reality. If you need enterprise multi-region orchestration or 16 years of production hardening, they're the right choice. If you need casino-native CRM with a modern stack and predictable pricing, we are.

The RG feature catalogue covers self-exclusion, deposit/loss/session limits, reality checks, cooldown periods, and affordability checks. The CRM enforces locally regardless of adapter support (capability_mock pattern) — a self-excluded player is never messaged, even if the platform doesn't enforce on its side. Audit log captures every mutation; GDPR export + erasure are first-class endpoints.

Five canonical bonus types (free spins, deposit match, no-deposit, cashback, reload) with wagering multipliers, game contribution maps, expiry rules, and anti-stacking checks. The bidirectional adapter contract means the platform credits the player wallet; the CRM tracks wagering progress via wagering_events webhooks. Daily reconciliation closes any gaps from dropped webhooks.

Everything in the Growth tier — all channels, bonus engine, journeys, A/B testing, audit log, sandbox tenant. No credit card required to start. After 3 months, choose any tier or walk away.

Sandbox tenant + first segment + first journey: under an hour with the adapter contract documented. Production go-live with a real platform integration: 1-3 weeks depending on platform complexity (KYC + bonus + wallet contract). Most operators run sandbox for a week to validate flows before flipping to prod.

Postgres Row-Level Security on every tenant-scoped table. Every query carries a tenant_id context; the database refuses to return rows from another tenant even if a bug in application code asks for them. ClickHouse uses tenant_id partitioning + per-query filters. Audit log records every cross-tenant attempt.

Two founders with 40+ years combined in iGaming — slot floors, online platforms, payment integrations, retention. We built this because the tooling we always wished we had didn't exist. See the Founders section above.