Game QA companies: a buyer’s guide for studios

Game QA companies are external vendors that run functional, regression, performance, compatibility, localisation, and certification testing on games for studios and publishers. Most teams outsource QA to control cost, scale a device lab quickly, or add specialist skills (automation, load testing, certification prep) that are hard to keep on payroll full time. The right game QA companies match your project’s platform mix, engagement model, and QA maturity.

What game QA companies actually do

Game QA companies run structured test cycles against a build to confirm it works, holds up under real-world load, and passes platform submission. The scope splits three ways: functional QA (does the feature match the GDD), non-functional QA (performance, load, stability, compatibility), and certification QA (does the release candidate pass PlayStation TRC, Xbox TCR, Nintendo Lotcheck, or store submission rules).

A typical engagement covers test-plan design against the GDD, daily regression on new builds, defect logging in Jira or a comparable tracker, test management in TestRail or Xray, and reporting cadence agreed per sprint. Automation coverage is scoped per project; economy math, save-load, and multiplayer sync usually pay back automation cost within a few sprints, while cinematic and narrative sequences rarely do.

Standards vocabulary follows the ISTQB foundation syllabus, and test documentation on regulated or enterprise-grade projects often references IEEE 829 for test plan, test case, and defect report structure.

When to outsource to game QA companies

Three signals usually push a studio toward external game QA companies: the project needs a device lab the studio does not want to build, the QA headcount plan does not fit the release calendar, or a specialist skill (test automation, load testing at scale, console certification) is required only for a window.

For mobile releases, the device matrix alone is often the deciding factor. A launch across the top Android and iOS footprint typically needs 40-80 handsets covering active OS versions and hardware tiers. Building and maintaining that lab in house is rarely justified for a single title.

For live ops, the driver is cadence. Weekly patches with regression on every drop scale better when the regression suite is co-owned by a vendor QA team plugged into the studio’s CI. For pre-launch, certification prep is often outsourced because the checklist changes per platform generation and per store.

In-house vs outsourced vs crowd testing

Three models cover most QA setups. Each has a place, and larger studios usually run all three at once.

Top-tier vs mid-tier vs boutique game QA companies

The vendor market splits into three loose tiers. The right pick depends on project scale, platform mix, and how much of the QA scope is volume work versus specialist work.

TRC, TCR, and certification-ready game QA companies

Certification is the gate that stops a release candidate from shipping. PlayStation publishes TRC (Technical Requirements Checklist), Xbox publishes TCR (Technical Certification Requirements), Nintendo runs Lotcheck for Switch submissions, and PC stores add their own submission rules. VR headsets (Meta Quest, PlayStation VR2, PICO, SteamVR) each maintain a separate store review process.

Certification-capable game QA companies keep a submission desk that tracks checklist versions per platform generation, prepares the submission pack, runs pre-cert passes against known-fail items, and coordinates re-submission if the first pass fails. Miss a checklist item and the platform holder returns a fail with a defect list; each round-trip typically adds 2-6 weeks.

For most studios, the practical question is whether the vendor has shipped titles through the same platform in the last 12 months. Recent submission experience matters more than legacy volume, because checklists update between console generations.

Automation and manual coverage across game QA companies

The automation-to-manual ratio varies by vendor and by project. There is no single right answer, but the trade-off is well understood.

Manual QA covers what is subjective or changing:

Automated QA covers what runs often and is stable:

Vendors with mature automation practice usually run the Unity Test Framework, Unreal’s automation system, Appium for mobile, and custom device-farm harnesses. Ask for the automation coverage percentage on their last three shipped titles; a real number sits between 25% and 65% of the regression suite depending on genre and cadence.

Mobile device labs at game QA companies

For mobile-first projects, the device lab is often the single largest QA capex item. A launch-ready lab typically covers 40-80 handsets across active Android and iOS versions, split by chipset tier (low, mid, high), screen size, and refresh rate. Each device needs a rotation schedule so battery health, storage state, and OS version stay production-like.

Publicly reported labs at top-tier game QA companies exceed 3,000 devices worldwide. Mid-tier vendors typically run 200-800 devices across one or two regions. Boutique vendors focused on mobile keep 100-300 units aligned to a narrow platform target.

For scope beyond mobile handsets, the practical mix includes console dev kits (per platform per SKU per region), VR headsets per supported store, and PC hardware matched to the game’s minimum, recommended, and enthusiast spec. For a deeper look at platform-specific mobile QA, see the Game-Ace mobile game testing guide.

Cost model at game QA companies

Most game QA companies price under one of three models: dedicated team (monthly rate per QA engineer), fixed-scope project (agreed cycle, agreed deliverables), or milestone-based (bundled per release candidate or per certification submission).

Dedicated-team rates on mid-tier vendors typically fall in the €3,000-€6,000 per engineer per month range, depending on region, seniority, and specialisation. Automation leads and cert specialists sit at the top of the range. Top-tier vendors carry a 20-40% premium against mid-tier for the same seniority, reflecting scale overheads and global lab access.

Fixed-scope QA cycles for a mid-sized mobile release typically fall in the €30,000-€120,000 range, with certification prep and load-test scope moving the top of that band. Live ops regression per patch typically runs €2,000-€8,000 per drop, scaled to sprint length and platform coverage.

Cost also depends on device-lab access model: pass-through fees per device, blended into the day rate, or included as capacity. Ask vendors to break the line items out; hidden device-lab surcharges are a common source of budget overrun.

A procurement checklist for game QA companies

Before signing with any game QA vendor, run this checklist against the shortlist. It surfaces the questions that separate real production capability from marketing decks.

A short list of current game QA companies

The vendor landscape includes global providers, mid-tier specialists, and boutique studios. The table below covers eight active game QA companies commonly considered by publishers and independent studios; it is a starting shortlist, not an endorsement, and every project should validate references against the procurement checklist above.

Beyond this shortlist, active game QA companies also include QA Mentor, Babel Media (Keywords group), Enzyme Testing Labs, and specialist boutiques for VR, competitive integrity, and single-platform certification. Match the shortlist to your platform mix, engagement model, and QA maturity before running requests for proposal.

A QA case from Game-Ace

Two next steps if you are shortlisting game QA companies for an upcoming build or a live game:

When to talk to Game-Ace about game QA companies

Game-Ace sits in the mid-tier of game QA companies, with 120+ in-house specialists and QA capacity under Team Extension, Co-development, and Full-cycle delivery. Engagements typically open with a test-plan review against the project’s GDD, agreed exit criteria per QA type, and a coverage split between automated regression and manual exploratory work. Standards vocabulary follows the ISTQB foundation syllabus and test documentation aligns to IEEE 829 where the project requires it. Test management runs in TestRail or Xray, defect tracking in Jira, and automation on the Unity Test Framework, Unreal’s automation system, or Appium depending on platform.

If a QA engagement is part of your roadmap, game development studio Game-Ace supports the cycle end to end. Related services include game testing services, the option to hire game testers, game co-development for teams that want QA embedded alongside their in-house engineers, and full-cycle game development when QA is scoped inside a turnkey delivery. For a broader overview of QA scope and cadence, see the Game-Ace guide to game testing.