Case study · CrustlabiGaming
Mar to Nov 2024Senior frontend engineering & vendor migration02 / 04
Mar to Nov 2024Senior frontend engineering & vendor migration02 / 04
All clients
Crustlab
Migrating an iGaming platform off an undocumented provider
Brought in to take ownership of a third-party integration nobody could explain, on a legacy casino product that could not go offline.
iGamingMar to Nov 2024
−71%
Time to interactive
7 s → 2 s
What changedMeasured before
and after3 outcomes
in production02
and after3 outcomes
in production02
What changed
(01)−71%Time to interactive7 s → 2 s
(02)0Downtime during the provider switch
(03)100%Provider contract documented
The processWhat we walked into
and what we didSenior frontend engineering & vendor migration03
and what we didSenior frontend engineering & vendor migration03
What we
walked into
- The incumbent game provider integration had no documentation and no internal owner, only legacy code and live traffic.
- The provider UI ran in iframes, and time-to-interactive on the main game screen reached 7 seconds.
- The new front end had no login or registration.
- The vendor switch had a fixed commercial deadline and could not take the product offline.
What we
did
- (01)Reverse-engineered the existing integration by tracing production network traffic against the legacy codebase, and documented the real contract.
- (02)Turned that document into the technical specification used to negotiate scope with the incoming provider.
- (03)Designed the replacement API client together with the new vendor's engineers, then implemented it behind a swappable interface.
- (04)Replaced the iframe-embedded provider UI with native React components and measured TTI in PageSpeed Insights before and after.
- (05)Built login and registration UIs and their API integrations from scratch.
StackNext.jsReactTypeScriptReact Querystyled-componentsPageSpeed Insights
Now an agentThis playbook runs
on every commit2 agents
in the fleet04
on every commit2 agents
in the fleet04
What we did by hand,
the fleet now repeats
The agents below now run the checks, measurements and fixes from this engagement on every repository they connect to.
Next stepGains Audit
Fixed price, fixed scopeTwo weeks
One repository05
Fixed price, fixed scopeTwo weeks
One repository05
Find out what
slow costs you.
Start with a two‑week audit.
We connect the fleet to one repository for two weeks. You get a ranked list of gains in euros and the first pull requests, already open.