Built toward a first assembly suggestion.

Awaire is being built to review prepared rushes locally against your brief, references and storyboards, and surface useful moments, structure and a reviewable first path through the cut. We're validating this end to end during controlled access.

Behind the workbench, Forge Engine prepares the media and Anvil Engine is being built to review it. Source media stays unchanged. The editor decides what to use.

Awaire works locally.·Engines behind the workbench.·Editor decides.

Awaire is in controlled validation. We onboard projects in small batches so setup, data handling, and workflow feedback are handled properly.

awaire · workbench
  • LOCALMedia handling validated per onboarding.
  • EVIDENCESource media unchanged.
  • REVIEWEditor reviews before use.
  • RECORDEvidence model under validation.
Network behaviour validated per projectSource media unchangedEditor reviews before useEvidence model under validation
§ 00 · Workbench previewAwaire v0.4 · controlled validation build
§ 01 · Workflow

Short loop. Editor in control.

Awaire is being built around a short loop — start with the drive and brief, and return a reviewable first assembly suggestion with evidence. We're validating this end to end during controlled access.

  1. STEP · 011/6
    Drive arrives

    Approved rushes land on local storage.

    Editor review
  2. STEP · 022/6
    Brief added

    Brief, references and storyboards set the target.

    Editor review
  3. STEP · 033/6
    Awaire prepares media

    Awaire prepares review media and proxies locally.

    Awaire workbench
  4. STEP · 044/6
    Awaire reviews rushes

    Awaire is being built to review prepared rushes against the brief.

    Awaire workbench
  5. STEP · 055/6
    Editor opens suggestion

    A reviewable first path through the cut. Not a finished edit.

    Editor review
  6. STEP · 066/6
    Evidence shows what happened

    Local records capture what was prepared, with review and proposal records as those stages come online.

    Awaire workbench
§ 02 · Inside the workbench

The workbench, surface by surface.

A look at Awaire across the workflow — Prepare, Review, Assemble, and Evidence. These representative previews show the product direction for the unified workbench; today Forge runs as its own local prep app/tool, and Review/Assemble/Evidence behaviour remains under controlled validation.

Prepare · Forge Engine
Review · Editor surface
Assemble · Anvil Engine
Assemble · Anvil Engine
Evidence · Editor surface
§ 03 · Inside Awaire

Two engines. One product.

Awaire is the product surface. Behind the workbench, Forge Engine handles media preparation and Anvil Engine handles editorial intelligence. One Awaire licence includes both.

Forge Engine01

Media preparation behind Awaire.

Forge Engine prepares review media and proxies locally and keeps a local job record for every run. Recursive watch folders are in development, and Resolve-enabled RAW-to-proxy preparation remains gated behind validation proof before live automated rendering claims.

  • —Local proxies and review media
  • —Source media unchanged
  • —Local job queue, logs and preparation records
  • —Recursive watch folders (in development)
  • —Resolve-enabled RAW-to-proxy preparation (validation-gated)
Part of AwaireSee Forge Engine →
Anvil Engine02

Editorial intelligence behind Awaire.

Anvil Engine is being built to help Awaire review prepared rushes against the brief, references and storyboards, and surface useful moments, structure, an assembly suggestion and evidence. Anvil's analysis is in controlled validation.

  • —Brief, references and storyboards guide review
  • —Useful moments and standouts (in development)
  • —Evidence-backed first assembly suggestion (in development)
  • —Editor reviews before use
Part of AwaireSee Anvil Engine →
Current boundary

Today Forge exists as Awaire's current standalone local prep app/tool. The Forge to Anvil handoff is the product direction and integration contract for the Awaire workbench, being validated carefully rather than claimed as a fully live automated flow today.

§ 04 · Local-first by construction

Built to keep your media on your machine.

Local-first workbench
Awaire runs on the workstation and is designed to keep media on local storage. The workflow does not require cloud upload.
Source media unchanged
Awaire prepares review-safe outputs from approved media. The original files stay read-only and are not overwritten.
Editor decides what to keep
Awaire surfaces useful moments, standouts, and previews from the rushes. The editor decides what stays.
Draft-only before export
Edit plans, shot orders, and frame choices stay proposals until the editor exports. Nothing leaves the workbench on its own.
Plain-English local record
Steps are designed to write a local record of what was prepared, read, and proposed. Reviewable end to end, on the workstation.
§ 05 · Access

Controlled validation. Onboarded in small batches.

Awaire is in controlled validation. We onboard projects in small batches so setup, data handling, and workflow feedback are handled properly. Tell us about your project and we'll send the validation pack and schedule a working session.

Next step