Scope
What you are shipping, what your release pressure looks like, and where quality already hurts. One call, no discovery invoice.
Week 1 Cipher Solutions · Bulgaria
Release QA for iGaming, owned end to end.
I am a QA engineer who takes ownership of release quality for sportsbook, casino and platform products. Not a CV and not a seat on your team: a coverage plan in writing, testing inside your sprint, and a verdict on every release.
Nothing ships on a guess.
The shape of what you get in writing before testing starts.
Sample coverage plan, not client data. Cipher has no engagements to report yet.
Sample coverage plan, not client data. Cipher has no engagements to report yet.
Station 02 · the gap
"It passed testing" and "we know what was tested" are different sentences.
Ask your team which one was true of the release you shipped last Thursday. The honest answer is usually the first. The distance between the two is where bugs reach players instead of a test environment.
Bet slip
A suspended leg inside an open accumulator. The slip is blocked, or the leg is silently dropped.
Only one of those is correct for your product. A generalist tester walking the happy path never finds out which one you do. Odds feed
Odds drift between selection and submit. A stale price is accepted and confirmed.
The margin is gone before anyone reads a report, and the report will say the release passed. Responsible gambling
Self-exclusion mid-session, with an open bet and a pending withdrawal.
Every jurisdiction has an opinion about what should happen. Your build has a behaviour. Nobody has checked whether they match. Settlement
A void leg recalculated across the remaining legs, off by one rounding step.
Repeated ten thousand times before anybody notices it as a pattern rather than as a complaint. Station 04 · coverage depth
The checks a generalist never runs.
Every QA vendor claims iGaming expertise. Almost none will show you what that actually means. This is 36 failure modes from the coverage plans I build, published in full, so you can judge the domain knowledge before a call rather than after an invoice.
Not exhaustive and not a template. Your product gets its own plan, scoped to what it actually does. Casino, platform and payments each have their own version of this list.
Poll each station before you ship.
No goUnverified
0 checks apply to what you just described, and nothing on this page has tested any of them. This is not a scan of your product. It filters Cipher's published coverage list against what you told it you are shipping. Unverified is the honest default state of every release until somebody owns the checks, which is the entire job.
Station 06 · the model
From a guess to a verdict you can act on.
No recruiting funnel, no bench, no CVs. Five steps take release quality off your desk and put it on mine.
Coverage plan
I map what needs testing and what does not, and hand it to you in writing. You approve the scope before anything is billed.
Week 1Embed
I work inside your sprint, your Jira or TestRail, your CI pipeline and your standups. No parallel process for you to manage.
Week 1 to 2Sign-off
Each release gets a verdict: what passed, what failed, and what the risk is if you ship anyway. Never a green tick with nothing behind it.
Every releaseScale
As volume grows I bring in QA engineers trained to the same standard. You never interview anyone, and I stay accountable for the verdict.
OngoingStop within 30 days if it is not working. You pay only for what has been delivered, and everything produced is yours: suites, frameworks, plans.
Station 07 · who signs off
Founder-led. Domain-tested.
Kristiyan Radev Founder · Bulgaria
QA automation engineer with hands-on experience inside iGaming products, betting flows, bonus systems and platform integrations, before starting Cipher Solutions. The coverage list further up this page is the short version of what that means.
I am taking on a small number of founding accounts. I do the testing myself, you get my full attention, and the terms are transparent. There are no clients to name yet, which is why this page argues with a coverage list instead of a logo wall.
Engagements
Coverage audit
Fixed scopeOne-off · 1 to 2 weeksI map what your testing covers today and what it misses, then hand you the gaps in writing. Yours to keep either way.
Release QA
Per scopeOngoing · per sprint or releaseI own testing for your releases: coverage plan, manual and automation, and a verdict every time you ship.
Launch QA
Fixed scopeDefined engagementA new market, a new product, a platform migration. Testing owned end to end for that scope.
QA function build
CustomTeam · ongoingEngineers trained to one standard, test strategy, CI gates. A QA function you do not have to run.
Priced to the scope, not to an hour you have to audit. You get the number on the call: no proposal cycle, no black-box quote.
Station 08 · open a call
Tell me what you are shipping next.
Twenty minutes, free. I will tell you where I would look first and whether I am the right person to own it. If I cannot help, I will say so and point you somewhere that can.
Prefer a calendar? Book a coverage call. Or email kristiyan@ciphersolutions.dev.