App · Assets

Output-driven asset status, with comments built in.

Every asset has a status, an output tag, and a comment thread. Override which task types complete which outputs per asset. Get AI naming and tagging suggestions when you create something new.

assets.layerline.co
Screenshot · Asset Management
The problem

What this app solves.

Asset state lives everywhere except in one place. The 3D file is almost done, the texture lives in someone else's Drive, the producer thinks it's shipped, the reviewer hasn't seen it yet. There is no single answer to whether the asset is ready.

  • 01 No single status across modeling, texturing, rigging, animation
  • 02 Files and reviews live in different tools than the asset record
  • 03 Naming chaos — hero_v3_FINAL still happens
  • 04 Producers can't see what's blocked without DMing artists
Features

Built for the way teams actually work.

01 · feature

Asset CRUD with custom statuses

Define the statuses your team uses (Not Started, In Progress, Review, Complete) per project. Move assets through them as they progress.

create_asset · update_asset · get_asset_statuses
02 · feature

Output overrides per asset

Most modeling tasks complete a "modeling" output. But this hero asset needs three modeling tasks plus a separate cleanup task. Override per asset, and the status rolls up correctly.

update_task_output_overrides
03 · feature

Threaded comments with @mentions and file refs

Comment directly on the asset. Mention teammates, attach files from Storage, reference other assets. The thread is the asset's review log.

create_asset_comment · list_asset_comments
04 · feature

AI naming and tagging suggestions

When you create a new asset, Layerline suggests a name and tags based on the project's vocabulary. Skip the naming-convention argument.

asset-suggestion.service.ts

One OS. Every app. Yours.

Start free. No credit card, no procurement loop. Scale to a studio when you're ready.