Skip to content

Why Storyloom exists

Creative work needs a surface, not another handoff.

Generative tools made media abundant. They did not make a multi-medium project easier to see. Storyloom is built so the idea, branches, machinery, and final sequence can share one inspectable canvas.

A thread passing through the materials of a modern creative studio.

The premise

A creator should be able to see the whole thread.

The model is not the project. The prompt is not the project. The project is the connected body of references, decisions, iterations, and finished media that a creator directs.

Storyloom began from a practical frustration: image, video, audio, 3D, and assembly often live in separate products. Moving between them breaks context and turns useful branches into downloads with unclear lineage.

An infinite canvas gives that work a shared surface. A factorable engine lets buttons, a copilot, and external agents call the same actions. Open source and BYOK keep the infrastructure legible to the person taking responsibility for it.

Open by default

Trust starts with inspectable code and explicit boundaries.

The core is MIT-licensed, the studio can run without keys, and the BYOK proxy path is documented with its trade-offs rather than hidden behind a trust slogan.

  • No account, database, or funded provider key required to explore
  • Source-visible action, provider, storage, and credential paths
  • Self-hosting remains a first-class way to use the product
An open framework of connected creative materials.

Agent-capable, creator-directed

Automation should expose the work it performs.

The copilot plans and places results on the same board a person edits. MCP calls the same registry. The creator can see the output, compare it, and change direction.

  • Plans and estimates before provider-backed execution
  • Results placed into visible, editable canvas sections
  • Direct controls remain available when delegation adds no value
A branching thread coordinating several creative stages.

Creator ownership

Keep the keys, boards, and production path under your control.

Boards persist in the browser and can be exported or synced to creator-configured storage. Provider accounts and charges stay connected to the keys you choose.

  • Portable board archives with the document and its media
  • Optional S3-compatible storage configured by the creator
  • Local FFmpeg composition outside a proprietary cloud pipeline
A finished sequence gathered around one unbroken line.

One thread, many mediums

Storyloom is a place to direct the system, not disappear inside it.

Open Storyloom without an account or a provider key. Add your own models when the direction is ready for production.

About · Storyloom