Archon vs Rocky

Archon is an open-source workflow engine and harness builder for AI coding agents, built by indie developer coleam00. It addresses the non-determinism problem at the heart of LLM-based coding: the same prompt doesn't always produce the same result, making agentic coding pipelines unreliable in production. Archon solves this by defining development processes — planning, implementation, validation, code review, PR creation — as structured YAML workflows that run consistently across projects and environments. Each task gets an isolated git worktree, automatic test execution is baked in, and PR creation is handled as part of the workflow rather than an afterthought. The YAML-first design means workflows are version-controlled, diffable, and reviewable by teams — treating the agent process as code rather than a black box. Archon also positions itself as the first open-source tool for building deterministic AI programming benchmarks, giving researchers a reproducible harness for evaluating coding agents. For solo developers, Archon provides guardrails that make autonomous coding agents safe to run unattended. For teams, the YAML workflows create shared standards for how AI contributes to codebases. The core limitation is that you still need to write the workflows — there's no auto-discovery, and complex multi-repo setups require careful YAML construction. But as a free, open-source foundation for reliable agentic coding, it fills a real gap.

Rocky is a Rust-based SQL transformation engine that brings software engineering discipline to data pipelines. Where tools like dbt gave data teams a version-controlled workflow, Rocky goes further: type-safe compile-time SQL, column-level lineage visualization, git-style branches for isolated testing, and a built-in AI intent layer that stores your purpose as metadata alongside the code. The branching feature is the standout — you can create a branch, run it against an isolated schema, inspect the results, then drop or promote. The column-level lineage shows the full downstream blast radius before you ship a change, tracing any single column back through every aggregation and join to its source. This is the kind of visibility that prevents the "who broke the revenue dashboard" post-mortems that happen in every data team. The AI intent layer is genuinely novel: it stores what a model is supposed to do as metadata, so AI can later explain models, auto-update them when upstream schemas change, and generate tests based on the original intent. Rocky integrates with Dagster via an official plugin and supports DuckDB for local development with no credentials required. With Hacker News coverage and a Rust-native architecture, it's positioned as the data pipeline tool for engineering-forward teams who are tired of YAML-based transformations.