For media teams
Years on tape,
answerable with its sources shown.
A media operation's archive is its institutional memory, and most of it cannot be consulted under deadline. Anjin Media runs a video archive for media teams as working infrastructure: sessions indexed to the word, speakers named, and desk requests answered as composed edits you can defend, not merely publish - every segment carrying its source timecodes.
Retrieval runs on meaning, briefs name their sessions, and nothing reaches an edit without a line in the plan.
One video or an entire archive.
Media teams product demonstration
The problem
The archive only one person can search.
Every long-running operation has the colleague who remembers - which town hall the chair said it at, roughly when, possibly on which drive. Retrieval by tenure works until the deadline is today, the request is three years deep, and that colleague is on leave. So the archive gets consulted for anniversaries and obituaries, and the daily output is cut from whatever is recent.
The waste compounds quietly: interviews re-shot because finding the original costs more than filming again, claims paraphrased because the clip that proves them cannot be produced in time, a body of material that appreciates in value while depreciating in reach.
The general workflow - index once, create repeatedly - is walked through on the archive-to-content page →
Retrieval by meaning
Any sentence said on camera, reachable.
Indexing is the once-only investment: each session is transcribed with word-level timecodes, its voices diarised, its speakers named by you a single time. From then on the session answers questions - who spoke, for how long, in which words - before anyone scrubs a frame. Multicam sessions load as one group, supported camera angles held together.
Requests arrive as briefs and name their sessions, up to four at a time. That scoping is editorial discipline as much as engineering: what comes back is checkable against exactly the material it drew on, which is the difference between search results and something a producer can stand behind.
The transcript itself is a first-class product - pull it as text segments, word-level JSON, SRT or VTT, for research, subtitling or the archive's own records.
Governance
A posture stated in two tenses.
Media organisations evaluate archive tools with governance questions first, so this page answers in the platform's actual tenses. Today: media sits in private storage under your account, behind signed URLs; the sub-processor list is short and named; deleting a source group purges its media from storage; and access within an account is account-wide, with roles governing settings, billing and membership.
On the roadmap, and stated only as roadmap: library-level permissions, so a desk will see its own groups and nothing else; and rights metadata, so planning will leave out material whose licence has lapsed. Until they ship, teams draw hard boundaries by running separate accounts, and clearance stays with your records.
Every render's provenance is already present tense: the plan before it, the EDL and QC report beside it. An editor can audit any edit back to its sources without asking anyone.
The route in
Capacity for your organisation’s work.
One organisation or a group
Start with the production and archive needs of your organisation. Enterprise can also cover a group, with paid licences and the units they cover named in the quote.
Capacity sized to the work
AI and supported multicamera recordings are included. Your quote specifies source minutes, export minutes and active storage for each account. Every camera consumes source minutes.
Clear account boundaries
A quote can arrange central billing for a group, with usage specified for each account. Extra brands or accounts do not create licences or allowance, and usage is not pooled across accounts.
Enterprise is for a single organisation with higher usage or archive requirements, as well as groups of organisations. Your quote defines the paid licences, the units they cover and usage for each account. One company can be one quoted unit; departments or locations do not automatically require separate licences. A group can be billed centrally; extra brands or accounts do not create licences or additional allowance. Usage is not pooled across accounts.
Existing subscribers keep their contracted plans and archive terms. Archive onboarding and support requirements are agreed in your quote.
Discuss your requirementsThe full capability split - shipping today against roadmap - is on the enterprise page; data handling, vendors and the claims we do not make are on security; self-serve plans for smaller teams are on pricing.
A demo runs against your material and ends with a plan on the table, source timecodes included.
The objections
What the standards editor asks.
- Some of our masters carry third-party rights - we cannot use a tool that ignores that.
- Then know exactly what this one does: nothing, yet. The platform reads no rights fields today; rights metadata is on the roadmap and this page will not pretend otherwise. What it offers meanwhile is control at two gates - a brief only draws on the sessions it names, and the plan lists every segment with its source before anything renders - so cleared material can be loaded and worked, while clearance itself stays with your records and your process.
- Who inside the organisation can see what?
- Everyone in the account can reach the account's libraries - that is the honest answer today. Roles restrict settings, billing and membership, and the API restricts keys by scope, but not by library. Where a boundary is non-negotiable now, deployments run separate accounts on either side of it, and library-level permissions are the roadmap item that will fold those back together.
Questions
- What is a video archive for media teams, in this platform's terms?
- A library of indexed sessions that stays addressable. Each session is transcribed with word-level timecodes and its speakers are diarised and named; a written brief then draws on up to four named sessions and returns a composed edit whose every segment carries its source timecode range. Renders ship with SRT captions, an EDL in JSON and a QC report.
- Can we find what someone said on camera years ago?
- If the session is in the library, yes - retrieval runs on the transcript, so a brief reaches any sentence spoken in the sessions it names. The speaker index helps you point it well: each session lists its named speakers with talk time and sample quotes before you write a word.
- How is access to the archive controlled?
- Plainly: access is account-wide today. Roles govern settings, billing and membership, and media sits in private storage behind signed URLs - but the platform does not yet restrict who inside an account sees which library. Library-level permissions are on the roadmap; teams needing a hard boundary now run separate accounts either side of it.
- What does an archive deployment cost?
- Enterprise can serve one media organisation with higher source footage, export or storage needs, or a group with explicitly quoted paid licences and account allowances. Onboarding and archive requirements are agreed in the contract. Existing archive subscribers keep their contracted terms.
Make the archive answerable.
Bring one shelf of it to a demo: a town hall, an AGM, a panel. Ask for something specific, and read what comes back.
Custom Enterprise usage, archive and licensing quotes