The Trickest platform

The operations center for security execution.

Agents plan. Workflows define the graph. Fleets run it. Results stay queryable.

Four primitives. One workspace.

Editor, runtime, results, and apps share the same graph and the same run history.

Editable workflows

Tools and modules on one canvas. Wire ports. Keep the graph visible.

Fleet execution

Managed pools or enrolled hosts. Parallelism is a run budget, not a rewrite.

Structured results

Outputs land in tables and files attached to the run, not scattered logs.

Shareable apps

Turn a workflow into a web app with the SDK already wired to its outputs.

Connect

Start where you sit.

trickest · connect
$ curl -fsSL https://trickest.io/install.sh | sh
$ trickest auth login
$ trickest attach
$

@trickest/sdk

The typed client your agents already know how to call.

One npm package, native fetch, no HTTP client to wire up. The whole platform behind a typed API that your coding agent can reach through the CLI, SDK, and MCP.

trickest · integrate · Cursor
$ curl -fsSL https://trickest.io/integrate | sh -s -- --client cursor
src
lib
srclibruns.ts
import { TrickestClient } from "@trickest/sdk"
 
const t = new TrickestClient({
token: process.env.TRICKEST_TOKEN,
})
 
// Boot a full workflow run on a managed fleet.
const run = await t.runs.execute(workflowId, {
fleet: "asm-fleet",
inputs: { domain: "northstar.io" },
})
 
// Re-execute one node. Upstream deps memoized.
const partial = await t.runs.execute(workflowId, {
node: "httpx",
})
 
// Pull a single node's output files.
const output = await t.runs.getNodeOutputFiles(
run.id,
"findings",
)
app · findings

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.