Blueprints
A blueprint is your application: a graph of nodes, drawn on the Blueprint Editor canvas, that reads sensors, processes their data, and sends results to the cloud. Deployed to a bundle, it runs on every device that bundle contains — see How the pieces fit together for where a blueprint sits relative to devices, bundles, and fields.
Create a blueprint
Click Blueprints in the sidebar
Click New Blueprint at the top of the screen
Choose how to start
Start from Scratch
An empty canvas you build yourself.
-
Choose Start from scratch and click Next.
-
Enter a name and click Create Blueprint.
The canvas opens empty, ready for you to drop prefabs onto it and wire them together.
Nodes, edges, and prefabs
The canvas is built from three related pieces:
- A prefab is a reusable node template — either built into PRIZM or made custom for your company. It defines what inputs, outputs, and node constants a node built from it will have. The Blueprint Editor’s left panel is this library; you drop a prefab onto the canvas to use it.
- A node is one block on the canvas — a placed copy of a prefab, with its own node constants (a threshold, a topic name, a format string) and typed input and output ports.
- An edge is the line you draw between two nodes. It carries data from an output handle on one node to an input handle on another, and is what turns a set of nodes into a pipeline.
Some prefabs talk to hardware directly and are peripheral-aware — their peripheral (baud rate, IP address, and so on) is configured when you deploy, not on the node itself, see Deploying a blueprint.
Add a prefab to the canvas
Click + on the canvas toolbar
Search or browse for a prefab, then select it
Prefabs are grouped by category. Selecting one adds it to the canvas as a node.
Deploying a blueprint
Click Ship
Pick the bundle to deploy to and click Save & Deploy
Every device in that bundle starts running the compiled blueprint.
The rules that govern what deploy targets, how many apps a bundle runs at once, and what a late-joining device receives all live on the Bundles page — this page owns the canvas, not the deploy mechanics.
