Agent pipelines deserve software discipline

Arestrix treats a pipeline as a program: designed, versioned, compiled and packaged like anything else in production.

Beta 2 · 2.0.0-beta.1 · Windows and Linux. Beta APIs, file formats and command-line flags may change before general availability.

Built for the people who run it

The Studio is for the person who designs the graph. The runner is for the person who has to operate it.

  • Platform engineers

    Need agent workflows on managed Windows endpoints without shipping a Node or Python runtime to every machine.

  • Security teams

    Cannot put provider keys in project files or send prompts to a multi-tenant automation service.

  • Operations

    Want a standalone runner with a clear progress screen, an integrity check and no IDE.

  • Researchers and educators

    Need a reproducible, local example of agent orchestration that can be inspected end to end.

  • IT and release managers

    Want MSI/MSIX packaging and artifacts they can review, version and sign off.

How it works

  • Design visually

    The graph is the source of truth: agents, tools, decisions and feedback loops on one canvas, validated before a run starts.

  • Compile natively

    Arestrix generates C++20 and compiles it with Taskflow. You can read the code, diff it and build it outside the Studio.

  • Distribute as software

    Export a standalone runner with an HMAC integrity manifest, then package it as MSI or MSIX for managed Windows deployment.

A deliberate scope

What Arestrix is not

  • A hosted automation service that keeps your projects and prompts
  • An Electron app with a browser runtime on every endpoint
  • A prompt UI that produces no artifact you can review
  • A workflow interpreter that hides the execution model
  • A place to store provider keys in the project file
  • A closed format you cannot diff or version