Map a feature once: design doc, prototype, art and programming running in parallel, then QA and platform cert before it ships. Everyone sees what's actually ready today, not a sprint board that says "in progress" on six things at once with no idea which one is really blocking the rest.
✦ Free forever for two people · Runs alongside Jira, Perforce and your build pipeline · The embed on the right is a live flow
Animation and gameplay programming run in parallel, but VFX and level integration each wait on only what they actually need.
Platform matrix, crash triage and the cert checklist are real sub-tasks: ship waits until every one of them is done.
QA only opens up once both VFX and level integration are actually finished, not whenever someone remembers to loop QA in.
The projected ship date is computed from what's actually done and what's on the critical path, not a sprint estimate from six weeks ago.
The same flow embedded above, as a snapshot. 3 of 10 objectives done, two running in parallel.
Animation and gameplay programming both unlocked the moment playtest greenlit the prototype. Neither waits on the other, but VFX and audio need both finished before it can start.
The best feature ideas show up before there's a design doc to hold them. Get the "what makes this feel good" conversation out on an open canvas first, then map the dev flow once the shape is clear.
Grappling hook traversal started as a Brainstorm: what makes the swing feel good, where it could break level design, which moments were worth showing off. The team tagged risks and open playtest questions right on the ideas, before any of it became the flow embedded above.
Keep Perforce, Jira, your engine's own task board and your build pipeline exactly as they are. Flowral is the feature-level plan sitting above them: the milestones that need design, art, programming, QA and platform sign-off, in the order they actually depend on each other. And because it's built for exactly this kind of graph, it's also a plan you can hand to an agent as real targets, instead of a checklist it has to be re-told every session.
Free for two people. No credit card. Publish and embed a flow whenever you want to show your build in real time.
Start free, no card neededNo. Keep your engine, source control and CI exactly as they are. Flowral is the feature-level plan (design, art, programming, QA and cert), not the codebase or the build.
Yes. Two tracks can start the moment they're both unblocked and run independently; whatever needs both waits until the slower one finishes.
Yes. Make cert an objective with sub-tasks per platform, and gate ship on all of them, not on someone remembering to check a box.
Yes. A live Flowral flow, published and embedded the same way any customer can embed one of theirs. It updates in real time as the plan moves.
Not a game studio? Flowral is also used by agencies, dev & product studios and consultancies, and to set targets for AI agents.
