Blueprint SDK
Fills a contract with your data and returns a portable envelope — server-side, no eval.
Learn moreHow it works
From contract to screen. No black box.
Four honest steps, one artifact you own. You design the contract in the Builder, your frontend fetches it, your backend answers with an envelope, and the client renders it — logic stays in typed, reviewable React.
01
Builder
Design & validate the contract, then export portable JSON you own.
02
Your frontend
The user opens a URL — read params, orchestrate, fire the fetch.
03
Your backend
Your web service handles the request and composes the envelope.
04
Client handles response
Receive the envelope and render the page — no eval.
Follow the contract from the Builder to the browser.
Blueprint
An open contract and a thin runtime you host — it maps nodes to your components.
Learn moreBuild it visually. Own the JSON. The Builder is a self-hosted editor for your Blueprint contracts — drag atoms, validate live, and export the screen.
Learn moreDrag-and-drop canvas
Assemble screens from the atom palette — no code, with a live preview.
Typed inspector
Every prop is a validated control — you can't export an invalid contract.
Own your export
Export portable JSON and self-host the runtime. No lock-in, no black box.
Why it matters
No step in this pipeline ships executable code to the browser. The contract describes structure, the SDK binds data, and the runtime maps nodes to components — so every screen stays auditable, CSP-clean, and yours to run. Logic lives where it belongs: in typed, testable React.