← All news

Why I released Playbook to the public domain

A week after releasing Playbook, the most common question I received was about the license. Here is the case for CC0, and why that choice matters more than the code itself.

Last week I released Playbook - a complete, open-source brand system for responsible gambling content. The most common question I’ve received, by a wide margin, was a variation on the same theme: Why open source? Why release the whole thing for free?

Fair question.

The license is the point

The Playbook repository isn’t released under MIT or CC-BY. It’s CC0, which is the legal equivalent of putting the work in the public domain. No attribution required. No clause you have to run past your legal team. An operator’s compliance lead can copy a template into production this afternoon without sending me a single email.

That choice is part of a larger goal: remove as many barriers as possible between a regulator or operator and a better player-protection program. The license is one barrier. Cost is another. The technical lift of going from a static disclaimer page to a live, multi-channel system is the biggest. Playbook tries to take all three close to zero, so the gating question stops being “can we justify this?” and starts being “how far do we want to take it?”

RG content is not viewed as a competitive moat

The second thing worth saying plainly: nobody competes on the quality of their responsible-gambling page. Operators compete on product, brand, odds, user experience, and acquisition economics. With limited exceptions, player-protection content is a regulatory floor and a trust signal, not a source of a sustained competitive advantage. Treating it as proprietary IP is the worst of both worlds: it costs real money to build, and the upside is “we wrote our own version of the same thing everyone else is doing.”

The reverse is more interesting. For operators who already lead on player protection - and there are some genuinely excellent programs out there - a shared base is what frees up their resources for the work that actually distinguishes them. You stop paying to rebuild templates, design tokens, and game guides from scratch every cycle, and you start spending that money on the things only your team can do: bespoke research, novel interventions, deeper integration with your product. The floor rises for everyone, and the ceiling rises for the people pushing on it.

Creating a shared system helps create the scale on which an ecosystem can grow.

What CC0 specifically unlocks

A few things become possible the moment you remove attribution:

  • Regulators can adopt Playbook as a credible reference template, or quietly use it as the baseline they expect licensees to meet, without endorsing a vendor.
  • Playbook competitors (e.g. ad agencies) can adapt it, improve a section, and ship an even better program that shares the same DNA.
  • And new vendors can build paid services on top of the Playbook system - implementation, localization, new tooling, custom modules - without negotiating a sublicense.

None of those require asking me for permission, which is the entire point. Anything that requires asking for permission does not scale.

Network effects only work in one direction

The strongest argument for releasing this work openly is the one that is hardest to make in a slide deck: responsible-gambling content gets better the more places it shows up. Players who see the same loss-limit concept, the same self-assessment, the same odds explanation across multiple operators learn faster. The category becomes legible.

A proprietary RG system used by one operator generates one operator’s worth of feedback. A shared system used in eleven jurisdictions generates eleven jurisdictions’ worth of compliance modules, edge cases, and translation fixes, most of which I will never have to write myself. That asymmetry only resolves in favor of the open system, and only if the license is permissive enough that contribution feels frictionless rather than charitable.

An open invitation

If you run a player-protection program, take it. Reskin it, swap in your helpline numbers, and ship something better than what you have today. If a section is wrong for your jurisdiction, send me a note. I would rather hear it from you than guess.

If you’re a regulator, review the foundations and tell me what modifications are needed to use it in your market. If you’re a vendor, build on it. If you’re a researcher, build on the brand book and publish your own version with the evidence base you would want operators to follow.

The goal was never for Playbook to be the system. The goal was for the floor to come up, and for the next five years of RG content to start from a better baseline than the last five. CC0 is the only license that makes that outcome low-friction enough to actually happen.

-Kahlil