Approach
Delivered so the client can run it without us.
A regulator that cannot operate, extend or re-tender its own enforcement infrastructure has not acquired a capability; it has acquired a dependency. Our delivery model is designed to prevent that.
Delivery model
Five commitments
Staged delivery, working results
Each stage of the programme ends in a system that does something, used by real officials against real cases. A stage that produces only a document has not produced a result, and we do not treat it as one.
The licence register comes first
Everything else depends on knowing, authoritatively, who is licensed for what. Enforcement, monitoring and player protection all resolve against that record, so it is the first subsystem built and the first handed over.
Sovereign delivery
Source code, database schema, operational runbooks and infrastructure-as-code are handed to the client and held in escrow. The client can operate the system, extend it, or re-tender it to another supplier without us.
Open technology core
The platform is built on an open technology core: no per-seat licence fees, no proprietary runtime and no dependency on a single cloud provider. Hosting can move inside the Republic, between providers, or on-premises.
Skills transfer from the first sprint
Every subsystem has a named client counterpart from the first sprint, not from the closing handover phase. They review design decisions, run the system alongside us, and take operational ownership progressively.
Position
Independence
We hold no gambling licence, no interest in any operator, and no revenue exposure to gambling turnover.
This is a structural requirement rather than a statement of good intentions. An enforcement register whose operator has a commercial interest in who appears on it is not credible — not to the licensed industry, not to the courts that review its decisions, and not to the public it is meant to protect.