# AgentRun

> Updated 2026-09-24 · type: tool · category: workflow-automation · status: active · rev 1

AgentRun is a JSON/TypeScript DSL from Parcha-ai for turning repeatable AI-agent work into orchestrated, typed workflows.

- Open source: yes (Apache-2.0)
- Self-hostable: yes
- Pricing model: free
- Best for: An engineer who runs the same AI-agent process repeatedly and wants it expressed as a typed, orchestrated workflow rather than ad-hoc prompt glue — and is comfortable adopting a beta with little traction.
- Last verified: 2026-09-24

- **Canonical:** https://gtmstacker.com/registry/tool/agentrun/
- **Source:** [Parcha-ai · GitHub](https://github.com/Parcha-ai/agentrun)
- **Tags:** workflow-automation, mcp-agents, self-hostable, dsl, orchestration
- **Repository:** https://github.com/Parcha-ai/agentrun

## Is AgentRun open source?

Yes, AgentRun is open source under the Apache-2.0 license.

## How much does AgentRun cost?

AgentRun is free to use.

## Can I self-host AgentRun?

Yes, AgentRun can be self-hosted (the source is available under the Apache-2.0 license).


---

AgentRun is a workflow DSL from Parcha-ai — expressed in JSON or TypeScript — for turning repeatable AI-agent work into orchestrated, typed workflows. It ships beta npm packages and is self-hostable under Apache-2.0. It is brand-new: created 2026-09-23, only 20 stars, and explicitly beta, so treat it as an early bet rather than a settled orchestration layer.

## Provenance

- Apache-2.0 (OSI-open); 20 stars, created 2026-09-23, last push 2026-09-24 (two days old); a workflow DSL in JSON/TypeScript for orchestrated, typed agent workflows, with beta npm packages published and self-hosting supported (WebFetch 2026-09-24).
- Surfaced via studio discovery in the 2026-09-24 pass.
- Anti-hype note: this is a genuine permissively-licensed release, but it is two days old, beta, and carries only 20 stars — presented as an early bet, not a proven or widely adopted orchestration layer.
- Curated from the GTM Stacker signal registry (2026-09-24 pass); license/facts independently verified 2026-09-24.

## Why it matters for a GTM stack

Most agent work in a GTM team starts as a one-off prompt and never becomes a repeatable process — the enrichment run, the outbound-draft pass, the lead-scoring loop each get rebuilt by hand. AgentRun's pitch is the orchestration layer for that: express the repeatable agent process once as a typed workflow (in JSON or TS), then run it as a defined pipeline instead of ad-hoc glue. For a RevOps or growth engineer, that is the difference between a clever prompt and an operable process you can version and re-run. The honest read: it is two days old, beta, and has 20 stars — the idea is well-placed, but the plumbing is unproven, so pilot it on something non-critical before you build a GTM process on top of it.