The cloud side never touches your storage
It holds the board, the tasks and the record of what happened. It has no route to your drives and no credentials for them.
How it works
Two pieces, and your footage never leaves your building
One part runs in the cloud so the board opens anywhere. One part runs inside your facility and watches your storage. What travels between them is facts, never files.
Runs in the cloud
- the board and every view of it
- tasks, handoffs and notes
- a record of everything that happened
- who can do what
what it sees ↑↓ settings
Runs in your building
- your drives and masters
- your media system
- transcodes and delivery
- your logins, which stay here
What that means in practice
Four rules your IT person will ask about
The program in your building only sends out
It does not open a port and does not accept connections. Nothing new is exposed to the internet, which is usually the question your IT person actually wants answered.
Your logins stay with you
The credentials for your own storage and media systems live in your facility and are never uploaded.
It sends facts, never media
That a master exists. That a file landed. That a cut was updated. Never the file itself.
Confirmed, or worked out
Every card says where its information came from
Some dates are confirmed — a program in your building watched the file land. Some are estimated from the air date and your show’s schedule.
Both are useful. Mixing them up is not. So the board never quietly blends the two: it labels each card, every time, rather than putting a key in a corner that nobody reads.
If the program in your building goes offline, the board switches those cards to estimated and says so. It does not mark them missing, and it does not go blank.
What happens when a connection drops →Q-1058RB
TAILGATE WEEK
Q-1059AL
TAILGATE WEEK
Q-1060DV
HOME MAKEOVER
Q-1061CS
HOME MAKEOVER
Q-1062AL
SUMMER GETAWAY
Standards note outstanding
Q-1063RB
SUMMER GETAWAY
What is optional
You can start with none of it connected
The board works on its own. Everything that reaches into your facility is a step you can take later, or never.
- The program in your building — optional. Without it, dates are estimated rather than confirmed, and the board says so.
- A version source — optional, and not an Avid feature. Avid MediaCentral, a PilotWare export, a nightly export or a pasted list all feed the same handoff check. Without any of them, handoffs show as not checked rather than verified.More on this →
- Slack — optional. Activity works with nothing connected at all. If you do use Slack, messages post there too.
See it on a real board
The demo is the actual software, running on a made-up show. Nothing to install, no sign-up.
Walkthroughs are with Kevin Kelsey — 15 years an assistant editor, Children's & Family Emmy-nominated, and the person who built this. More about him.