Pipeline
Every issue gets a traceable path to a merged PR. It moves through named agents and a fixed set of states, from intake to a merged pull request.
See the pipeline Product
From issue to merged PR. Every step on record.
Colony runs the lifecycle of an engineering issue — from intake, through analysis and implementation, to a reviewed, merged pull request. Colony runs its own development on this pipeline — 2,500+ merged PRs all-time — and has been in production with an enterprise customer since October 2026.
What shipping looks like — our own pipeline The receipts you can verify are public. The full ledger and audit trail are at /built-by-colony/.
2,500+ PRs merged · all-time Through Colony’s pipeline on Colony’s own development.
250,000+ Lines of TypeScript Shipped, reviewed, merged through the pipeline.
10,000+ Tests, green Unit, integration, end-to-end.
$2.06 Median cost per PR · last 30 days Tokens plus worker time, attributed per merged PR — rolling window from the live ledger.
Features
What Colony does, by area.
Each card leads with what you get, then how Colony does it.
Governance
Your engineering standards hold at machine speed. Review checks, merge controls and conventions enforcement keep them in force.
See governanceObservability and ledger
You can see what each issue cost and who did what. Per-issue cost attribution, an audit trail and a public ledger of Colony's own development.
See observabilityDeployment
Run Colony where your security posture needs it. Self-host on your infrastructure or run it managed in Colony Cloud.
Compare self-host and cloudWorkflows
Fit the pipeline to your process, not the reverse. Start from the default workflow, adapt it in a versioned file your team reviews, and extend it with an Apache-2.0 SDK, plugins and MCP.
See workflowsIntelligence
Agents that learn from past work. On Colony's own repositories, a deterministic Code Map, post-issue lessons from the Chronicler, semantic retrieval into agent prompts, and self-improvement tracks run today.
See intelligenceStrategist
Goals and risk limits set by the operator; the Strategist turns them into a weekly plan. On Colony's own repositories, it re-plans from pipeline signals and work inside the charter envelope ships automatically; anything bigger escalates to a person.
See the StrategistEverything on this page ships today and runs Colony’s own development.
How we’d measure your pilot
Six metrics. Read together.
We do not publish outcome ranges we cannot defend. Here are the six numbers we will put in your pilot contract — and the mistake to avoid when reading them. Commitment ranges live on the pilot page, where they belong.
Throughput
Issues closed per week, measured per active repo. Same team size, vs. your pre-Colony baseline.
Cycle time
Median time from issue filed to PR merged, on Colony-handled work. Reported per repo, weekly.
Cost per issue
Tokens plus worker time, attributed per issue. Visible in the same ledger your engineers see — not a separate finance dashboard.
Escape rate
Defects that originated in Colony work, divided by Colony PR count. Read against your pre-Colony defect baseline.
Agent attribution
Share of issues handled end-to-end without human steering. The number that says how much of the pipeline is actually autonomous.
Review cycles
Number of inspect-rework loops before a PR clears. Trends toward one as the conventions file stabilizes.
The most common mistake is optimizing for one metric in isolation. Throughput up and escape rate up means broken code shipping faster. Read the basket.
What changes for your team
Four human roles. The titles you have already.
Colony expands your team. The four roles below describe how work flows once the pipeline is running — activity-based, drawn from the titles you already have. A person can fill more than one; on small teams, one person fills all four.
Briefs the pipeline.
Common fit PMs, BAs, product designers, sometimes engineers.
Holds the quality gate.
Common fit Developers, tech leads, architects.
Maintains the colony.
Common fit Senior engineers, architects, platform teams.
Charters the rollout.
Common fit Engineering managers, directors, VPs of engineering.
Most adoption work in the first ninety days is concentrated in two places: Authors learning structured issue writing (three to four weeks; the LLM-assisted drafting workflow shortens it), and Operators tuning the conventions file from real review feedback. The other two roles read the dashboards.
Want to see how this would land in your team? Talk to us.
Pilot scope back in two business days. Fixed-fee, time-limited, yours to walk away from.