Operational writing on licensing routes, migration, payments, player safety and the economics of a platform contract. Written by the people here who do the work.
Who writes these
Every piece is signed by the person here whose job the subject actually is, and the name in the byline is the name the structured data carries. Nothing is published under an invented author.
6 pieces, newest first.
Every piece here started as a question an operator asked us on a call. Nothing is written to fill a publishing calendar, so the list is short and stays short.
Martin Baris9 minute read
Kris Kukic10 minute read
Each row carries the subject it belongs to, so a reader looking for migration or for commercials can find it without a filter.
Three lines carry almost all of the cost, and the definitions underneath them carry almost all of the risk. A clause by clause guide to the commercial half of a platform agreement.
Hassan Naveed8 minute read
Every casino platform says it supports multiple brands. Very few agree on what that means. Six tests that separate a real separation model from a skin over one shared database.
Branko Petrovic8 minute read
In most stacks, compliance finds out about a payment after it has happened. Moving the check in front of the money changes what your team spends its day doing, and what a regulator sees when they ask.
Gayle6 minute read
The platform is rarely what delays a launch. Licence approval, payment onboarding and content agreements are. A checklist for founders, ordered by how long each item takes to clear.
Marko8 minute read
We reply within one working day.
