One repository, every modality
Video, image, audio and documents in a single store, with the source you uploaded and the finished artifact kept together rather than scattered across the tool that happened to produce each one.
Assets & Storage
Vitra Intelligent Asset Manager
Every AI tool is an island, so the work between them is export, download, re-upload, and a filename with v3_final in it. The Intelligent Asset Manager is the repository underneath Universe: every upload, every intermediate artifact and every finished asset lives in one place, and workflows start from a file already there rather than from one you moved.
Free to start · 75+ languages · No credit card required
Capabilities
What Asset Manager does
Workflows start from the asset
Select a stored file and launch dubbing, translation, creation or personalization directly from it. There is no export step, because the file is already where the workflow runs.
Intermediate artifacts are first-class
A transcript, an extracted audio track, a translated design file — each is stored as an asset in its own right, so the next workflow consumes it instead of regenerating it.
Bring your own S3 bucket
Point the asset manager at your own AWS S3 bucket, so assets live in your account, your region and under your lifecycle and retention rules. Storage becomes yours while the workflows stay managed.
Every capability reads the same store
Video dubbing, video creation, image translation, image creation and personalization all resolve assets from here, which is what removes the download-and-re-upload step between them.
Lineage you can follow
Each derived asset records what it came from, so a dubbed cut traces back to its master and a localized banner to the design file it was built from — without relying on a naming convention.
Organization-scoped access
Assets are scoped per organization with role- and entitlement-based access control, so an agency can hold a separate library per client and reviewers see only what their role permits.
Reachable from your own systems
Assets are addressable over MCP, REST API, SDK and CLI, so a DAM, CMS or pipeline you already run can deposit files and trigger the workflow that consumes them.
How it works
Four steps, one orchestrated run
Every stage runs on the same platform, so nothing is exported, re-uploaded, or handed between tools.
- 01
Land the source once
Upload, or connect your own S3 bucket and let existing files be addressed in place. This is the only transfer in the whole chain.
- 02
Launch work from the file
Start any Universe workflow directly against a stored asset — no export, no re-upload, no local copy that immediately goes stale.
- 03
Intermediates stay available
Transcripts, stems, extracted layers and translated files are written back as assets, ready for the next step or for a different workflow entirely.
- 04
Finished artifacts land beside their source
Every output returns to the same library with its lineage recorded, so the master and its forty market versions live together rather than in forty download folders.
Who it is for
Teams using Asset Manager
Kill the upload-download loop
A campaign that touches five AI tools normally means five uploads and five downloads per asset. Here the file is uploaded once and never leaves.
One master, many markets
The source video, its transcript, its 40 dubbed versions and their subtitle tracks stay in one place with the relationships intact.
Agencies with client libraries
Separate, access-controlled libraries per client under your own branding, with your own storage if you want the data in your account.
Regulated retention
Assets in your own bucket inherit the region, lifecycle and retention policy you already had approved, instead of a vendor's defaults.
FAQ
Questions people ask
What problem does the Intelligent Asset Manager actually solve?
The transfer tax between tools. Producing one localized campaign across separate AI products means exporting from each and importing to the next, which is slow, duplicates every file, and leaves several versions of the truth. When the store sits underneath the platform, the workflow starts from the asset and the transfer disappears.
Can I launch a workflow directly from a stored asset?
Yes — that is the point of it. Select a file already in the library and start dubbing, translation, creation or personalization against it. Nothing is downloaded or re-uploaded, and the output returns to the same library.
What is an intermediate artifact?
Anything a workflow produces on the way to its result — a transcript, an extracted audio track, a translated design file. Each is stored as an asset in its own right, so a later workflow reuses it rather than regenerating it, which saves both time and the cost of the second generation.
Can assets live in our own storage?
Yes. Connect your own AWS S3 bucket and assets are held in your account, your region, under your lifecycle and retention rules. That keeps residency and retention decisions with you while the workflows remain managed.
Does this replace SharePoint, Google Drive or Dropbox?
Inside the content production loop, yes — those tools are usually where creative assets sit only because there was nowhere better, and the constant export-import between them and each AI tool is the cost. It is not a general corporate file store, and it is not trying to be your intranet or your document management system.
How does it relate to a DAM we already run?
It complements rather than replaces one. Assets are addressable over MCP, REST API, SDK and CLI, so an existing DAM can deposit files and trigger the workflow that consumes them, and finished artifacts can be pushed back to it as the system of record.
Who can see which assets?
Access is scoped per organization with role- and entitlement-based control, so an agency can keep a separate library per client and a reviewer sees only what their role allows. Combined with your own bucket, both the boundary and the storage stay under your control.
Start with Asset Manager. Grow into the whole platform.
Everything in Vitra Universe shares one translation memory, one brand kit, and one quality bar — so the work you do here makes everything you do next faster.