Postil vs Macroscope

A neutral default is advisory until configured

Macroscope Check Run Agents default to a neutral conclusion ceiling, and GitHub branch protection cannot block on a neutral check. Macroscope Approvability can also be configured to conclude failure as a required status check, so the product can gate merges when a team opts into that mode. Postil makes the gate a separate pass/fail check from the start: require postil/gate in branch protection while postil/review stays advisory. 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 charges by diff size

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. Its docs describe most reviews as under the minimum, or $0.50, with a 30 KB medium feature at $1.50. Two pricing models in six months. To its credit, Macroscope offers spend caps, but the structure still charges you more for bigger changes and more PRs. Postil prices private plans by active author. BYOK provider usage is billed directly. Hosted starts with a 30-day trial. See the pricing details.

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, so you can audit restraint continuously rather than relying on a single launch-post benchmark.

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 an option.