From first email to certificate
Five steps, a named engineer throughout, and no surprises on price.

Scope and quote
Tell us what you need certified. Within one working day you get a written scope, fixed price and start date.
Submission
You send the build, documentation and test environment access through our secure portal. We confirm it is complete within three working days.
Testing
Your engineer runs the tests and shares findings as they come, not only at the end, so fixes start early.
Review
A second engineer who did not run the tests reviews every finding before anything is signed.
Certificate
We issue the certificate and report, with file hashes of the certified build, and file them with the regulator where required.
Changes, re-tests and annual audits
Certification is not a one-off. When you change a certified product, we test the change and anything it could affect, not the whole product again. Emergency security fixes can go live first, as long as you tell us and the regulator within 24 hours and submit the fix within five working days.
Crash games and draw systems are re-certified every year. Platforms get an annual compliance refresh, timed to your licence renewal.

Submission checklist
| Item | Why we need it |
|---|---|
| Technical documentation | Architecture, versions and configuration, so we test what you actually run |
| Maths specification and paytables | For games: to verify return to player independently |
| Build and source code | Delivered through our secure channel; source code stays in Kenya |
| Test environment access | Mirroring production configuration |
| Existing certificates and reports | So a Kenya review can replace a full re-test where possible |
| Signed declaration | That the materials are complete and accurate |
Can we help you?
Send us the game, platform or draw system. We reply within one working day with scope, price and a start date.
Get in touch