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.
Blueprint turns a screen into a portable JSON contract you own and render yourself — server-driven UI, without shipping an interpreter to the browser or handing your work to a vendor. It's how you ship the flows that carry weight — onboarding, payments, anything that has to stay auditable — as a file you control, not a black box.
How it works · one contract, from the Builder to the browser
Builderdesign & validate
Export contractportable JSON you own
Store it anywhereS3 · Local · CDN
Your frontend
client orchestrationblueprint · runtimerendered- fetch the page request
- take the response envelope
- resolve the SDUI route
- render the page — no eval
request →
← envelope
Your backend
SDUI orchestrationblueprint · SDK- handle the API request
- run your logic — DB · auth · policy
- retrieve the contract by URL
- bind your data with the SDK
- compose the envelope
Design and validate the screen in the Builder.
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.