Solutions

Writers, designers and engineers on one story

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. Narrative drafts in it (or imports their Docs), design balances and tests in it, engineering wires variables and pushes to Unity — all on the same canvas, each discipline on its own layer, reviewing each other's work where it lives.

Three disciplines, one board

✍️NarrativeImport a Word or Docs draft; write dialogue with per-line speakers and emotions; give characters idle lines and moods; keep narrative notes on beats; export the outline back to Docs for notes from anyone.

🎛DesignGame nodes for combat, shops, puzzles and quests; behavior tags that switch whole routes; the Economy view and Path explorer for balance and structure; design-note media fans; project targets.

🔧TechnicalA tech-note layer, technical review of every variable read/write, named engine events, locks on finished beats, and Unity as the pipeline — export or Live link, with a companion package that builds the test scene.

Collaboration is built in, not bolted on: cloud projects and shared workspaces, live co-editing with cursors, threaded comments with @mentions, review requests, suggest mode for propose-don't-overwrite editing, and one inbox so nothing addressed to you is lost. On a phone the same project opens in review mode — read, play, comment, approve.

Solo developers

Everything runs in the browser and works offline against local storage — no account needed. Import the notes you already have, keep chapters as projects inside one workspace, and lean on the built-in checks as your second pair of eyes.

A Word outline — or messy notes reshaped by AI — becomes a connected board in one step.
Test-play in a generated Unity scene (top-down, third- or first-person) before writing engine code.
Live link means "save" and "Unity has it" are the same moment.

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 follows, including ones teammates add later.
Suggest mode lets a contract writer or playtester propose lines without write access.
Lock approved beats so a late edit can't slip in unnoticed.

Studios

Storyloom deploys as a static site you host, with your own Supabase project for accounts and row-level-security-backed sharing — 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; cross-project links stitch boards together.

Reviewer roles, approval flow and email digests keep leads on top of a large cast of beats.
Technical review and the Unity export act as the contract between narrative and engineering.
Version history, live sessions and per-user 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 play mode gives instant feedback.

Students import their outlines and watch 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.

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