Case study 01 · iGaming platform · B2B · Regulated market
A B2B platform that lets sports-betting and online-casino operators in the regulated Brazilian market run their own branded product: a player portal on the web, as a PWA and in mobile apps, and a back office to manage it. The multi-brand frontend we built took it from a single brand to seven on one codebase, with more than a million players.
operator brands on one codebase
players across the brands
of portal commits were bug fixes, 2022 → 2026
to build identity verification (KYC) for a regulatory deadline
page-speed score (Lighthouse) after the Next.js rebuild, on staging
automated test files, 72% coverage
A white-label platform grows by adding operator brands, and this one was preparing to launch into a regulated market where search traffic mattered. In autumn 2022 the player portal served a single brand, wasn't ready for search engines and carried duplicated desktop and mobile code from a legacy sportsbook. The back office was a monolithic app from 2020.
Regulators added hard deadlines along the way. In late 2025 the portal hit a performance ceiling and still had no automated tests, so the team decided to rebuild it on Next.js.
The client, brand names, domains and screenshots are under NDA. Quality figures come from git history.
Server-side rendering with each brand's look and localised addresses, so the portal could bring in the search traffic the launch depended on.
A theming system turns a brand's palette into a complete look, and each brand's country, currency, language and payment settings live in the back office. Seven brands launched on it in two years, and brand apps for iOS and Android were added too.
Both products moved into monorepos split into eleven micro-frontends with clear boundaries, and the back office was rebuilt on a new API, removing about 65,000 lines of legacy code in six months.
Document scanning, face detection and liveness checks built from scratch and live within 1–1.5 months. In 2026 the company switched to an external provider.
Visual builders for the header, navigation and game cards with a live preview, so operators change their sites without developers.
Component libraries for the portal and the back office, and an in-house data table that replaced the paid AG Grid Enterprise in 141 places.
In 2026 a team of five rebuilt the portal on Next.js 16 and React 19, with page speed and automated tests as the goals. It is ready for launch.
Under the hood
Operators expect banner, game and promo changes to appear on every brand's site at once, while pages stay cached for speed. Timer-based revalidation can't do both: content is either stale or constantly rebuilt.
Frontend lead · Oct 2022 → today
Joined as a senior engineer and became frontend lead within the first year. Owns the frontend architecture and infrastructure, the design systems and the mobile apps, and reviewed about three in four portal pull requests.
Senior frontend engineer · Aug 2025 → Jun 2026
Built the header, navigation and game-card builders end to end, from the admin editor to the live site. In the Next.js rebuild, moved about 57 components — from sportsbook cards to responsible-gaming pages — and wrote 86 test files.
Frontend engineer · Jul 2025 → 2026
Built identity-document and verification flows and settings in the portal, and sportsbook, user and bonus screens in the back office. In the Next.js rebuild, moved the casino and sportsbook screens, set up PWA behaviour and added tests.
Two-week sprints with a board per brand. The client's PM owns priorities and releases, and the engineers can reach the client directly with questions. Every change goes through a reviewed pull request with automated checks, and a feature can wait for its release without blocking others. Since 2026 the team has worked with Claude Code under agreed repository rules.
Start a conversation
Tell us what you're building, modernising or trying to unblock. One contract via a Lithuanian entity, EU VAT invoicing — we reply within one business day.
