From design to real components.
Design on the canvas. Build with Zaoly Kit. Hand off React components your team can use in other products.
Why Zaoly.
And when the others.
One table: job, pros, cons — with a clear view of where Zaoly wins for design → React building block.
| Criterion | ZaolyBuilding block | Figma | Framer | Penpot | Sketch | Webflow |
|---|---|---|---|---|---|---|
| Job | Web UI → reusable React component | UI design, collaboration, Inspect/Dev Mode | Design is the published website | Open-source design + SVG/CSS inspect | Mac-native UI design + libraries | Visual site builder + CMS / commerce |
| Pros |
|
|
|
|
|
|
| Cons |
|
|
|
|
|
|
| Best when | When design and engineering need the same React building block — not just specs or a site. | When you want to design and collaborate broadly first — and accept handoff as specs. | When the website itself is the product — landing, portfolio, campaign. | When open design and self-host are the priority — and code export is secondary. | When your team is already deeply rooted in Sketch on the Mac. | When CMS, commerce, and a hosted marketing site are the goal. |
Zaoly isn’t trying to replace Figma as a design OS or Framer/Webflow as a site publisher — it owns the step where design becomes a React building block in your product.
Less rebuilding.
More reuse.
Zaoly turns visual decisions into structured building blocks with variants, design tokens, and code, so design and development can keep working from the same source.
Don’t just read.
Try it.
Five public demos here — full interaction at /explore. App links go to /editor, /kit, and /tokens (sign-in).
Illustration · not the live editor
Design becomes the language of a product.
for ideas.DESIGN
Selection: Heading · HOME · Canvas
Illustration · lenses · pages · layers · canvas hotspots.
Text, links, buttons, and badges carry meaning — without them a layout stays silent.
Text: Typography and paragraphs. Seed atom — foundation for every layout composition.
Text · Content · 37
Content · Layout · Page — full catalog on Explore.
#7457D8 · 2 uses
Catalog · toggle color · click cards.

Desktop 1440
Zones · tabs · tap the illustration to cycle widths.
Design
Tabs · tap scene details · next-step button.
Three lenses.
Canvas, Masters, Preflight — illustration here; full demo on Explore.
The system.
At work.
Three real views with sample data — no mockup, no suite requirement.

Token paths connect values to components in the editor.

Kit atoms, TSX, and live preview sit side by side.

Multi-breakpoint compare on the canvas.
One building block.
As many projects
as you need.
Your projects have different goals. Well-made components can still live on in more than one context.
for ideas.A module for stories.Landing
in view.Same structure. New context.Dashboard
move on.Ready for the next product.App shell
Handoff
without guesswork.
Turn a visual building block into a React module with imports, token context, and guidance for integration into other React projects.
Many places.◇
Marketing example · not a seed atom
01import { Stack, Text, Button }02from '@zaoly/site-kit'0304export function FeatureCard() {05 return (06 <Stack>07 <Text>One idea. Many places.</Text>08 <Button>Explore</Button>09 </Stack>10 )11}Let’s talk about
Zaoly.
Planning a team rollout, want to learn about hosting and AI features, or have questions about developer handoff? We’ll help you find the right next step.
hey@zaoly.appMake more of
your next
design.
Design today what keeps working as a component tomorrow.
Get started