About Cadrix

AI workflows a company can actually oversee.

Cadrix is a governed workspace where teams design AI workflows on a visual canvas, run them with full tracing and human approvals, and keep control through roles and access settings.

What Cadrix is

One place to build, run and oversee.

Most teams can get an AI prototype working. The harder part is running it for a whole company: knowing what it did, who approved it, which data it touched and who is allowed to change it.

Cadrix puts those concerns in the product instead of around it. You design a workflow on a visual canvas, connect it to your own knowledge and tools, and run it with a trace of every step. Where a person should decide, you add an approval. Who can build, run or administer is set with roles inside each workspace.

  • Visual canvas. Agents, tools, conditions and loops laid out as a flow your colleagues can read.
  • Tracing. Each run is recorded step by step so you can inspect, retry and re-run it.
  • Approvals. A workflow can pause and wait for a person before it continues.
  • Roles and workspaces. Separate workspaces, role-based permissions and API keys.

You can read more on the product and governance pages.

Principles

How we think about the product.

Short, and meant as commitments to hold ourselves to rather than slogans.

01

Governed by default

Access, history and approvals are part of the workflow itself, not an add-on you bolt on later.

02

Show your work

If a workflow did something, you should be able to see what, in which order and with which inputs.

03

People stay in the loop

Automation handles the routine. Decisions that matter can be routed to a person before anything happens.

04

Your data, your keys

You connect your own model providers and tools. Credentials are stored encrypted rather than in plain workflow definitions.

05

Say only what is true

We describe what the product does today. Where something is not built or not verified, we say so on the security page and elsewhere.

06

Clear for non-engineers

A flow should be legible to the operations lead or the auditor, not only to the person who built it.

See it on your own use case.

Start on the free plan, or tell us what you want to automate and we will walk through it with you.