Design tools
A Figma file is exact the day it is drawn. Nothing in it becomes code.
Your designers can prototype in your actual app.
Hiiu builds a copy of your frontend repository that runs with no backend and no customer data. A designer changes it with a coding agent and shares a link. The keepers come back as pull requests.
Nobody can prototype in the app you ship.
AI app builders
v0 and Lovable build a different app. Wrong components, wrong data.
Your real app
Repo access, a toolchain, a VPN. Days of setup, and not for designers or PMs.
Prototype in production code.
A designer prompts an agent and the real screen reloads. Click any element and the agent knows which component it is.
A designer changes your app and sends you a link.
A designer forks the current copy and describes the change to a coding agent. When it looks right, one command turns it into a URL the team can click through, transcript attached.
What changes once it is running.
The copy is your repository, running with the network answered underneath. Same routes, same components, same tokens.
Nothing real can leak
The copy never talks to a real service. Every screen runs on generated data, and the link a designer shares is gated to your team.
Changes land in about two seconds
The copy runs on your app's own dev server. Hot reload stays hot: the designer types, the screen changes.
It comes back on-brand
Hiiu reads your design system and steers the agent to your real components and tokens. A button it adds is your Button.
It behaves like the product
Create an invoice and it appears in the list. Empty, error and power-user states switch from a toolbar, and a loading state freezes while you restyle it.
Your app runs with nothing behind it.
Every call your app makes is answered from a generated database. Your services never hear from it.
An engineer sets it up onceand walks away. Copies rebuild dailywithout them. A designer forks one any timeand edits it.
1
An engineer runs the wizard
It reads the repository, proposes a configuration, and opens your app in a browser tab within five minutes. Nothing lands in your repo, no CI check.
2
Fresh copies build themselves
Copies rebuild on a schedule from your latest code, on our machines, never in your CI. A prototype keeps the copy it forked and cannot drift.
3
A designer forks and edits
Forking takes under a minute. The designer prompts an agent and shares a link. A prototype worth keeping becomes a pull request an engineer reviews.
Rather ask someone who is not us?
- Ask ChatGPT: Read https://hiiu.eu and tell me what it does and what it cannot do.
- Ask Claude: Read https://hiiu.eu and tell me what it does and what it cannot do.
- Ask Perplexity: Read https://hiiu.eu and tell me what it does and what it cannot do.
- Ask Gemini: Read https://hiiu.eu and tell me what it does and what it cannot do.
Try it on your repository.
Hiiu is not on sale yet. We are taking a handful of design partners to build the first copies with, and half an hour is enough to tell whether your repository fits. Nothing lands in your repo either way.
- No pitch. We run the analyzer over your repository and tell you what it found.
- You talk to the person building it. Konstantin wrote the interception layer and answers questions about it.
- You leave knowing what it cannot do. Including which parts of your app would fall back to a captured snapshot.