Skip to content
kumo

One app, every discipline

Each person on the team opens kumo for a different reason. Here is what it does for each of them.

Producers

Milestones on a timeline, sprints with velocity and flow, scenarios that show what a cut buys in dates and budget, goals that measure themselves, and one Calendar for the studio. Plan & produce

Designers

The design lives in the wiki as concepts linked to the tasks that build them. Boards for flowcharts, screen flows and level layouts, and dialogue that exports to ink and Yarn Spinner. Wiki & docs

Artists and animators

Reference boards, versions on every task, frame notes on renders, and 3D review of the model, its LODs, UVs, rig, blend shapes and animation. The verdict moves the task. Review

Audio

Sound graphs on the canvas, played and mixed live, exported as audio, MetaSounds, or to Wwise, FMOD Studio, Godot and Unity; sound tracks on board videos; voice-over lines on the task. Boards

Engineers

Builds and their logs, a build computer in one popup, pull and merge requests on tasks, the API and webhooks, and an assistant that builds in Unreal through checked operations. Builds & release

QA

The Bugs page, crashes grouped into bugs, the in-game reporter, test runs and certification checklists on the task, and playtests whose feedback becomes work. Bugs & QA

Community and marketing

A campaign calendar, posts sent on their day to Discord, Bluesky, Mastodon and X, Steam reviews and Discord messages proposed as bugs, and the numbers read back into Insights. Marketing & Insights

Founders

Hiring with a careers page, people’s records, leave and reviews, funding calls matched to your project and refreshed daily, the investor network, and store sales and wishlists. Run the studio