Your brand, your domain
The platform runs on your own custom domain with your logo, your palette and your primary brand colour. Your customers sign in to your product, not to a reskinned one.
Partners & Agencies
Vitra White Label — Run Universe as Your Own Product
Reselling someone else's platform usually means reselling their brand, their storage, their model vendors and their invoice. White Label inverts that: your domain, your branding, your provider keys, your S3 bucket and your translation memory, with you deciding which capabilities your customers ever see.
Free to start · 75+ languages · No credit card required
Capabilities
What White Label does
Your email identity
Branded email templates sent through your own SMTP credentials, so notifications, invitations and reports arrive from your domain rather than from a vendor your customer has never heard of.
Your model providers, your keys
Bring your own API keys for LLMs, image generation, video generation and TTS. Inference runs on your accounts, under your commercial terms, against vendors you have already assessed.
Provider preferences per workflow
Choose which provider serves which workflow rather than accepting one default everywhere — the model that wins on dubbing is rarely the one that wins on document translation.
Your own storage
Supply your S3 access key, secret and bucket configuration, and every artifact is stored in your account. The Intelligent Asset Manager runs directly on your bucket, so the repository your customers use is infrastructure you own.
Your own memory
A translation memory scoped to your organization, built from your customers' work — with Phrase and XTM selectable where an external TM should stay the system of record.
Your own org structure
Members, roles, permissions, teams, team members and credits are all yours to define, alongside your company details, so the tenancy behaves like a product you built.
Expose only what you want to sell
Pick which features and products each customer can see, and compose custom workflows on top. Your catalogue does not have to be our catalogue.
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
Claim the tenancy
Your organization is created with your company details, custom domain and brand kit — colours, logo and primary brand colour applied across the product.
- 02
Connect your own infrastructure
Add your provider API keys, your S3 credentials, your SMTP settings and your translation memory. From here, data and inference sit on accounts you control.
- 03
Shape the product
Decide which capabilities are exposed, define roles, teams, permissions and credit allocations, and build any custom workflows your service depends on.
- 04
Sell it as yours
Onboard your own customers as sub-organizations, each with their own members, entitlements and assets, under your brand end to end.
Who it is for
Teams using White Label
Agencies
Offer localization and content production as your own capability rather than reselling a logo your client can look up.
Language service providers
Add AI throughput under your existing brand and keep the linguist review, the memory and the client relationship where they already are.
Services and systems integrators
Deliver a content capability inside a larger engagement, on infrastructure that satisfies the client's own vendor and residency requirements.
Multi-brand enterprises
Run separate tenancies per brand or per region, each with its own storage, memory, entitlements and credit budget.
FAQ
Questions people ask
What exactly can be branded?
The custom domain, the logo, the colour palette including your primary brand colour, and the email templates — sent through your own SMTP credentials so mail comes from your domain. Company details are yours throughout, so the tenancy reads as your product rather than a themed version of someone else's.
Can we use our own AI model providers?
Yes. Bring your own API keys for LLMs, image generation, video generation and TTS, and inference runs on your accounts under your commercial terms. Provider preferences then let you choose which provider serves which workflow instead of applying one default across all of them.
Where are our customers' files stored?
In your own S3 bucket, if you want them there. Supply the access key, secret and bucket configuration and every artifact is written to your account, in your region, under your lifecycle rules. The Intelligent Asset Manager operates directly on that bucket.
Do we get our own translation memory?
Yes. Memory is scoped to your organization and accumulates from your customers' work, so the reuse benefit belongs to you. Phrase and XTM are selectable per organization where an external TM should remain the system of record.
Can we control which features our customers see?
Yes, per customer. Choose which capabilities and products are exposed and compose custom workflows on top, so you can sell a focused service rather than the full catalogue, and price it however your business requires.
How are users, teams and credits handled?
Members, roles, permissions, teams and team members are defined by you, with credits allocated across them. Each of your customers can be a sub-organization with its own members and entitlements, isolated from the others.
How is this different from the enterprise deployment options?
White Label is about commercial identity — running the platform as your own product for your own customers. The enterprise page covers the security and deployment posture underneath it: tenant isolation, residency, the audit ledger and fully air-gapped installs. Most partners need both, and they compose.
Start with White Label. 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.