Forge Engine is the media-preparation engine behind Awaire. The live handoff into the wider workbench is product-direction work under controlled validation, not a claim that today's Awaire app is already the control surface for Forge job execution.
RAW-family handling remains behind validation gates and is not offered as a live automated render path until those gates pass. Source media stays unchanged. In Awaire, Prepare/Verify is the intended review surface for what has proof, what remains bounded, and what still needs review.
Forge Engine is Awaire's media-preparation engine. Local proxies and review media today — watch folders and Resolve-enabled RAW in development.
Resolve-enabled RAW preparation is in development. The target is to route supported camera RAW workflows through DaVinci Resolve Studio on a workstation where Studio is installed, licensed, and running. RAW-family handling remains gated behind validation proof before it is offered as a live automated render path.
Resolve Studio required where used · Validation-gated workflows only · Source media unchanged · Local job records
The current state of post automation.
- 01Watch folders limited to one level deepBLOCKED
- 02Proxy workflows locked inside single UIsBLOCKED
- 03Limited control over ProRes and DNx profilesBLOCKED
- 04Automation that breaks when RAW appearsBLOCKED
- 05Enterprise systems disproportionate to the taskBLOCKED
One local prep tool. Repeatable operator-grade output.
- 01Recursive folder scanning (in development)LOCAL TOOL
- 02Resolve-enabled RAW routing (in development)LOCAL TOOL
- 03Saved settings for repeatable prep runsLOCAL TOOL
- 04Runs locally on your hardwareLOCAL TOOL
- 05Local records · failures with a reasonLOCAL TOOL
Four validation behaviours Forge Engine is built around.
Design targets and current behaviours visible in the local preparation record during controlled validation.
Repeatable prep settings
The same input and saved preparation settings produce the same intended output, so a proxy or transcode run can be repeated deliberately.
Failures with a reason
If a job fails it fails clearly — with a reason, the file it stopped on, and the rule it broke. Nothing is dropped silently.
Verified before exposed
Outputs are written into a temporary output area first. They only appear in the deliverable folder once they have been checked.
Plain-English local record
Every job writes a clear local record: what went in, what came out, when, on which workstation. Editors can see what happened.
Operators who own the output.
Post-production teams
Tired of babysitting proxy jobs and manually checking outputs at 11 pm.
Facilities
Running mixed-format ingests where silent failure is not an option.
Technical operators
Set a job up once. Walk away. Trust the result.
Operator UI. No surprises.
Representative source-panel preview showing folder hierarchy and multi-camera roll structure. RAW detection and Resolve-enabled routing remain under gated validation.
Representative destination preview. Prepared output roots are designed to keep the production structure where required.
Representative encode-settings preview. Codec, settings, burn-ins, and container controls are designed for repeatable proxy and validation-stage transcode runs.
Representative queue preview. Status-led runs block failures rather than hiding them, and validation-stage records are kept locally.
Controlled access during validation.
Awaire is in controlled validation. We onboard projects in small batches so setup, data handling, and workflow feedback are handled properly. Forge Engine is included — customers buy Awaire.