Enterprise
Your archive
has more to say.
Years of town halls, interviews, webinars and productions are loaded once and stay addressable, word by word. From then on, a written brief comes back as a finished edit, every segment carrying source timecodes.
This page is written for the reader who checks. Each capability below prints its real limit, and everything still on the roadmap sits in its own section, in the future tense.
2,000 to 10,000+ archive hours · annual packages
Group C contributed nothing - the plan lists every segment it did use, with its source group and timecodes, so what was left out is visible.
In the platform now.
Seven capabilities, each printed with the limit or the exact surface the platform gives you. Anything you cannot find here is either on the roadmap below or does not exist.
The library persists.
Source groups are ingested once: each group transcribed from its reference recording with word-level timecodes, every angle registered, every speaker separated. A group stays addressable after the project that loaded it ends, so the next brief starts from everything already there.
TRANSCRIPTS: SEGMENTS · WORDS · SRT · VTT
Found by what was said.
A brief reaches any sentence spoken on camera, because retrieval runs on the word-timecoded transcript. Material surfaces by meaning across the groups a brief names - up to four at a time.
BRIEFS UP TO 2,000 CHARACTERS
Composed across videos.
One brief draws on up to four source groups at once. Segments interleave across years and rooms, ordered to carry the argument, with repetition cut.
UP TO 4 GROUPS PER BRIEF
Multicam, held together.
A source group carries up to four synchronised angles of one session, lettered A to D and treated as a single recording.
UP TO 4 ANGLES PER GROUP
Speakers, named.
Diarisation separates the voices in each group; you attach display names once. Every speaker carries talk time and sample quotes, so a plan can say who is speaking and for how long.
DIARISED · TALK TIME · QUOTES
Provenance, attached.
Every plan lists its segments with source timecodes before anything renders. Finished edits ship with SRT captions, an EDL in JSON and a QC report.
SRT · EDL JSON · QC REPORT
Driven by your systems.
The full workflow is callable: a REST API, an MCP server for agents, and webhooks that announce when sources are ready and renders land.
REST · MCP · 6 WEBHOOK EVENTS
How a brief becomes a plan and a plan becomes a render is a page of its own - what composition means here →
Named, not shipped.
Enterprise conversations ask for these four by name. All are planned; none is in the platform today. Beside each one is what stands in for it now.
PLANNED
Rights-aware exclusion
Rights and licensing metadata will attach to sources, and planning will leave out material whose rights have lapsed.
TODAY The platform reads no rights fields; clearance stays with your records.
PLANNED
Library-level permissions
Libraries will carry their own access lists, so a team will see its groups and nothing else.
TODAY Access is account-wide; roles govern settings, billing and membership.
PLANNED
Learned editorial memory
The platform will learn a house style from the edits you approve and carry it into new plans.
TODAY Style is explicit: a brand kit applies your fonts, colours, logo and end card at render.
PLANNED
Speaker-tracking crop
Vertical output will follow the active speaker through the frame.
TODAY 9:16 renders with the full frame letterboxed, or with stacked crops.
Three sizes, printed in full.
Annual packages fix three quantities: the archive hours you load, the people in the account, and the finished work that leaves each month. For Team and Archive, the figures below are the contract's figures; Network is sized to the organisation.
| Package | Archive hours | Users | Compositions a month | Annual |
|---|---|---|---|---|
| Team | 2,000 hours | 10 | 250 | £18,000 |
| Archive | 10,000 hours | 30 | 750 | £36,000 |
| Network | Custom | Custom | Custom | £75,000+ |
Onboarding
The work is front-loaded by design: load it once; create from it repeatedly. For smaller deployments, onboarding is included in the package. Where implementation work is needed, it is scoped before contract and runs £2,500 to £15,000.
Your footage stays yours.
Media sits in private storage under your account, the sub-processor list is short and named, and every second of output traces to source timecodes. The details are written down where procurement can cite them.
- ASSEMBLYAI · EUAUDIO, BY SIGNED URL
- ANTHROPICTRANSCRIPT SEGMENTS + BRIEF
- SUPABASEMEDIA AT REST · DATABASE
- FLY.IO · LHRCOMPUTE
The full list, including billing and email vendors, is on the security page.
Questions
- What does “enterprise video archive search” mean on this page?
- Loading footage into persistent libraries where every word is transcribed with word-level timecodes, then retrieving moments with a written brief. What comes back is a composed, source-grounded edit carrying source timecodes on every segment, with up to four source groups feeding one brief.
- How much footage can we load, and in what form?
- Packages are sized by archive hours: 2,000 on Team, 10,000 on Archive, custom on Network. Files upload at up to 16 GB and four hours each, up to four cameras to a source group, in mp4, mov or mkv, with wav, mp3, m4a and aac for audio.
- Can we restrict a library to one team?
- Not yet. Access is account-wide today, with roles governing settings, billing and membership. Library-level permissions are on the roadmap, and this page keeps them in the future tense until they ship.
- How do we audit what an edit used?
- Before a render, the plan lists every segment with its source timecodes, so review happens before the allowance is touched. The finished edit ships with an EDL in JSON naming each segment's source and timecodes, SRT captions and a QC report, and webhooks can log every render into your own systems.
- What does onboarding involve and cost?
- Loading the archive once, so every brief afterwards starts from it. For smaller deployments onboarding is included in the package; where implementation work is needed, it is scoped before contract and runs £2,500 to £15,000.
Hear the rest of it.
A demo runs against real footage and ends with a plan you can read, source timecodes included.
Team · Archive · Network - annual packages