Skip to content

iGaming · Platform

Maintaining three casino brands — legacy refactor, shared components and a new flagship site.

Under NDA we stabilised three production gambling brands: cleaned up legacy PHP/JS stacks, extracted shared modules, and shipped a new marketing site without stopping live traffic.

Casino operator · NDA NDA 2024 6 min read
Casino operator · NDA case study
live brands
3
downtime cutover
Zero
client
NDA

Three brands, one operator

Under NDA we support three live casino brands for a single operator — legacy PHP stacks, separate front-end codebases, duplicated payment and bonus logic, and a marketing site that no longer matched product reality.

Maintenance and refactor

We stabilised production first: logging, error boundaries, cache invalidation, payment webhook idempotency. Then extracted shared modules — auth, wallet, bonus engine hooks, CMS blocks — so a fix ships once across brands.

  • Legacy PHP/Laravel services — structured refactors without big-bang rewrites
  • Shared Vue component library — headers, promo tiles, responsible gaming banners
  • Redis session and rate-limit layer — consistent under traffic spikes
  • CDN and asset pipeline — faster LCP on mobile acquisition pages

New flagship site

We shipped a new marketing and onboarding site for the lead brand — modern layout, compliance-first copy blocks, geo-aware registration funnel — while legacy apps kept running. Cutover used staged DNS and feature flags, zero hard downtime.

NDA note

Brand names, jurisdictions and revenue figures are not disclosed. Engagement scope: multi-brand maintenance, refactor and relaunch.

Technologies

  • PHP
  • Laravel
  • Vue
  • Redis
  • CDN

Outcomes

  • Shared design system across brands
  • Reduced duplicate code
  • New flagship site launched
All cases

Blog

The case for boring web stacks

TypeScript, Postgres and edge deployment are not exciting — they are how you still iterate fast in year three without rewriting the platform.

Blog

Mobile release trains that do not break

Fastlane, staged rollouts and feature flags — a practical playbook from eighteen App Store submissions without a Friday-night rollback.

Blog

Shipping evals before prompts

Why we run regression suites on LLM outputs before every release — and how it changed our AI delivery cadence at ZNN.

Fashion · Data

Global fashion manufacturer

A major apparel producer had no single source of truth: Amazon, Zalando, own D2C and wholesale channels each spoke different schemas. We built a governed data layer so finance and ops finally know what came from where.

Payments · Platform

ZNN

Go + Gin backend and Next.js front end normalise invoices and provider webhooks across projects — clients scan a code, pay, and track status in real time.

Luxury · Volume eDTL

The Brand Collector

The Brand Collector resells pre-owned luxury through a supplier network. Same class of problem as a catalogue feed — except each dump crossed 120,000 rows, and the CSV they hold sits above 169,000. Fastify stayed the orchestrator. The heavy compute moved to Go workers. About 60% faster on taxonomy, mapping and pattern-match at that volume.