Purpose-built for game studios

The QA platform built for
how games actually ship.

Build reusable release templates and compose them into multi-template runs for complete release coverage. Execute checks collaboratively across your whole team, track real-time readiness, and log failures straight to Jira — all in one place built specifically for game studios.

Private beta · Limited spots · No credit card required

Live QA run · PC — Xbox Network Requirements
PC — Xbox Network Requirements
build-412 · RC3PCActive
Progress0 / 10 actioned
XR-007 · Submission ValidatorALPending
No failures — logs attachedALPending
XR-045 · Account PrivilegesSCPending
Privilege 252 (comms) checkedSCPending
XR-015 · Gamertag DisplayMKPending
Full 16-char gamertag rendersMKPending
XR-074 · Connectivity HandlingMKPending
No crash on Xbox service timeoutMKPending
Input · Xbox button glyphsJRPending
Sign-OffALPending

Jira ticket created

Input · Xbox button glyphs

QA-847 · pinned to step

Generic QA tools weren't built
for game studios.

Tools like Qase and TestRail are designed for software teams running automated test suites. Game QA is different — it's hands-on, platform-specific, live-service-aware, and deeply collaborative across testers, leads, and producers.

Certification requirements change per storefront. Multiplayer systems need dedicated sign-off flows. Console patches have their own compliance checklists. Generic tools can't model any of that — so studios end up back in spreadsheets.

Ludovite is purpose-built for the way game studios actually ship — structured test case libraries, reusable release templates, collaborative execution, and a clear audit trail from smoke test to cert submission.

Checklists scattered across docs and Sheets

Structured, versioned release templates

Generic tools like Qase or TestRail

Purpose-built for game studios

Unclear execution ownership

Per-step assignees & real-time tracking

No audit trail per build

Complete, exportable run history

From test case to sign-off

Build reusable release templates, execute checks collaboratively, and track live readiness — with a full audit trail from kickoff to cert submission.

01

Build your release templates

Create templates with nested steps, tags, and instructions — or import directly from the public library or an existing Qase project.

02

Start a QA run

Pick one template or compose several into a single run — smoke tests and cert checks together, for example. Steps merge in order with section headers showing which template each one comes from. The run snapshots against a specific build, branch, platform, and environment.

03

Execute checks collaboratively

Assign testers, track progress in real time, and capture pass, fail, blocked, or skipped results — without chasing anyone on Slack.

04

Log failures straight to Jira

Mark a step failed and a Jira ticket is created automatically — pre-filled with step title, notes, and build context. The ticket key pins back to the step.

05

Sign off and ship

See live pass rates, open blockers, and which checks are still pending. Every run is a timestamped audit record you can export for cert submissions.

Everything your QA team needs. Nothing it doesn't.

Not a bug tracker. Not a generic test management tool. A purpose-built QA platform for studios that ship games.

Template Library

Build a structured library of reusable release templates — organised by platform, feature, or workflow. Import from the public library or Qase, and export any template to CSV.

Reusable Release Templates

Build once, run for every release. Compose multiple templates into a single run — smoke tests alongside cert checks, for example — with section headers so testers always know where each step comes from. Templates version automatically; each run snapshots exactly what was used.

Nested Step Hierarchies

Boot → Matchmaking → Host Migration. Arbitrary depth with aggregated pass/fail status rolled up to every parent.

Team Execution & Ownership

Assign steps to specific testers. See real-time pass/fail/blocked status across your whole team without chasing anyone on Slack.

Run Time Analytics

Track pass/fail rates and average completion time per step across releases. Surface which checks consistently block your ship and where testers get stuck — before it becomes a pattern.

Release Readiness

Instant visibility into pass rates, blockers, and unresolved failures across every active run. Know if you're good to ship before the call.

Jira Integration

Failed steps create Jira tickets automatically — pre-filled with step title, notes, and build context. The ticket key pins back to the step so nothing gets lost.

Slack & Discord

Keep your studio informed without leaving their tools. Get run-started, step-failed, and run-completed notifications in any channel.

Permanent Audit Trail

Every run is a timestamped, immutable record of what was tested, who tested it, and what build it ran against. Export anytime for cert submissions.

Free to use

Public template library

QA checklists sourced from official platform documentation — ready to import in one click and customise for your workflow.

XboxConsoleCertGDK

Xbox Certification (XR Requirements)

Identity, achievements, Xbox Live features, privacy, accessibility, Store billing, and title update validation — mapped to XR numbers.

XboxPCMobileXbox LiveGDK

Xbox Requirements for PC, Mobile & Creators Program

Xbox network integration requirements for PC, mobile, and Creators Program titles — covering stability, player data, privileges, achievements, and multiplayer.

SteamPCValveSteamworksSteam Deck

Steam Store Submission Checklist

End-to-end checklist for launching on Steam — store page, graphical assets, build review, content survey, achievements, Steam Deck verification, and release.

iOSAppleApp StoreiPhoneiPad

Apple App Store Submission Checklist

Pre-submission checklist sourced from the Apple App Store Review Guidelines — completeness, metadata, IAP, UGC, privacy, content rating, and legal.

AndroidGoogle PlaymobileGoogle

Google Play Store Submission Checklist

Pre-submission checklist sourced from the Google Play Developer Policy Center — store listing, assets, content rating, data safety, billing, and release.

