What is PlaylogiQ

PlaylogiQ CRM Gamification Hub is an enterprise, multi-tenant CRM + Gamification SaaS platform for the iGaming industry. It lets operators manage players, run omnichannel campaigns, and deliver gamified experiences — positioned alongside products like FastTrack, Smartico, and Solitics.

What it does

• Player CRM — a 360° view of every player: profile, financial snapshot, event/session/transaction timelines, lifecycle stage, consent, ownership.
• Segmentation — dynamic, rule-based segments with live preview, plus static segments with manual membership; real-time membership reconciliation.
• Campaigns & journeys — omnichannel campaigns (email, SMS, Telegram, WhatsApp, push, in-app) and a visual journey automation builder.
• Gamification — levels, missions, badges, tournaments, leaderboards, points and currencies.
• Analytics — KPIs, revenue, retention/churn, engagement, cohorts, forecasting, and a customizable dashboard.
• Player portal — a player-facing app with real gamification, an in-app inbox, and web-push.

Principles

1. Multi-tenant by design. Every table carries tenant_id (and brand_id); isolation is enforced in the database with Row-Level Security, not just in application code.
2. API-first. All business logic is exposed via the versioned REST API. The dashboard uses the same primitives.
3. Event-driven. Player actions flow in as events → a background worker derives stats and drives gamification, segmentation, and lifecycle.
4. Append-only streams. Event and balance-transaction streams are never updated or deleted — they are the source of truth.
5. Type-safe & self-hosted. TypeScript end to end; the whole stack runs on your own infrastructure.

The stack in one glance

The reference deployment

The platform runs as one Docker Compose stack on a single server (part of the LogiQDesk suite on logiqdesk.com). The full stack — Caddy, the four apps, the worker, Redis, and a self-hosted Supabase (Postgres, Auth, Realtime, Storage, PostgREST, Kong, Studio) — is defined in infra/docker-compose.yml. Each app is served on its own subdomain:

See Background jobs and the infra/ directory for the deployment details.

Continue to Modules for what each area does, or Tenants & brands for the isolation model.