Solutions

One board where writing, design and engineering meet

Branching stories die in the gaps between tools — the writer's doc, the designer's spreadsheet, the engineer's JSON. Storyloom keeps the story itself as the shared artifact: writers draft in it (or import their Docs), designers balance and test in it, technical folks wire variables and export to the engine — all on the same canvas, with layers each discipline can show or hide.

How the disciplines share one space

✍️NarrativeDraft in Google Docs or Word and import; write dialogue with per-line speakers and emotions; keep voice notes and narrative notes on the beats; export a screenplay or the outline back to Docs for notes from anyone.

🎛DesignBalance economies with tracked variables and the Economy view; verify structure with Path explorer and targets; keep reference images in design-note fans; review beats and approve or request changes.

🔧TechnicalA tech-note layer, technical review of every variable read/write, engine contracts via Unity/Godot/Unreal/Ink/Yarn exports, entry points and events named for the engine, strings export for localization.

Collaboration is built in, not bolted on: cloud projects and workspaces, live co-editing with cursors, threaded comments with @mentions, review requests, suggest mode for propose-don't-overwrite editing, and an inbox so nothing addressed to you is lost.

Solo developers

Everything runs in the browser and works offline against local storage — no account needed. Start from a genre template or a rules-generated skeleton, keep chapters as projects inside one workspace, and lean on the built-in QA (story check, path explorer, targets) as your second pair of eyes.

Import the notes you already have — a Word outline becomes a connected board in one step.
Test-play in a generated Unity scene (top-down, third- or first-person) before writing a line of engine code.
Export to Ink or Yarn if your pipeline already speaks them; take the JSON anywhere else.

Indie & small teams

A writer, a designer and a programmer can be in the same project at the same time — live cursors, per-field merges, and a soft lock so nobody tramples a beat mid-edit. Reviews and statuses (draft → in review → approved) give just enough process without a producer.

Share a whole workspace once — every cloud project in it, including ones added later, follows.
Suggest mode lets a contract writer or playtester propose lines without write access.
The beat sheet and storyboard PDF keep meetings grounded in the actual story, not a stale export.

Studios

Storyloom deploys as a static site you host, with your own Supabase project for accounts, row-level-security-backed sharing, and Stripe-driven plans — your data stays in infrastructure you control. Multiple quest lines live on one board via entry points; workspaces mirror your game's chapters or pods.

Reviewer roles, approval flow, and email digests keep leads on top of a large cast of beats.
Technical review + engine exports act as a contract between narrative and engineering.
Version history, live sessions, and per-user plan limits are enforced in the database, not the client.

Education

Interactive-fiction and game-writing courses need a tool that is free to start, runs on anything with a browser, and makes structure visible. Storyloom's canvas is the lesson: branching, gating, economies and pacing are all on screen, and the play mode gives instant feedback.

Students import their essays/outlines and see them become playable structure.
Instructors comment, @mention, request changes and approve — a workshop loop built in.
Path explorer and targets turn "is your story well-formed?" into something checkable.

Curious what it costs? Plans are on the home page — the free tier is genuinely usable, and everything local never needs an account at all.