Midgard Studio is the workspace where your team and AI agents build games. One shared environment, from inception to DLC.
A team builds one scene of their game in Midgard Studio, and each step waits for a person's approval. Ines and Mark agree to build the camp at the second bend of the Gloamwood, and Ines asks @Midgard to summarize chapter 4 from the mood board. Midgard writes the chapter into the game bible, tagging what the scene needs, and Ines approves the chapter. Sarah asks @Midgard to surface the assets the scene needs: Midgard gathers the Gloamwood pack (oak, birch, mushrooms, lantern post, Sarah's Lampkeeper from Blender, tent, fence and boulder), and Sarah approves the pack. Mark asks @Midgard to bring Sarah's camp into Unity: the terrain, path, tent and lantern posts assemble into a lantern-lit night scene, live in Unity, and Mark approves the scene. Dana asks @Midgard to ship the camp to Friday's playtest: patch 0.4.3 passes the playtest, Dana signs off the release, and it is merged, live on Steam and announced. The pack's credits: the oak, birch, tent and the Lampkeeper are Sarah's, from Blender; the mushrooms and boulder come from the Asset Store; the lantern post is built from store parts; the fence is AI generated. Shipped three days before Friday's playtest, by Ines, Sarah, Mark, Dana and Midgard.
A team builds one scene of their game in Midgard Studio, shown at phone size, and each step waits for a person's approval. The Gloamwood project switches between its Chat and Project screens. In Chat, Ines and Mark agree to build the camp at the second bend, and Ines asks @Midgard to summarize chapter 4 from the mood board. In Project, Midgard writes the chapter, with the mood board in a row beneath it, and Ines approves the chapter. Sarah asks @Midgard to surface the assets the scene needs, and the Gloamwood pack arrives as eight cards: oak, birch, mushrooms, lantern post, Sarah's Lampkeeper from Blender, tent, fence and boulder. Sarah approves the pack. The pack's credits: the oak, birch, tent and the Lampkeeper are Sarah's, from Blender; the mushrooms and boulder come from the Asset Store; the lantern post is built from store parts; the fence is AI generated. Mark asks @Midgard to bring Sarah's camp into Unity: the eight assets travel into the scene, the Unity view fills the screen and pans across the lantern-lit camp at night, and Mark approves the scene. Dana asks @Midgard to ship the camp to Friday's playtest: patch 0.4.3 passes the playtest, Dana signs off the release, and it is merged, live on Steam and announced. Each person taps their own approval. Shipped three days before Friday's playtest, by Ines, Sarah, Mark, Dana and Midgard.
Game studios do their best work with Midgard. Run everything your team and partners need on one collaborative platform.
Today
With Midgard
Your team sets the direction, decides what gets into the game, and agents move the project forward stage by stage.
References from anywhere, to set the visual tone.
One source of truth for your whole project.
Every asset in one library, whatever its source.
Scenes built from approved assets, true to the game bible.
Shipped, played and patched from one place.
Mood boardThe Gloamwood
Approve board
Pinterest · Sarah
The Lord of the Rings · Sarah
Valheim · Sarah
Stock photo · Sarah
Pinterest · Sarah
Pinterest · Mark
World of Warcraft · Midgard
Pinterest · MidgardMark
@Midgard find more that match this.
Every asset carries its provenance: what made it, from what, each human edit since, and who signed it off.
Ask for changes at any stage the way you’d brief a colleague. No node graphs, no prompt recipes.
Work lands in your project as real files. Open them, edit them, keep them.
The bible, the assets and every approval are shared across the project, so anyone can carry the work forward.
Midgard exists to give years back: the same team, the same creative vision, less of the production drag.
Clair Obscur: Expedition 33, by a core team of about 30 at Sandfall Interactive
Disco Elysium, by about 35 in-house developers at ZA/UM
Cuphead, by StudioMDHR, a team that started as three people
A small group of studios is shaping the first build. Partners run Midgard on real work, tell us what's wrong, and decide with us what comes next.
A good fit: a studio of 5 to 50 people, in or heading into pre-production, open to trying AI on real work.
Apply as a design partnerOr write to contact@getmidgard.ai with your studio name, team size and engine.
Midgard is a production tool for professional studios. Join the early-access list, or apply to shape the first build as a design partner.
Occasional updates, no spam. Unsubscribe anytime. Running a studio? Apply as a design partner
