Choose the QA capacity your team needs.
Use BugHunter in your team's workflow, with help getting started. Choose your execution capacity and add hands-on support when you need it.
QA capacity for your next release. Experience for the builds after it.
Start with a focused run, then add recurring capacity as your release cadence grows. Keep the game's checks and history connected across builds. We help you get started with BugHunter; your team can run the ongoing workflow, with additional help available when needed.
One product with flexible assistance: pick your execution capacity and add hands-on support when you want it. These stages are how an engagement progresses, not separate products.
Send a game link and see BugHunter work through a small, agreed task on a supported build of your game. We follow up to prepare the demo around your game.
Evaluate one repeatable QA workflow with defined builds, checks, evidence, review, and a follow-up run. This is a paid engagement with an agreed scope and fixed fee, separate from the free Guided Pilot Run.
Keep agreed checks running across upcoming builds. Choose the execution capacity, support, review, and integration scope your team needs.
What a scoped engagement coversShow
- Included builds and checks
- Qualified execution environment
- Runtime and retry allowance
- Setup and evidence preparation
- Studio QA review responsibility
- Included retest scope
- Any separately scoped integration or maintenance
A single run or capacity plan does not by itself include indefinite maintenance, human triage, integrations, or unlimited retests. We confirm inclusions before work begins.
Your release schedule doesn't stop at 6 p.m.
Keep repeatable QA running after the team signs off. Add execution capacity for launches, content drops, and hotfixes, then bring results into the next review. These terms stay separate and clearly labeled:
Day or night, including overnight. 24/7 execution is when work can run, not unlimited included usage.
Active runtime in your plan (e.g. up to 200 hours/month on Studio Lane). Not 200 human hours saved or 200 parallel agents.
How many runs or devices operate at once, agreed for your workflow.
Human setup, review support, and response hours are defined separately in your plan.
Add execution around launches, live events, and hotfixes. We arrange runs and capacity around your workflow; initial game setup and additional device provisioning follow the normal service process.
Included agent hours
How pricing works
How teams scale with BugHunter
From validation to continuous coverage
Plans for every stage
Start with a guided pilot, validate on a supported build, and scale to a repeatable monthly AI QA lane.
Guided Pilot Run
Run your first AI QA session with guided onboarding. We help set up your build and review the results with you.
What you get
- Setup + environment preparation
- First AI test run (up to 8 hours)
- Real bug report with logs and video
- Guidance on next steps
Typical use
Evaluate BugHunter before release or integration
We review each request and work with teams where we can deliver measurable results.
Release Run
Run a full AI gameplay test on your build and get reproducible bugs before release.
Actual runtime, not parallel agents.
A focused run on a single build, reviewed with your team
What you get
- Up to 8 active agent hours
- Full bug report (video + logs + steps)
- Regression testing on your build
- AI-assisted onboarding
Typical use
Validate one build before launch or release candidate
One-time run. No subscription required.
We guide onboarding and help prepare your build before the run.
If we see setup issues or low signal, we help adjust your test before execution.
Early access product. Each run is supported by our team.
Studio Lane
Your team's dedicated monthly AI QA lane.
Annual commitment
$1,200 / mo
Month-to-month flexibility
Active agent hours = total runtime, not parallel agents.
Up to 200 active agent hours of runtime per month
What you get
- Continuous testing across builds
- AI QA agent (dedicated capacity)
- Run history and reports
- Priority queue
When it makes sense
- 3+ builds per month
- Ongoing development cycles
- Multiple releases
A predictable monthly lane for teams that want the same checks run on every build.
No charge today. 7-day onboarding and setup period. Billing starts after setup.
Our team will reach out to prepare your environment and connect your build.
Early access product. We support onboarding and setup for every team.
Scout Add-On
Deeper gameplay exploration for teams that need more than regression.
Used after Studio Lane for deeper exploration and edge cases
Requires Studio Lane
- Guided exploration setup
- Edge-case discovery
- Exploration workflows
Scout is a guided premium exploration mode for teams that need deeper edge-case discovery beyond regression.
Command Center
Managed QA expansion for larger studios and live ops teams.
- Multiple AI agents
- Managed onboarding
- Workflow setup
- Integrations
- Support
Plans can be changed at any time.
Recommended path
Capabilities by plan
These are plan capabilities and entitlements, not QA tasks. The QA tasks are Scout, Freeplay, Testcase, and Regression, explained on How It Works. Testcase and Regression run on the deterministic test-case capability shown in the product.
| Plan | Regression | Adaptive | Scout | Command |
|---|---|---|---|---|
| Guided Pilot Run | Yes | - | - | - |
| Release Run | Yes | - | - | - |
| Studio Lane | Yes | Yes | Preview | - |
| Scout Add-On | Yes | Yes | Yes | - |
| Command Center | Yes | Yes | Full | Yes |
Onboarding by plan
More QA coverage, less overhead
Repeatable runs
Start a run on the current build and get findings your team can review.
Consistent checks
Run the same agreed checks on every build as your game changes.
Works with your team
Adds repeatable QA capacity alongside your existing QA team, not instead of it.
Frequently asked questions
See what BugHunter finds on your build
Apply for a guided pilot run or go straight to a release-ready run.