Meta QuestVRHorizon StoreOculus

Meta Quest / Horizon Store (VRC)

All required and recommended VRC checks for publishing on the Meta Horizon Store — packaging, performance, functional, tracking, input, assets, and privacy.

ESRBage ratingNorth Americacertification

ESRB Rating Submission

Pre-submission self-assessment for ESRB ratings — covers physical submission (questionnaire + gameplay video) and digital IARC routes via store portals.

PEGIage ratingEuropecertification

PEGI Age Rating Submission

Pre-submission self-assessment for PEGI ratings across 38 European countries — covers IARC digital route and formal PEGI signatory submission for physical releases.

Works with your existing tools

Connect in one click. No webhooks to configure manually, no tokens to copy-paste.

Jira

Issue tracking

When a QA step is marked Failed, a Jira ticket is created automatically in the project of your choice — pre-filled with the step title, notes, and build context. The ticket key is pinned back to the step so nothing gets lost.

  • OAuth — no API tokens required
  • Choose project key & issue type
  • Ticket key pinned to the failed step
  • Enable or disable per project
Jira Cloud via Atlassian OAuth

Slack

Run notifications

Keep your team in the loop without leaving Slack. Get instant notifications when a QA run starts, a step fails, or a run completes — delivered to whichever channel your team already watches.

  • OAuth — installs in seconds
  • Multiple channels per project
  • Choose which events to receive
  • Enable or disable per channel
Slack Bot OAuth 2.0

Discord

Run notifications

Already running your studio on Discord? Connect your QA channels directly. Get run-started, step-failed, and run-completed events posted as formatted messages to any server channel — no bots to host yourself.

  • OAuth — no manual webhook URLs
  • Multiple channels per project
  • Choose which events to receive
  • Enable or disable per channel
Discord OAuth 2.0 & Webhooks

More coming: Linear, GitHub Issues, PagerDuty, and custom webhooks for any endpoint you already use.

Simple, transparent pricing

Start free. Upgrade when your studio grows. Significantly more affordable than Qase or TestRail — and purpose-built for games.

Free

$0/mo

Perfect for trying out the workflow on a single project.

  • 1 project
  • Up to 3 team members
  • Reusable templates
  • Basic QA runs
Continue with Free

Indie

$49/mo

For small studios running structured release QA.

  • Up to 3 projects
  • Up to 5 team members
  • Unlimited templates & runs
  • Run time analytics
  • Jira, Slack & Discord
Get started

Studio

$149/mo

For active studios shipping multiple titles or live updates.

  • Up to 10 projects
  • Unlimited team members
  • Unlimited templates & runs
  • Run time analytics
  • Jira, Slack & Discord
  • Priority support
Get started

Start free, no credit card required · Cancel or downgrade anytime · No long-term contracts

Annual billing available at checkout — save two months on any paid plan.

Common questions

Everything you need to know before getting started.

Does this replace our bug tracker?
No — Ludovite is complementary. It handles structured release execution and QA sign-off, while your bug tracker (Jira, Linear, etc.) handles defect lifecycle. When a step fails, Ludovite creates a Jira ticket automatically and pins the key back to the step, so both systems stay in sync without manual handoff.
We already use Notion, Google Sheets, or Qase. Why switch?
Sheets and Notion have no concept of a 'QA run' — they can't snapshot a checklist to a specific build, track live pass/fail status across multiple testers, or generate a Jira ticket when a step fails. Qase and TestRail are built for software engineering test automation pipelines, not hands-on game QA with cert requirements, multiplayer systems, and platform-specific sign-off flows. Ludovite is built specifically for how game studios ship.
Can multiple testers work on the same run at the same time?
Yes. You can assign individual steps to specific testers and everyone works in the same live run. Progress updates in real time so leads can see the overall pass/fail picture without chasing people on Slack.
How does template versioning work across builds?
When you start a QA run you choose one or more templates and snapshot them — the run captures the exact steps at that point in time. You can keep evolving the master templates between releases without affecting runs already in progress. Each run records which build, branch, platform, and environment it was executed against. If you compose multiple templates into a single run, steps are merged in the order you selected them, with section headers so testers always know which template each step came from — and timing analytics are tracked per template so you can see where each suite is taking the most time.
What counts as a 'project'?
One project per game. All your templates and QA runs for a title live in one place, regardless of platform — PC, console, mobile. The Free plan covers 1 project; Indie covers up to 3; Studio covers up to 10.
Where do the public templates come from?
Each template is sourced directly from official platform documentation — Microsoft's GDK certification requirements, Apple's App Store Review Guidelines, Google Play Developer Policy, Valve's Steamworks docs, Meta's VRC guidelines, and the ESRB and PEGI rating guides. We link to the source on every template page so you can verify the steps yourself. They are not official resources and are not endorsed by the respective platform holders — platform requirements change, so always cross-reference with the current source before submitting.
What happens to our data if we downgrade or cancel?
Your data is never deleted on downgrade. If you drop to Free, runs and templates for projects above the plan limit become read-only. If you need to cancel entirely, get in touch and we'll work out the best path for your studio.

Your next release deserves a real QA process.

Private beta — limited spots, approved manually. Request access and we'll review your studio and be in touch.

Request early access