The Game Development system for all teams and agents
Art, code, design, audio, QA, product and community — every team on one grid, from the first pitch to launch day and the players after it. Built for the AI era.


See how it works
From the first sketch to launch day
A game moving through LevelGrid: planned, designed, built, tested and shipped by every team, then put in front of its players — on the same grid.
Features
Built for game studios
Not an engineering tracker with art bolted on. LevelGrid is shaped like the way a game gets made — by many teams, on one grid.
One board for every team
Art, engineering, audio, QA and production keep their own statuses and labels — and the whole game moves on one board. Priority you can read at a glance, drag to reorder, sub-issues across teams.

A board inside every issue and doc
Sketch the level, mark up the concept, pin the references — on an infinite canvas that lives next to the work, with everyone’s cursor on it.

The GDD, written together
Live documents with an outline, comments anchored to the sentence, @mentions and permissions per document. GDD, TDD and Art Bible are there on day one.

From objectives to issues
Objectives as OKRs, SMART goals or milestones, then initiatives, projects and issues — one chain, with progress rolling up from real work and health posted at every level.

3D objects in the issue
Drop an OBJ or FBX with its textures and turn the model around right in the browser.

An inbox that keeps up
Mentions, assignments and reminders in one place, with the issue open beside the list.

Find anything, fast
Search every issue, doc, board and objective across your games — or jump anywhere with ⌘K.

Your players, straight from Discord
The LevelGrid bot brings your community’s bugs, suggestions and feedback into one box — by form, channel message or forum post. Triage by game, priority and sub-topic, and approve one into an issue on the right team.

Playtests, run from one queue
Post the call to your Discord, collect applications with a form you build, and pick who plays — one by one, in bulk or automatically. The result goes out by DM, only to players who asked for it.

Testimonials
What studios say
“Our artists finally live in the same tool as the engineers. The board inside the issue is what sold them.”
Art director14-person studioSample “The GDD stopped being a file nobody opened. Comments sit on the exact sentence, and the task is right next to it.”
Game designerIndie team of sixSample “Milestones, bugs and the Steam page on one grid. Our Friday review went from an hour to twenty minutes.”
Producer30-person studioSample
Pricing
Priced for studios, not for enterprise seats
Start free with the whole team on it. Move up when the game grows — not when a sales call says so.
Free
For a first project, or a team trying the whole thing on for size.
per user / month, foreverNo credit card, no trial clock.
Create my TeamIncludes
- Up to 10 people
- 1 game
- 250 issues
- 3 boards
- A board inside every issue and doc
- Preset game dev teams, statuses and labels
Indie
Most popularFor the studio shipping a game and tired of paying four tools to do it.
per user / month, billed monthly$96 per user, per year
Create my TeamEverything in Free, plus
- Unlimited people, games, issues and boards
- Objectives, initiatives and projects
- Docs with comments, mentions and permissions
- 3D objects in issues
- Custom statuses, labels and sub-labels per team
Studio
For the studio running several projects and outside partners.
per user / month, billed monthly$168 per user, per year
Talk to usEverything in Indie, plus
- External guests: publishers, playtesters, contractors
- Advanced roles and permissions
- Priority support
Most issue trackers start at $10 per user — and the whiteboard your artists actually use is a second subscription on top. Studios deserve better math.
Prices in USD, per user. Billing is not switched on yet: every team starts on Free, and nobody is charged until it is.
Contact
Talk to the people building it
Moving a studio off Jira, pricing a 40-person team, or a workflow you cannot ship without — write it here. A person reads it and replies by email.
- Migrating issues, docs and boards from another tool
- Plans for studios with outside partners and playtesters
- Anything you need before your team moves over