Projects
Project

Phoenix Games Landing

Every betting site runs the same games. Yours won't. Branded exclusive games and a live engagement suite for betting operators.

Sep 2026landingreactgsapgaming
Phoenix Games Landing

games.phoenixverse.io sells the games arm of the Phoenix platform to betting operators. The argument on the page is in the headline: every betting site runs the same aggregator games, so a player has no reason to stay. Phoenix builds games under the operator's brand, in the formats its market plays, exclusive to its lobby, then keeps players inside them with rain, jackpots, tournaments, missions, streaks and free bets, all run live from one backoffice.

Built during my time at Phoenix Games (Oct 2025 to Sep 2026), as one of the sites in the Phoenix landing monorepo.

What is on the page

  • A dark hero on a near-black sheet, with the Phoenix mark blown up behind the type as a watermark and the claim set in two weights: white for the problem, violet for the promise
  • See it in your brand. The primary call to action opens a demo that drops a live game into the visitor's own colours in about a minute
  • Games. A roster of what Phoenix builds, in the formats each market plays. One roster, not three stacked lists
  • Engagement. The retention tools and how each one is run from the backoffice
  • Backoffice. What the operator's team actually touches, day to day
  • A blog, and a separate /games venue page that is the live catalogue

Motion

This is the most cinematic of the Phoenix sites. Scroll is smoothed with Lenis, and GSAP ScrollTrigger drives the reveals, the headline split and the tool rows that stagger in and back out again as you pass them. The rule I kept was that motion explains the section or it does not ship.

Engineering

  • Vite, React 19, TypeScript, Tailwind v4 with the brand tokens in CSS
  • Multi-page routing: the landing and the games venue are separate HTML entries, with a /games rewrite at the edge
  • Self-hosted fonts, so nothing on the page waits on a third party
  • The same performance budget guard as the hub: critical-path JS and CSS gzipped after every build, and the build fails over budget
  • Published from the shared pipeline to Cloudflare Workers static assets, with a preview URL on every pull request

The hub it belongs to: Phoenix Verse.