Build
Follow along
The platform
Platform · The suiteOne workspace for components, portals and tools.See the platform See pricingComponents, Tools, Pricing and Docs are in the bar — nothing is duplicated here.
The next version of this suite is one integrated development experience: a library agents can consume, a designer they can build in, and hosting they can ship to — with you directing, from brief to live site, without leaving the workspace.
Everything in the library ships as data an agent can consume, not just a page a human can read. Components carry anatomy docs and raw source routes; templates ship as fully static Astro with a manifest that hands over finished, importable pages.
The goal is Claude native in the workspace: composing from the library, importing templates into the Terminal designer, and iterating on the canvas — the same surfaces you use, driven by an agent you direct.
Shipping should not be a context switch. A Vercel MCP and native Vercel and Hostinger connections put provisioning, deploys and domains inside the same workspace the site was designed in.
If a human can browse it, an agent can consume it — components, templates, tokens and docs all exist as structured routes, not screenshots.
Code to canvas and back without degradation. Templates are written to a static contract the designer imports exactly, so what ships is what was designed.
An agent should be able to take a brief, compose from the library, assemble pages in the designer and put the result on a domain — without leaving the suite.
Vercel and Hostinger as first-class connections: deploys, previews and domains readable and drivable from the workspace, by you or by an agent.
Libraries and templates share one catalog, so a component learned once is known everywhere — by every surface, every product and every agent in the suite.
Every step above lands on the roadmap first and in the changelog when it ships.