PlaylogiQ Documentation
Welcome to the documentation for the PlaylogiQ CRM Gamification Hub — an enterprise, multi-tenant CRM + Gamification platform built for the iGaming industry.
These docs are organized by audience. Jump to the section that fits you:
Platform Overview →
What PlaylogiQ is, the modules it ships, the multi-tenant / multi-brand model, and the delivery phases. Start here for the big picture.
Operator Guides →
How to use the operator dashboard: managing players, building segments and campaigns, journeys, gamification, analytics, team & lifecycle, and settings. Written for the people who run the CRM day to day.
PAM Integration →
The technical contract for connecting a Player Account Management system (or any backend) to PlaylogiQ: authentication with brand-scoped API keys, the event ingestion API, the per-brand configurable mapping engine, the canonical event catalog, and outbound webhooks. Written for the PAM’s engineering team.
Developer Docs →
For engineers working on the platform: architecture, the monorepo, database + Row-Level Security, RBAC, background jobs, conventions, and Architecture Decision Records.
API Reference →
The full public REST surface under /api/v1, plus the machine-readable OpenAPI
spec.
The 30-second version
- Multi-tenant, multi-brand. A tenant (operator) owns one or more brands (skins). Every record is scoped to a brand; isolation is enforced in the database with Row-Level Security.
- Event-driven. Player activity flows in as events → a background worker derives stats, advances lifecycle stages, recomputes segments, and runs journeys.
- API-first. Everything the dashboard does is available over the versioned REST API. A PAM pushes data in; nothing is required back out.
- Self-hosted. The whole stack (Supabase + Redis + the four apps) runs on your own infrastructure.