Beta Not the live site. Pages in review Live site →
Loft

Loft  /  asset management

At scale, the hard part
is finding the work

A feature or a series makes tens of thousands of files: plates, characters, takes, versions, notes. Loft keeps every one of them in its place, knows which version counts, and can tell you where each one came from and what it cost.

Why it matters

Small teams remember. Big productions can't.

With ten shots, everyone knows where things are. At a thousand, with AI turning out takes by the hundred, memory and folder names stop working. These are the questions that start costing days:

  • Which one is final?Forty takes of the same shot, and the edit needs the approved one.
  • What changed?The character was updated. Which shots used the old version?
  • Who made this, and how?Legal or the client wants the model, prompt, inputs and rights.
  • Where are we?What's waiting for review, what's on hold, and what's late.
  • What did it cost?Labour and generation spend, shot by shot, against the bid.
  • Where's the file?On the cloud, on an artist's desktop, or on the studio's own storage.

How Loft does it

Every file knows what it is

In Loft, a file is never just a file. It belongs to an asset, and the asset knows its type, its versions, what it's used in, where it stands and what it cost.

Structure

Projects start organised.

Pick a project type and the libraries are already there: Assets, Shots, Plates, References, Dailies. Each asset type brings its own fields. A shot has its frame range and handles. A character has its wardrobe. A product has its SKU and approved claims.

Versions

One answer to "which take?"

Takes go from New to Selected, Published and Approved. Publishing gives a take the next version number for its step, so the current version is always obvious and the earlier ones are kept.

Relationships

References, not copies.

A shot points to the characters, props and plates it uses, so a change or a note on the original shows up everywhere it's used. Every derived take records what it was made from, and the flow graph shows the whole chain.

Status

The whole show on one grid.

Each asset type has its own pipeline steps, and they become tasks when the bid is published. The Status grid shows every shot by step, and you can change statuses, assignees and dates in bulk.

Provenance

Every file keeps its history.

Generations record the model, prompt, inputs, author and date. Uploads carry an origin and rights fields, filled in from the file's own metadata where it has any. When someone asks how a file was made, the answer is already there.

Review

Notes land on the take.

Takes go to Dailies. Reviewers pin notes to a frame and approve or send back. Clients see only the libraries you share with them.

Cost

Spend has an address.

Generation spend is recorded on the asset that used it and adds up through the library. Artists' hours are spread over the assets they worked on. Budgets per project, person or asset flag overspend, or block it.

Storage

Your files, where you need them.

Libraries live in Loft's cloud, in your own S3 or GCS bucket, or in an existing folder. Desktop sync works both ways and keeps both copies when there's a conflict. For local projects, an agent on your network moves and creates files.

One record per asset

Everything about a shot, in one place

Open any asset and its versions, references, tasks, notes, provenance and cost are all on that one record. Nobody has to dig through folders or ask around.

Asset record · example

Asset
Shots / SQ040_0120
Type
Shot · 1001–1096 · 24 fps · 8-frame handles
Uses
Characters / Wren, Locations / Harbour, Plates / SQ040_0120_bg
Published
Comp v007 · approved in Dailies
Steps
Layout done · Animation done · Comp in review
Made with
Video model · inputs Wren v004, Harbour v002
Cost
Labour 14.5 h · generation $38.20

Keeping order as you grow

Order that doesn't depend on discipline

Uploaded and generated images are described and tagged as they come in, using the names of your own assets, so search finds them. Got a pile of files? Loft suggests where each one should go, and you check the list before anything moves.

  • Bulk import assets from a spreadsheet.
  • Hand your editor an EDL and only the new takes after a recut.
  • The Assistant, or your own agents through MCP, can find, create, file and update assets for you.
A generation flow: two reference images feed an image edit that made the Lamp Room keyframe

Start with one project

Bring your next show

Pick a project type and the libraries, asset types and pipeline steps are ready from the first upload. Your structure grows with the show, and nobody has to clean it up afterwards.