Web

Spec → mock → Build.Sites, portals, and apps.

Marketing sites, customer portals, and operator apps from one product model — not a separate React codebase. Author once; open it as pages and journeys. Same model as Canvas, 3D, and Assistant.

Request AccessBuild in your IDE

How Web Experiences get built

The process is the product.

  1. 01

    Spec in natural language

    Describe the product in your IDE. Agents draft against live schemas — pages, binds, and policies land as DataObjects on the graph.

  2. 02

    Mock the Experience

    Compose the Web Experience from the graph: pages, components, themes, design tokens. Preview Dev / Test / Prod before you promote.

  3. 03

    Model the Workflows

    Business process, agentic, and form journeys share one runtime — forks, waits, HITL gates, and audit on the same spine.

  4. 04

    Wire Knowledge & Integrations

    Skills, files, tools, and connectors seal into systems of record you already trust. The Experience doesn't own the data — it opens it.

  5. 05

    Ship · evolve

    Goals watch Events and propose evolution. You approve. The graph versions. Change the product without rewriting three codebases.

Live proof

You’re looking at one.

This marketing site is a Web Experience on Closure — pages, theme, and CTAs authored against the same product model as customer portals and operator apps. Next proofs: self-serve portals and agency dual-skin delivery. See running portal fixtures →

Shapes of Web

Same product. Different hosts.

  • Marketing site

    Brochure and product sites — heroes, pricing, CTAs — authored on the graph for SMB and brand launches.

  • Customer portal

    Self-serve journeys — onboarding, status, payments — composed from the same components operators see.

  • Operator app

    Dashboards and internal tools with the same theme, binds, and Workflows. No shadow IT spreadsheet beside the product.

  • Partner / agency

    White-label Experiences for client delivery. Margin stays with the model, not with custom forks.

Same product as Canvas, 3D, and Assistant— four surfaces, one model.

Author the portal. Don't rebuild the stack.

Connect your IDE, draft against live schemas, and promote through the same gates every author passes.

QuickstartRequest Access