Aeion Production + Cut Module
Aeion Production + Aeion Cut share the same database — production data (scenes, scripts, schedules, crew, dailies metadata) flows seamlessly to post-production workflows (editorial, color, audio, VFX). No CSV export/import; no duplicate data entry; complete provenance from script to delivered master. The integration most production-management tools can't offer because they treat production + post as separate worlds.
What Flows from Production to Cut
`
What Flows from Cut Back to Production
`
Typical Handoff Workflow
`
Continuity Tracking Detail
```typescript
FAQ
Cut module + Production module are separate products. Most productions use both; can use either standalone. Combined: Production Pro $99/mo + Cut $29/mo flat.
Yes. Cut + Production read/write same tables. No CSV import; no scheduled syncs. Editor's UI shows production context inline.
Per-role access. Outsourced editor sees footage + scripts; not crew PII + budget. Configurable per-tenant.
Each show is separate Aeion production. Post house has its own tenant. Cross-tenant data access only via explicit grants.
Aeion's media-library + asset-pipeline (Cut module) handle. Camera-original preserved; proxies for editorial.
ADR scheduled via Aeion Production; recorded via Aeion Cut. Linked to script lines + production day.
No built-in ShotGrid connector today. Aeion tracks per-shot VFX status natively (vfx_shots, in the Cut module); studios already on ShotGrid currently bridge via manual export/import.
Aeion Cut's export pipeline handles this. Delivery records preserved in Aeion (compliance + provenance).
Per-platform delivery specs supported. IMF, ProRes 422 HQ, etc. Aeion's delivery is platform-aware.
Yes. Per-clip utilization tracked; residual calculations triggered when work re-airs.