ToolScanner
Workflow Builder
Every connection in its place.
An editable DAG of containerized tools and modules. Wire ports on the canvas, then run the graph.
An editable DAG. Not a black box.
Tools and modules on one canvas. Wire ports. Run the graph.
Drag. Wire. Run.
Tools become nodes. Edges carry data. The canvas is the source of truth.
Drop a tool. Get a node.
Library tools land as containerized steps with typed ports.
Wire outputs to inputs.
Connect by port schema. Data flows along the edge.
Modules nest as nodes.
Embed a whole workflow as one step. Open it to see the inner graph.
embed · reuse
Scripts are nodes too.
Python or Bash as a first-class step beside tools.
Distribute. Burst the fleet.
One node fans into parallel jobs. Managed machines scale to match.
Your library. Public or private.
Tools and scripts in one catalog. Keep private tooling in your vault.
From the canvas to the rest of your stack
Compose the graph once. Run it on managed machines. Land findings in the channels, tickets, and databases your team already opens.
ModuleDiscovery
Compose the process once
Tools and nested modules on one canvas. Reuse the same graph across workflows instead of rebuilding it.
Run it at fleet scale
Distribute a node, raise the machine budget, and let parallel jobs finish the scan while you stay on the graph.
Ship findings into your stack
Notify Slack or Teams, open Jira, write Postgres or Splunk. The run ends where your team already works.
Explore the platform
Adjacent surfaces on the same engine. Pick the next cut of the stack.
Get a personalized demo
See Trickest in Action
A 30-minute walkthrough. We map the platform to your stack and answer pricing and deployment questions for your environment.