Loomtide builds the Game Factory
Read-only connectors to your Git, tracker, and design docs. One queryable graph. Drift report and change-impact answers from day one.
The problem, in their words
"Every studio I have worked in could tell you the cost of an artist day. None of them could tell me the cost of a decision that got reversed six months later."Rob Sandberg, Game Production Alchemist
"A direction reversed in week three costs a prototype. The same reversal in month fourteen costs a milestone, a pipeline, and usually a few senior people."Rob Sandberg, Game Production Alchemist
"Bigger teams meant worse communication."Heather Cerlan, NEARstudios CEO, in Game Developer
The numbers
of developers lose 6+ hours a week to organizational friction, and finding information is the #1 drain.
Atlassian Developer Experience Report 2025, survey of 3,500 developersof coding time goes to understanding existing work, versus roughly 5% writing new code.
CISQ, Cost of Poor Software Quality in the US, 2022studio postmortems across 23 years: the majority of root causes are people and process, not technology.
Politowski et al., analysis of 200 game postmortemsAt the top end: GTA 6 slipped twice with "polish" as the entire public explanation. The reported cost of the second slip is around $10M a month (reported estimate, Insider Gaming; unconfirmed by Take-Two).
How it works
Read-only connectors to Git, your ticket tracker, and your design-doc folder. No migration, setup in hours, and one person can adopt it alone.
The Game Factory builds a living game wiki: a knowledge graph linking design docs, tickets, and code into one queryable picture of the game.
See where the build and the tickets have diverged from the design doc, ranked by severity, before the rework bill arrives.
Change X, and see every doc, ticket, and system that goes stale before you commit to the change.
"What does the design say about the shop flow, where is it implemented, what breaks if we change it?"
Every connector is read-only and your data stays in your systems. Self-hosted and open-weight model deployment is on the roadmap for teams that require inference inside their walls.
What we do not do
No art, no code, no design comes out of the Game Factory. It is the coordination and consistency layer over the work your team makes.
Your tracker and your docs stay the source of record. The Game Factory reads them; it does not own them.
Connect read-only to the tools you already run and keep working exactly where you work today.
Where this goes
Next, drift flags will be written back into your tracker as comments, so divergence surfaces where the work happens. Later, releases will be linked to their live outcomes, so the next design doc starts from what the last one earned.
Design partners
The Game Factory is built for teams of any size building production games. The pilot is free and scoped: one active feature, a named owner on your side and ours, and a success metric agreed up front.
We reply to every application at with how the pilot works.