FOR STUDIO LEADS

Ship your game knowing the backend was tested before any player touched it.

Most multiplayer studios reach launch having never tested their backend under production conditions. Staging environments drift from production. Load tests run once, manually, if they run at all. Integration bugs are found by players. Aevs changes the loop: every pull request gets a live backend sandbox, every scenario that could fail has a written assertion, and nothing merges if the assertion fails.

Before and after

What a validation plan looks like

A validation plan is a file in your repo that describes what your backend should do. It reads like a test: make this request, wait for this condition, assert this response. It runs automatically on every PR. Your team writes them once; they run forever.

const result = await client.runPlan(sandbox.id, {
  id: 'matchmaking-4v4',
  steps: [
    // Two players queue for 4v4
    { type: 'http', method: 'POST', path: '/match/queue',
      body: { playerId: 'p1', mode: '4v4' } },
    { type: 'http', method: 'POST', path: '/match/queue',
      body: { playerId: 'p2', mode: '4v4' } },

    // Match activates within 10 seconds
    { type: 'wait', condition: 'match.status === "active"',
      timeout: 10_000 },

    // Match has the right player count
    { type: 'http', method: 'GET', path: '/match/active',
      assert: { players: { length: 8 } } },
  ],
})

Launch confidence, not launch anxiety

When Pokémon Go launched in July 2016, servers buckled under 50× expected load within hours. Niantic had to geo-fence the rollout for three weeks while they scaled. When Palworld launched in January 2024, 2 million concurrent Steam players overwhelmed matchmaking; the team spent 48 hours on emergency infrastructure changes.

Neither failure was unforeseeable — both failures had clear precursors that integration tests would have surfaced. The difference between a launch disaster and a launch is whether you validated the backend before players did.

With Aevs, your CI history for the past six months is a record of every backend scenario your team has validated. Launch week, you look at green CI — not server dashboards and Discord panic threads.

It doesn't slow your team down

The sandbox provisions in under 60 seconds. Validation plans run in parallel with other CI checks. Developers don't wait — plans complete while linters and unit tests run. Writing the plan for a new feature takes 15–30 minutes and runs on every subsequent PR that touches the same area.

The net effect for most studios: fewer hours in post-launch hotfix mode, fewer incidents that require all-hands debugging, and a QA team that can focus on gameplay and UX rather than manually verifying backend contract correctness on every build.