Enterprise DNA

Instead of ftrack Studio

Stop renting ftrack Studio. Own your shot tracking.

We build your version around your pipeline steps, review rules and bids, bring your ftrack task lists across and run it for you.

ftrack Studio lists US$25 per user per month billed annually, or US$30 month to month. That is US$300 per user a year, and fifty users is US$15,000 a year before storage.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Read the invoice first

What the per-user price is really paying for

ftrack Studio prices every user who needs to track work. Most of what a producer uses it for is records and questions. Look at what you pay for before the next renewal.

group_add

A seat for every user

Studio lists US$25 per user per month on annual billing. Every artist, coordinator and supervisor you add raises the bill.

event_repeat

A premium for flexibility

Month-to-month Studio is US$30 per user per month. Short contracts and crew peaks cost more per head.

rate_review

Review-only access is still paid

The Review plan lists US$10 per user per month on annual billing, for people who only look and approve.

cloud

Storage on top

Each extra 500GB of storage lists US$25 a month per workspace on annual billing.

live_tv

Synced review as an add-on

Review Pro, for synced sessions and 4K playback, lists US$120 a month per workspace on annual billing.

request_quote

The rebate numbers still live elsewhere

Qualifying spend for the PDV Offset or the New Zealand rebate is usually rebuilt in a spreadsheet at the end of the show.

The tracking you own

Start with the questions your producers ask every day

Bids and money

See the overrun while you can still bill it

Every task carries its bid, every hour is logged against it, and every shot shows days used against days bid.

  • check Shots over bid, with the change orders that cover them
  • check Which department step runs over bid across every show
  • check Change orders raised, sent and still undecided
  • check Client cost on each change order, drafted for approval

Review

Know what is waiting on whom

Versions move from internal review to the client and back, and every client note stays open until someone marks it done.

  • check The dailies running order, oldest internal review first
  • check Versions sitting with the client past your limit
  • check Client notes still open after five days
  • check A shot approved only when every task on it is finished

Schedule

Find the fortnight that does not fit

Remaining bid days on each artist's open tasks against the working days they actually have.

  • check Artists booked past capacity in the next two weeks
  • check Tasks with nobody assigned
  • check Shots due in ten days with nothing approved
  • check Approved shots past their due date with no delivery recorded

Rebate evidence

Keep the claim straight as you go

Time is logged with where the work was done, so qualifying spend is counted the way the scheme counts it.

  • check Spend against the A$500,000 PDV Offset minimum or the NZ$250,000 New Zealand threshold
  • check The New Zealand 20 working day registration deadline
  • check Vendor costs with no invoice reference
  • check A printable spend schedule for your production accountant

Make it yours

Design your own ftrack Studio replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from ftrack Studio. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your ftrack Studio replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your ftrack Studio data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Shot Tracking for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Shot Tracking for Claude Code

Connected to your own database

Which shots have used more days than we bid?

HAR

Ot st
HAR_010_0030
Atus bi
In progress
D days ac
6.50
Tual days pc
7.25
T of bid ch
112
Ange orders
CO-101 sent

Ask it anything

Ten questions to ask your shot records

Each one has a working answer in the demo studio. Your own shows and rules make the answers yours.

chat_bubble Which shots have used more days than we bid, and does a change order cover the difference?
chat_bubble Which department's bids run light across every show we have delivered?
chat_bubble How far is each show from the PDV Offset or NZ rebate threshold, counting only in-country time at day rates and evidenced invoices?
chat_bubble Has every NZ show registered for the rebate within 20 working days of the bid being accepted?
chat_bubble Which vendor costs are missing the invoice reference we need for the rebate claim?
chat_bubble Which client notes are more than five days old and still not addressed?
chat_bubble Which versions have sat with the client longer than five days with no answer?
chat_bubble Which artists have more bid days left on tasks due this fortnight than working days to do them?
chat_bubble Which shots are due in the next ten days with no approved version?
chat_bubble Which shots are approved but past their due date with no delivery recorded?

Switching

How to switch from ftrack Studio

