Agents that already know your business
Drag-and-drop workflows that read your documents, follow your rules, and call the tools you already use.
Drag sideways to see the whole diagram
Example: a contract-risk agent, four steps on the canvas.
The builder as it ships
Drag from the library. Connect on the canvas. Configure inline. Hit save.
The library, the canvas and the node inspector in one view.
Thirty-one platform components in six colour-coded groups, plus connectors for Xero, iMIS, SharePoint, Jira, Confluence, Obsidian, Notion, WordPress and Drupal. Drag any tile onto the canvas.
Pan, zoom, branch and merge. Auto-tidy straightens a tangled flow, and the minimap shows where you are in a large agent.
Every node declares what it takes in and what it gives back, so bad wiring is caught before you run. Upstream values are referenced inline by node id.
No pile of modals. Every node's settings live on the node: schema picker, prompt editor, dialect, temperature, validation.
A live overview of the whole flow. Click anywhere to jump there.
Run the agent end to end against real or mocked inputs. Every node shows its input, output and cost, and you can diff a run against the last one.
Versioned releases, instant rollback, and a webhook or CLI hook for every agent. Same builder, your perimeter.
Most agent builders reach for your data last
Certant starts there.
Every agent starts with everything you have connected: contracts, policies, records. So instead of "fetch this row, send that email", the agent can decide: "is this contract risky? If it is, send it to the risk team and say why."
Build it, code it, test it
Code when you need it. UI when you don't.
Most of it is drag, connect, run.
Edge cases, anywhere in the flow.
Prove a step before it touches production.
What people build with it
Pick a job and see the whole flow: every branch, every sub-tool, every integration.
Templates to start from
Every agent starts from a template or a blank canvas; the builder follows your system theme.
he template chooser: 26 workflows available.
What comes in, what the agent does, what goes out.
Every component, one canvas
Thirty-one platform components and nine connectors. Click a tile to see what it does and when to use it.
How it is governed
Pause the agent, ask a person, and resume exactly where it stopped.
SecurityEvery node takes JSON in and gives JSON back, so there are no surprise blobs to parse.
ArchitectureBring a job you keep doing by hand.
Point an agent at it and watch what it reads before it acts.
Contract 2026-114 scored 4 of 5 for risk. It is with the risk team, and nothing has been sent to the vendor.
