fig. 00 · the real product: its parts fly in from off screen and assemble in no set order1920 × 1080

Partly live when I left·My last product at Vitra.ai

Vitra Universe: four products, one platform, one agent

My role: Product designer · Solo
Company: Vitra.ai
Year: 2025–2026
Platform: Web app

Vitra sold four AI products. Universe is the agentic platform that brought them in as modules of one product, with one shell and one set of rules, and an agent, Cosmos, that can do the work in any of them. I was its only designer.

# 01 / Problem

Problem: scattered tools

Vitra sold four AI products: Translate.video, Image translation, Hyper personalization and Translate.website. A customer using three of them had three logins, three file libraries and three credit balances. Nothing was the single source of truth.

Translate.videoown login
own files
own credits

Image translationown login
own files
own credits

Hyper personalizationown login
own files
own credits

Translate.websiteown login
own files
own credits

one customer, four places to look

01One customer, four products, four places to look

# 02 / Constraint

The constraint: surfaces we already had

Most screens came from the products customers were already using. The job was to bring them in, not redraw them, while a junior designer kept the four standalone products running for customers who hadn't moved yet.

So the platform had to hold surfaces it didn't originally design, and still read as one product.

# 03 / Solution

Solution: one shell, many modules

Every module sits in the same shell: a module rail, a page panel and Cosmos on the right. What used to be duplicated in each product now exists once.

03Live. Cosmos picks a video from Assets and starts the dub

03Live. Cosmos adds a term to the Smartphone launch glossary, English source and Spanish target

03Live. A file dropped on Cosmos goes straight into Assets with /save

03Live. Plain words in Cosmos become a report: September credits by organization

# 04 / Agent

One sentence, start to finish

A localisation lead has a launch talk to ship: dubbed into Spanish, subtitled in French. Before Universe that meant two products and a dozen screens. Now it's one message to Cosmos.

An agent that acts across a whole platform has to be easy to check. So every request goes through the same five moments, and they held everywhere Cosmos works.

Reads the requestnowThe video, Spanish and French show as chips before it’s sent.
Plans, then asksnowTwo jobs become a plan. Nothing runs until you press Run.
Shows its worknowEach step says what it’s doing while it does it.
Acts where the work livesnowBoth processes land in Dubbing, like rows made by hand.
Hands it backnowEach result links to what it made. One Undo takes it all back.

04Live. One message, two processes: dub into Spanish, then subtitles in French

# 05 / System

One system

Four products only read as one if they share the small things. Every answer Cosmos gives is built from the same parts as every module: the same buttons, badges, type and surfaces, at the same sizes.

05Live. The product's own components; every size is measured from them

# 06 / Status

Where it stood

When I left, Universe was partly live: some customers and modules were on it, and migration was under way.