A move usually involves exporting task lists, mapping your fields, testing the import, and deciding separately what to do with media, review annotations, and older time history.

  1. 1

    Export your task spreadsheet

    In ftrack Studio, export the task spreadsheet as a CSV. Start with the task lists you want to bring into the new system, and check that the export includes the fields your team relies on. The available export path and contents can depend on your account, so confirm the options with ftrack Studio before you begin.

  2. 2

    Prepare and test the import

    Add your artists to the new system, then load the task spreadsheet. Run a test first so you can see what the import would change before it makes changes. The import is for task lists, not a full copy of every ftrack record. Plan separately for media, review annotations, and older time history.

  3. 3

    Review the import report

    Check the issues the test reports before you proceed. The import checks the whole file before changing anything, so use its feedback to catch missing or mismatched information. If your spreadsheet uses different column names, map those fields to the expected ones, then test again and review the results.

  4. 4

    Run both systems briefly

    Keep ftrack Studio available while your team uses the new system for a short period. Compare the imported task lists with the records your team expects to see, and confirm that the team can manage its work in the new setup. Use this period to identify any remaining data or process gaps before you stop relying on ftrack Studio.

  5. 5

    Switch off ftrack Studio

    Once you have checked the task records and your team is ready to work in the new system, stop using ftrack Studio for ongoing tracking. Make sure you have decided what to do with media, review annotations, and older time history, since those need separate work and may not come across in the task import.

construction

Where the real effort goes

The real work is usually mapping your own fields and rules, then deciding how much history to bring. Task lists can come across from a spreadsheet, but media, review annotations, and older time history need separate planning. When you have Enterprise DNA install and run it, they handle the migration work with you.

Not ready for a call?

Get your ftrack Studio switch plan by email

We will send you the step-by-step plan for moving your business off ftrack Studio, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose how much you want us to handle

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and ask for /attention
  3. 3 Export your ftrack task spreadsheet as CSV and run import ftrack with --dry-run
  4. 4 Set your day rates and rebate scheme, then run /compliance and /weekly-review
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your pipeline steps, statuses and review rules
  • check Your ftrack task lists, notes and time history brought across and checked
  • check An artist task page or a link to your review player if you want one
  • check Hooks from your publishing tools so versions log themselves
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Set up, backed up and kept running for your studio
  • check Connected to your timesheets, accounts and review player
  • check Changes made as your pipeline and shows change
  • check Run through Omni by Enterprise DNA alongside the rest of your business
Talk to Sam

Questions

Instead of ftrack Studio, answered

Does it play our shots for review? expand_more

No. ftrack includes media review, and this does not. Most studios already review in a dedicated player. Here you record the decision and the notes, and the system tracks what is waiting on whom. If you want playback linked to each version, we build that into your version.

Do artists have to change how they work? expand_more

The free version is run by the people who manage the schedule: producers, coordinators and supervisors. Artists keep working in their own tools. If you want artists to see and update their own tasks, or versions to log themselves when they publish, that is part of a custom setup.

Can we bring our ftrack projects across? expand_more

Task lists come across from a spreadsheet export after your team is added. Do a test run first. The whole file is checked before anything changes, and running it again updates the same tasks. Media, review drawings and older time history need separate work, which we plan with you before the switch.

Is the rebate figure a claim we can lodge? expand_more

No. It is a working figure for the producer and your production accountant during the show. It counts in-country time at day rates and evidenced costs against the scheme threshold, and flags the gaps. What counts toward the claim is settled with your accountant and the agency.

What does it cost to run instead? expand_more

The free version has no per-user charge. You pay for your own hosting and your coding agent subscription. If we build and run it, there is one setup fee and then a retainer. Bring your ftrack invoice and user count to the call and we will compare them honestly.

Bring your ftrack invoice to Sam

Spend 30 minutes with Sam. Bring your ftrack invoice, a task spreadsheet export and the report your producers rebuild every week. We will work out what to keep, what to build and what it takes to run your version.

Book a 30-minute call Get the free version

Shot Tracking for Claude Code is free and open source, published by Enterprise DNA.

Done paying for ftrack Studio?

Get your version built