ZenCasino

Context

Sister brand shipped in parallel with KukiMuki in the same product org (backend and other departments alongside frontend). Same three-person frontend setup (one lead, two senior front-end developers). Same Angular 21 patterns and product breadth (lobby → cashier → account), separate repo, theme, CDN assets, and environments — not a theme-only reskin. Architecture decisions are detailed in the KukiMuki case.

Problem

Two live brands need the same features and stack, but separate visuals, CDN assets, and environments — without becoming two unrelated apps.

Decisions & tradeoffs

• Parallel repos with shared patterns instead of one brand-flag app — clearer ownership per brand; tradeoff is parity work.
• Brand delta mostly in theme tokens, assets, and envs — not a rewrite of cashier/forms/KYC — so both sites stay structurally the same.
• Same Payload CMS choice as Kuki (instead of Strapi) — one content approach across both brands.

What I built

• Zen frontend on the shared Kuki architecture: shell, routing, SSR/PWA, NgRx + Signals, orchestrators.
• Brand layer: lobby, theme tokens, light/dark assets on a separate CDN prefix and Zen envs.
• Feature parity with Kuki: games, auth/register, account + Sumsub KYC, cashier (PaymentIQ), promotions, loyalty surfaces.
• Same integration set wired for Zen: Payload CMS (not Strapi), Transloco, Sentry — plus ongoing parity releases.

Outcome

Live sister brand at zencasino.com — production feature parity with KukiMuki from a parallel codebase.