Runsight

Runsight

Open-source YAML workflow engine for Git-native AI agents with per-run cost tracking and built-in eval.

36/100At RiskFreeFree

Runsight is a refreshingly practical choice for teams that manage AI agents like software. Git-native workflows, block-level cost tracking, and a built-in eval framework give you real control and reproducibility. However, if you need a fully managed cloud with zero setup, look elsewhere—self-hosting is the price of that transparency.

Verified 2d ago · liveness 36/100 · cite: rightaichoice.com/tools/runsight

Best for
  • Developers building multi-step AI agent pipelines
  • Teams needing granular cost visibility for agent runs
  • Organizations requiring Git-based workflow version control
  • Engineers designing evaluation and regression tests for agents
Not ideal for
  • Non-technical users who prefer no-code only interfaces
  • Users needing a fully managed cloud service with zero setup
  • Those requiring built-in model hosting or proprietary AI models
Visit Website

IntermediateFor a developer familiar with YAML and Git, you can have Runsight running your first workflow in under 5 minutes using the quickstart. Writing a custom workflow with souls and tools may take 30-60 minutes. Setting up complex loops and sub-workflows with eval assertions could take a few hours to a day.CLI · WebAPI availableVerified 2d ago
Pricing
Free
FreeFree tier4 hidden costs
Learning curve
Intermediate
For a developer familiar with YAML and Git, you can have Runsight running your first workflow in under 5 minutes using the quickstart. Writing a custom workflow with souls and tools may take 30-60 minutes. Setting up complex loops and sub-workflows with eval assertions could take a few hours to a day.
Runs on
CLIWeb
API available
Who it's for
Developer building a multi-step research pipelineDevOps engineer embedding agent workflows in CI/CDAI engineer testing agent reliability
Live sentiment
Is Runsight actually worth it?

We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.

  • Honest verdict, not marketing
  • Real pros & cons from real users
  • Attributed quotes with receipts
Run a free scan

3 free scans · no card needed

Skip it if

Skip Runsight if you want a fully managed cloud service with zero setup, if you need pre-built integrations to external tools, or if you're not comfortable managing your own API keys and infrastructure.

The 30-second take
Biggest gripe

Self-hosting requires your own infrastructure, so you'll bear the cost of running the service and ensuring uptime and security—there's no managed option.

Price reality

Runsight is free (Apache 2.0) and self-hosted, making it cost-effective for startups and developers who already have infrastructure and API keys. Compared to managed platforms like Langfuse or agent studios that charge per usage, Runsight eliminates platform fees, though you'll invest in setup and maintenance.

In short

Runsight — Open-source YAML workflow engine for Git-native AI agents with per-run cost tracking and built-in eval. Best for Developers building multi-step AI agent pipelines, Teams needing granular cost visibility for agent runs, Organizations requiring Git-based workflow version control. Free to use.

Viability Score

36/100
At Risk

How well maintained and how widely used is Runsight? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this

Recent activity
not measured
Traction
20
Site health
95
User sentiment
not measured
What the vendor publishes
0

Last calculated: September 2026

How we score →

Key Features

  • YAML-first workflow definitions
  • Git-native version control (every save is a commit)
  • Visual canvas editor
  • Monaco YAML editor with dual-view sync
  • Per-run cost tracking per block
  • Hard budget caps (max_cost, max_tokens)
  • Built-in evaluation framework with assertions
  • Transform hooks for structured extraction
  • Offline eval test harness
  • Pause and kill agent execution mid-run
  • Loops with break conditions
  • Sub-workflows and nested orchestration
  • Souls (agent identities: role, prompt, model, tools)
  • Custom tools (HTTP, Python, file-based)
  • Self-hosted with your own API keys

About Runsight

FreeIntermediateAPI availableCLI · Web

Runsight is an open-source, Apache 2.0-licensed workflow engine that lets you design, version, and run AI agent pipelines as YAML files stored in Git. Instead of scattering agent logic across Python scripts, you define workflows in a readable YAML format that lives in your repository—so every change is diffable, reviewable, and revertible like any other code. This makes Runsight a fit for developer teams who treat agent behavior as code and want to collaborate through branch, review, and merge cycles. A key differentiator is the duality between a visual canvas and a Monaco-based YAML editor—both stay bidirectionally synced. Drag nodes on the canvas and the YAML updates; edit YAML and the canvas reacts. Every workflow is a file on disk, and every save is effectively a commit, enabling Git-native version control. Runsight also tracks per-run cost per block, including latency, and lets you set hard budget caps (max_cost and max_tokens) that automatically kill execution before overspend—no surprise bills. The built-in evaluation framework uses assertions on block outputs, with transform hooks for structured extraction and regression testing across runs. You can pause, inspect, and resume or kill agents mid-run. The engine supports loops with break conditions, sub-workflows as child steps, and hierarchical orchestration. Runsight is self-hosted: it runs on your machine with your own API keys and models, and nothing leaves your network unless you choose to send it. Compared to fully-managed agent platforms like Langfuse or agent studios, Runsight requires you to handle your own infrastructure and API keys, but for developer-focused teams already using Git, it's a transparent, lock-in-free alternative that puts your data and config in your hands.

Behind the Verdict

