Capaxima is a Windows app for planning a game production. You put milestones, tasks, dependencies and the people of your studio on one timeline. Under the Gantt, a capacity line per discipline turns red on the days where the plan needs more people than you have. The project is a folder on your disk. No account, no server.
A producer or a lead in a studio of 5 to 60 people, planning one project that runs six months to two years. You know every person on the project by name. Your director or publisher asks one question: will we make it with these people?
Most producers answer that question with a spreadsheet next to Jira. The spreadsheet has no dependencies and goes stale in a month; Jira has tickets and assignees but no roster with dates and no capacity. Capaxima is built for that one question. An indie lead of two to five people can use it the same way, with fewer cards.
Every feature in Capaxima does one of these three things. Features that do not are not added.
Each task has an estimate in person-days and needs one or more disciplines. Each person on the roster has a start date and an end date. Capaxima sums the two per discipline per day and draws the result under the Gantt: red where demand exceeds the team. Automatic assignment gives every task to a named person who is free; whatever nobody can take stays in the backlog, task by task.
“How many artists are we short in March?”
Dates move, people leave, a board is imported, two copies are merged. Capaxima checks the board for five kinds of conflict: a dependency cycle, a task that must end before it starts, a dependency that crosses a gate, a dependency to a deleted task, and a person on two tasks at once. Each conflict has a one-click fix, and each fix is one undo step.
“What broke after yesterday's move?”
A variant is a branch of the plan inside the same board: a different set of tasks, estimates or dates. One switch changes the board, the milestone stats, the Gantt and the export. Both variants share one history, so there is no second file to keep in sync.
“If we cut feature X, hire two people and move the gate — what happens?”
.roadmap.zip.A project is a folder you choose. Capaxima has no account, no server and no telemetry. It works with the network off.
One exception, for the beta only: the beta build checks its key with capaxima.com once a day and stops working when the beta ends. The paid version will not have this check; its licence is verified offline. See the beta terms.
Put the project folder where the team already keeps files: Dropbox, Google Drive, a Git repository. Every board is a CRDT document with its full history. When two people edit two copies, the copies merge without losing either person's changes.
There are no live cursors, comments or chat. If your team needs to plan together in one browser window, Capaxima is the wrong tool.
Capaxima includes an MCP server. Claude Code, Cursor or any MCP client can build a first roadmap on an empty board, link tasks, level resources or report on the schedule. The server uses the same actions as the UI, so every change is one undo step in the app. There is no model inside Capaxima; you bring your own agent. Eleven prompt recipes appear in your editor as slash commands.
These are decisions, not gaps in the roadmap.
Not yet. Capaxima runs on Windows 10 and 11. We count macOS requests; if you need it, write to us. A browser demo with a sample board is planned for everyone else.
No. The app has no account, no server and no telemetry. The beta build is the one exception: it checks its key with capaxima.com once a day and stops when the beta ends. The paid version verifies its licence offline.
In a folder on your disk that you choose. The board is one file with its full history. You can export it at any time as Markdown, CSV, JSON or a full .roadmap.zip.
Yes, if the project folder is in a place the team syncs: Dropbox, Google Drive or a Git repository. Two people can edit two copies; the copies merge without losing changes. There are no live cursors, comments or chat.
No. Jira tracks tickets, statuses and sprints. Capaxima plans phases, gates, the roster and capacity. Capaxima exports a CSV that Jira imports, and imports a JQL query as a board. There is no two-way sync. More on the split.
A production plan runs for months, and a day is the smallest unit people can plan reliably at that scale. It also makes capacity and demand directly comparable: one person for one week is five person-days. The arithmetic, with an example.
You do not need it. It is a Model Context Protocol server that lets Claude Code, Cursor or another MCP client read and change the board. It uses the same actions as the UI. If you never connect a client, it does nothing. How it works.
The beta is free. The price of 1.0 is not set yet. What is decided: a paid licence is a file, checked offline, with no calls to our server.
HacknPlan and Codecks are task trackers for game teams: boards, cards, hours, the work of this week, in a browser. Capaxima is a planner for the producer: whether the plan fits the team, and what happens when dates or the roster change. Side-by-side comparison.
Version 0.10.0 is the first build under the Capaxima name. It is a beta by request: sign in with an emailed link on the beta page, tell us what you plan with today, and you get a Windows installer, a key and a short scenario to run on your own project. Before 1.0 the board format and the MCP tool names may still change.