GameDriver First Horizon

You run your QA. We keep you moving forward.

First Horizon supports your in-house QA team with the latest GameDriver Core platform and AI layer to rapidly build and maintain test coverage as the game changes – plus a standing weekly session with our solutions engineers to speed and support adoption. Your team is moving from day one, without carrying the risk of going it alone.

First Horizon – this page

Your team operates. We maintain the AI layer and guide every week.

QaaS – fully managed→

We run coverage end to end. Right if you'd rather not operate any of it.

Talk to us about First Horizon How it works

Multi-engine support · AI-supported test coverage

GameDriver · NUnit · CombatSuite.cs

C# · NUnit

1// GameDriver First Horizon – your pipeline, our AI layer
2[TestFixture]
3public class CombatDomainSuite
4{
5  private ApiClient gd;
6 
7  [SetUp]
8  public async Task Init() =>
9    gd = await ApiClient.Connect("localhost:19734");
10 
11  [Test]
12  public async Task Hitbox_RegistersOnContact()
13  {
14    await gd.LoadScene("Combat_Arena_01");
15    var hit = await gd.SimulateAttack("Player", "Enemy_01");
16    Assert.That(hit.Registered, Is.True);
17    Assert.That(hit.Damage, Is.InRange(24, 26));
18  }
19}

Test output
▶ NUnit 3 · GameDriver 4.2 · Unity 2023.3 · Android Pixel 8 Pro
✓ Hitbox_RegistersOnContact · 340ms
✓ Physics_IceCollider_Stable · 512ms
✓ Camera_FollowTarget_Smooth · 228ms
✗ Economy_IAP_PurchaseFlow · timeout 5000ms
✓ Save_Checkpoint_Persisted · 190ms
88Passed
4Failed
4Platforms
2m 14sRun time

EngineUnity · Unreal · Godot

Console accessPS5 · Nintendo

DeploymentSelf-operated

What First Horizon includes

The platform, the AI layer, and a line to our solutions engineers.

GameDriver Core

The full execution platform for Unity and Unreal – the same engine support that powers our QaaS engagements. Author tests against the runtime, run them against your builds. No reduced-capability tier.

AI-maintained coverage

The AI layer that keeps scripted tests alive as object paths rename, UI reorganizes, and features get cut and reintroduced. This is the maintenance work most teams underestimate – and the part a self-run license leaves entirely to you.

Dedicated weekly time with solutions engineers

A standing block of time each week with our senior solutions engineers – setting coverage strategy and helping your team stand up a CI/CD pipeline that runs coverage on every build. It's the setup work that accelerates adoption, not a managed handoff.

Ready for every platform you ship

Ready across PC, Xbox, PlayStation, and Nintendo. GameDriver's runtime overhead is small enough to run on both test kits and dev consoles to more accurately model the user's actual experience.

The capacity problem

One tester does the work of five.

Your testers aren't underused – they're buried. Most studios know they need more QA and stall on the budget call. First Horizon gives your existing team the reach of a much larger one, so coverage gets done without a hire you have to fight for.

5×

capacity per tester

Repetitive execution runs automated and stays maintained, so your current testers cover far more ground. It's relief for an overworked team, not a reason to shrink one.

Your testers get back to the work only they can do.

When execution is automated, the hours it was eating go back to your team – exploration, edge cases, and the release calls that need someone who knows the game. As the cost of running a test falls toward zero, that judgment is the work that only rises in value.

What stays with your team

You keep the work that has to know the game.

Authoring

Writing the tests that cover the parts of the game that matter. Your team knows the product – that knowledge is exactly what makes the coverage worth running.

Release judgment

Exploration, edge cases, and the call on whether a build ships. The judgment work stays where the product knowledge lives.

Running the pipeline

Execution against your builds and wiring findings into your release process, on your infrastructure. We maintain the layer; your team operates it.

Where First Horizon sits

Between building it yourself and handing it over.

	GameDriver SaaS	GameDriver First Horizon	GameDriver QaaS
Execution platform	GameDriver Core	GameDriver Core	GameDriver Core
Who keeps coverage alive	Your team	AI layer maintained by us; you run it	AI-assisted; we run it
Guidance from solutions engineers	Support channel; escalation only	Reserved weekly time	Built into the service
Who owns the pipeline	Your team	Your team, with our support	We do
Adoption & rollout risk	Yours to carry	We de-risk it with you – guided setup and rollout	On us
Who absorbs change risk	You	Shared	We do

GameDriver SaaS

Execution platform: GameDriver Core
Who keeps coverage alive: Your team
Guidance from solutions engineers: Support channel; escalation only
Who owns the pipeline: Your team
Adoption & rollout risk: Yours to carry
Who absorbs change risk: You

GameDriver First Horizon

Execution platform: GameDriver Core
Who keeps coverage alive: AI layer maintained by us; you run it
Guidance from solutions engineers: Reserved weekly time
Who owns the pipeline: Your team, with our support
Adoption & rollout risk: We de-risk it with you – guided setup and rollout
Who absorbs change risk: Shared

GameDriver QaaS

Execution platform: GameDriver Core
Who keeps coverage alive: AI-assisted; we run it
Guidance from solutions engineers: Built into the service
Who owns the pipeline: We do
Adoption & rollout risk: On us
Who absorbs change risk: We do

SaaS licenses the platform and leaves the upkeep to you. QaaS takes the whole layer off your hands. First Horizon is the middle – your team runs QA, the coverage stays alive without becoming your maintenance project, and our solutions engineers are a standing part of the week.

Who First Horizon is for

Built for AA studios with a real QA team.

First Horizon fits studios that already run QA in-house – a team that knows the game and owns the release call – but doesn't have a dedicated automation engineer keeping an execution layer alive full time.

It also takes a quiet risk off the table. A self-run automation stack usually rests on one person: the engineer who built it and knows how it works. At a small studio that's a single point of failure – if they leave, the ability to run the tooling can leave with them. With First Horizon the layer doesn't live or die with one hire.

That's the gap First Horizon closes. You get the platform and the AI maintenance that a self-run SaaS license leaves on your plate, plus a weekly line to solutions engineers who've built coverage at scale. If you have the bench to operate everything yourself, license SaaS. If you'd rather not run any of it, engage QaaS. If you're in between – First Horizon.

See where First Horizon fits.

Tell us about your team, your engines, and where automation sits today. We'll be honest about whether First Horizon, SaaS, or QaaS is the right fit for where you are.

Get in touch