Runsight's core strength is its developer-first philosophy: workflows as YAML files in Git. This approach turns agent behavior into reviewable, diffable, and revertible artifacts, enabling standard code review practices. The bidirectional sync between visual canvas and Monaco editor lowers the barrier for those who prefer GUI, while still keeping everything in a text format that machines and humans can track. Cost tracking per block with hard caps (max_cost, max_tokens) directly addresses the common pain of runaway API costs. The eval framework using assertions and transform hooks supports regression testing, giving teams confidence beyond 'looks good'. Where Runsight falls short is operational overhead: you must self-host, manage your own API keys, and handle scaling and security. There are no pre-built integrations beyond custom tools in YAML, so you'll need to write custom tooling for external services. The community is early, so support relies on docs and GitHub issues. For a fully managed experience with low setup, you'd be better off with a platform like Langfuse or an agent studio that offers cloud hosting. But for developer-centric teams already invested in Git, Runsight offers transparency and lock-in avoidance that heavier managed platforms often trade away.

Researching Runsight? Get your full AI stack in 60 seconds.

Free, no signup — tell us your goal and get tools matched to your budget & existing stack.

Real-world workflow fit

Concrete scenarios for the personas Runsight actually fits — and what changes day-one when you adopt it.

Developer building a multi-step research pipeline

You define a workflow in YAML with a linear research block, a gate review block, and a publish block, using souls for analyst and editor roles. You set a max_cost of $2.00 and run it locally.

Outcome: The pipeline executes, each block traces its cost and latency, the gate validates the research output, and the workflow either passes to publish or loops back to research based on assertions. You commit the YAML to Git and track every change.

DevOps engineer embedding agent workflows in CI/CD

You add a Runsight workflow to your repository and run it as part of a CI pipeline, using the offline eval harness to validate blocks before deployment.

Outcome: Workflows are versioned in Git, reviewed like code, and executed in CI with budget caps preventing runaway costs. Eval assertions catch regressions early, ensuring only vetted workflows are promoted.

AI engineer testing agent reliability

You design a workflow with a loop that refines outputs until a condition is met, using assertions on block outputs to verify quality. You run it across multiple test cases.

Outcome: The loop iterates with break conditions, cost accumulates per iteration, and assertions flag failures. You use the eval harness to run regression tests, gaining confidence in the agent's behavior before deployment.

Use Cases

Models Under the Hood

analysteditorsenior-analyst

as of 2026-09-02

Limitations

  • Runsight is self-hosted and requires you to manage your own API keys and infrastructure.
  • There is no managed cloud service, so uptime, scaling, and security are your responsibility.
  • Integrations are currently limited to custom tools defined in YAML, with no pre-built connectors to external services.
  • The tool focuses on workflow orchestration; it does not include model hosting, training, or a marketplace of ready-made agents.
  • The learning curve is steeper than no-code platforms, and the community is still early, so you may need to rely on docs and GitHub issues.

as of 2026-08-31

Verification history

We have re-verified Runsight 5 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.

  1. re-checked, vendor evidence unchanged
  2. re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
  3. re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
  4. re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
  5. re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it

Free to cite with attribution — this page re-verifies continuously.

12-month cost

Project the real annual outlay, including the implied monthly cost when only an annual tier is published.

Annual total
Free
Over 12 months
Effective monthly

Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.

Plans compared

For each published Runsight tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.

Open Source

$0

Ideal for

Developers and startups who want full control, are comfortable with self-hosting, and need to track costs and eval without licensing fees.

What this tier adds

Starting tier: free, Apache 2.0 licensed, fully self-hosted with all features included, no paid upgrades.

Hidden costs & gotchas

What the public pricing page doesn't put in bold. Captured from pricing-page footnotes, contract terms, and recurring complaints.

  • Self-hosting requires your own infrastructure, so you'll bear the cost of running the service and ensuring uptime and security—there's no managed option.
  • API costs from your own model providers (e.g., OpenAI, Anthropic) are not included; you pay for every model call your workflows make.
  • While the core is free, custom tool development to connect external services requires engineering time and may necessitate paid add-ons.
  • No official support; you rely on community and GitHub issues, which may slow down troubleshooting for critical workflows.

Where the pricing makes sense

The company stage and team size where Runsight's pricing actually pencils out — and where peers do it cheaper.

Runsight is free (Apache 2.0) and self-hosted, making it cost-effective for startups and developers who already have infrastructure and API keys. Compared to managed platforms like Langfuse or agent studios that charge per usage, Runsight eliminates platform fees, though you'll invest in setup and maintenance.

Setup time & first value

How long it actually takes to get something useful out of Runsight — broken out by persona, not the marketing-page minute.

For a developer familiar with YAML and Git, you can have Runsight running your first workflow in under 5 minutes using the quickstart. Writing a custom workflow with souls and tools may take 30-60 minutes. Setting up complex loops and sub-workflows with eval assertions could take a few hours to a day.

Switching to or from Runsight

How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.

Migrating in
  • From Python scripts: Convert each script's logic into YAML blocks, define souls and tools, then run and validate with assertions.
Migrating out
  • To Langfuse: Export your YAML workflows and migrate to their managed environment if you need cloud hosting and built-in integrations.

Resources & Guides

Tutorials & Learning

Official links

Featured Head-to-Head Comparisons

Popular in Agent Frameworks & Orchestration

Temporal AI

Temporal AI

Durable execution platform keeping AI agents and workflows running through failures with automatic state capture and retries.

FreemiumTry
DBOS

DBOS

Durable execution for AI agents and workflows on Postgres

FreemiumTry
Sakana AI

Sakana AI

Autonomous multi-agent AI orchestration built in Japan for regulated enterprises

Contact SalesTry

Frequently Asked Questions

Used Runsight? Help shape our editorial sentiment research.