Insights

Notes from under the platform.

Engineering decisions, architecture and lessons from building technology for iGaming.

Mostly written after something broke.

What is a remote gaming server?

Architecture, responsibilities and where it fits into iGaming.

Control, engineering effort, dependency and operational responsibility — compared.

Change what is making change difficult.

What you thought was the product may have been one customer's assumptions.

“Customer Two knows what Customer Two wants.”

Using a simulated operator to test game launches, wallet transactions and the things that go wrong.

What stays reusable in an RGS as the game moves from slots to crash, multiplayer and mystery packs — and what doesn't.

On the gap between an outcome existing and a player knowing it — and why games seem to want to stretch it rather than close it.