Skip to content
Launch in September 2026

Your documentation says one thing. Your team does another.

As the project grows, documentation breaks. Strudo structures it in typed blocks by department and priority so the whole team works from the same truth.

The individual plan is free forever.

Strudo editor screenshot

Explore Strudo with a real
game design document

Explore the full editor
The problem

Documentation that works in pre-production breaks in production.

01
The setup
Everything looks under control.

In pre-production everything seemed under control. A central document in one tab, spreadsheets with technical values, visual references scattered across shared folders. But production always comes.

02
The break
Production arrives and the system explodes.

The documentation is 40 pages long and nobody knows what's approved, what was cut last sprint, or what changed last week. The programmer needs specific data and it's in a spreadsheet only the designer has. The artist is preparing assets for a system that was already redesigned. The director asks what makes the next milestone and nobody has a quick answer.

03
The spiral
The document dies.

The team stops checking the document because it's probably outdated. And when they stop checking it, it falls out of date even faster.

The result
Nobody knows which version is true.

One simple question. Four sources. Three different answers.

How much damage does the short sword deal?
GDD (Notion)
12
Base damage from initial design.
Updated 3 weeks ago
Balance sheet
14
"Fixed in sprint 4"
Updated 5 days ago
Code (Unity)
12
Implemented from August GDD.
No changes in 2 weeks
Slack · #design
"15?"
"I think we bumped it, can't remember"
Yesterday, 16:42
The solution

Documentation that can't be misread.

Strudo replaces endless pages of free-form text with specialised blocks. A balance table is a balance table, not a paragraph each department reads differently. A state diagram is an interactive diagram, not an exported image you have to redo every time something changes.

Typed blocks

Attributes, formulas, dialogues, controls, state diagrams, balance tables. Every block has a type that removes the ambiguity of free-form text. 24 special block types designed for production documentation.

Department filtering

Each block is assigned to one or more departments. Each team member filters and sees only what's relevant. Leadership keeps the full picture. Zero noise, zero confusion about who owns what.

Block priorities

Essential, Optional, Future, DLC. Every system in the project has a visible priority level. The team knows what's critical for the next milestone, what gets cut if time runs short, and what's saved for later.

Origin

Built from the pain.

Strudo was born from the frustration of documenting a project with four different tools. One for writing, another for diagrams, another for flows you export as an image and paste into the document. Two hours of work that's worthless next week because the system changed.

Before
01
Text document
Write the system description in prose.
No structure. Everyone interprets it differently.
02
Diagram tool
Create the state diagram or mechanic flow.
Separate tool. Requires access.
03
Export as PNG
Render, export, paste into the document.
If the system changes, the PNG is garbage.
04
Cloud storage
Share the reference. Explain which version to use.
Nobody knows if the link is still valid.
2 hours of work. Irrelevant next week.
VS
Today with Strudo
01
Text block
Inside the system, in the same editor.
No separate tool.
02
Diagram block
Inline, inside the same document.
No external tools. No exporting.
03
Always up to date
The diagram lives inside the system.
If the system changes, the diagram changes.
04
One link, the whole truth
The whole team accesses the same version.
No broken links. No parallel versions.
5 minutes. Always current.

The individual plan is free forever. No card, no time limit.

Create your account and start documenting your first project in minutes.