Postil vs Macroscope

A neutral check cannot protect a branch

Macroscope's check runs complete with a neutral conclusion (per its docs), and GitHub branch protection cannot block on a neutral check. That makes its findings advisory by construction, whatever severity they carry. Postil completes postil/gate as a real pass/fail check you can require in branch protection, separate from advisory postil/review commentary. On operational errors the gate fails closed by default; repos can opt into gate.onError: advisory, which fails open on provider outages only.

Per-kilobyte billing puts a meter on your diff

Macroscope launched in September 2025 at $30 per developer per month with a five-seat minimum, then flipped to usage-based pricing in March 2026: $0.05 per kilobyte of diff with a 10 KB minimum, around $0.95 to $1.50 for a typical PR. Two pricing models in six months. To its credit, Macroscope offers spend caps and $100 of credit for new workspaces, but the structure still charges you more for bigger changes and more PRs. Postil charges a flat $10 per developer per month and routes inference through your own key at provider rates with zero markup; your worst-case bill is seats times ten. Compare on the cost calculator.

Precision claims vs a standing metric

Macroscope's V3 review claims 98% precision and 64 to 80% fewer nitpicks (self-published benchmark, in a category where every vendor benchmark ranks its own author first). We make no counter-claim about whose findings are more precise. The difference is the reporting: Postil publishes its silence rate, the share of PRs where it said nothing, as a standing dashboard number on your own traffic, not a one-time benchmark result, so you can audit restraint continuously instead of trusting a launch post.

Where Macroscope is ahead

Macroscope builds an AST and reference graph across several languages, giving it structural context a diff-first reviewer does not have. It ships quickly (check-run agents and a CLI both landed in May 2026), and its usage pricing includes spend caps, which several usage-priced competitors lack. If you are entirely on GitHub Cloud and want its codebase-understanding features, it is a serious product. If you are on GitLab, Bitbucket, self-managed anything, or need code to stay inside your network, it is not currently an option.