# Warestack vs LinearB

LinearB provides engineering metrics, workflow automation, and gitStream for PR routing. Warestack governs the full delivery pipeline — from agent instruction file enforcement to post-merge drift detection.

|   | Warestack | LinearB |
|---|-----------|---------|
| **Analytics** | DORA metrics, Cycle time breakdown, Team benchmarking, Investment allocation tracking, Delivery health scores, Agent co-authorship tracking, Natural language queries |  |
| **Automation** |  | gitStream (PR routing rules), WorkerB (team goals) |
| **Governance** | PR-level check enforcement, Agent instruction file enforcement, Custom YAML checks, Team-level policy management |  |
| **Analysis** | PR risk scoring, Intent-to-diff validation, Post-merge drift detection | Via gitStream |
| **Integrations** | GitHub | Linear / Slack / Jira, Slack, Jira, GitLab |
| **Platform** | Open-source core | Watchflow, gitStream (OSS) |

## LinearB optimizes engineering workflows. Warestack governs delivery.

LinearB is strong on engineering metrics and PR routing via gitStream. Warestack adds the governance layer that LinearB lacks — enforcing agent instruction files, validating PR intent against tickets, and providing team-level delivery standards enforcement.