Skip to main content
New customers have been on usage-based pricing since March 27, 2026. On April 27, 2026, we moved all existing customers over from the legacy pricing plan, so everyone is now on the same plan.
Macroscope features are billed based on usage, so your costs are tied to the actual work Macroscope does reviewing and processing your code.

​
Usage-Based Prices

​
How Billing Works

Macroscope uses a prepaid usage model. Each workspace has a single balance that covers Code Review, Status, and Agent, and decreases with usage. Enable Auto-refill to have your balance top up automatically when it falls below a threshold you configure, so there’s no disruption.
Usage data in your billing dashboard may be delayed by a few minutes due to how Stripe’s metering system works.
Admins can manage auto-refill and spend controls, and view their workspace’s balance, usage history, and usage costs in Settings → Billing. To zoom into a specific date range, click and drag on the usage chart — the usage summary and breakdown tables update to match the selected window.
Go to Settings → Billing and configure your balance threshold and refill amount. We recommend enabling auto-refill to ensure Code Review and Status processing run without interruption. If your balance hits zero without auto-refill, processing pauses until your balance is topped up.
Whenever an auto-refill payment is made, you’ll receive a receipt. Your invoice at the end of your usage period will be $0 since top-ups are prepaid. You can view all receipts and invoices in Settings → Billing, powered by Stripe.
Add, update, or remove payment methods in Settings → Billing.
There can be up to a few minutes of delay in meter data due to how Stripe’s metering system works. If something still looks off after accounting for that, reach out to us at support@macroscope.com.
No.
Access continues until the end of your billing period. Your balance stays in your account. If you resubscribe, it picks up where you left off.

​
Spend Controls

You can set several limits to control your costs. Configurable by a workspace admin in Settings → Billing.
Default caps are $10 per review and $50 per PR. Both are adjustable in Settings → Billing.
If you don’t have auto-refill on and your balance runs out, all processing pauses — Agent, Code Review, and Status. Commits and PRs pushed during that window are skipped and are not retroactively processed when your balance is topped up.
Agent, Code Review, and Status processing pause for the rest of the billing period. Auto-refill does not trigger when the monthly max is hit. Commits and PRs pushed during that window are skipped.Processing resumes when the next period starts or an admin increases the limit.
Auto-refill tops up your balance but does not override the monthly spend limit. If you hit your monthly limit, processing pauses even if you still have balance remaining. They are separate controls.

​
Agent

Credits are a usage-based billing unit for Macroscope’s Agent features: Slack queries, Macros, Webhooks and Check Run Agents. 1 credit = $0.01. Credit usage is calculated by taking the raw LLM cost of each agent run (based on your prompts and parameters), then adding a 5% markup, then dividing by the value of each credit ($0.01). Every workspace includes 1000 free credits per month. Free credits do not roll over. Usage beyond the free credits draws from your balance.
Credit calculation: raw LLM cost of the agent run × 1.05 markup ÷ $0.01 per credit = credits consumed.

​
What uses credits

Code Review and Status are billed separately via their own meters. They do not consume credits.

​
Transparency

Workspace admins can view detailed Agent usage logs in Settings → Billing, including exporting a full CSV with cost and metadata for every agent invocation.
Credit usage scales with LLM cost — a quick Slack question uses fewer tokens than a complex multi-step research task, so it costs fewer credits.
Usage beyond the free credits draws from your balance, the same one used by Code Review and Status. Auto-refill and spend limits apply normally.
Yes. Go to Settings → Billing to view usage logs or export a CSV with detailed cost and metadata for every invocation.

​
Code Review

Code Review is charged per review, based on the byte size of the PR diff that Macroscope reviews.
Anytime Macroscope’s correctness check runs on a PR counts as one review. This can happen:
  • Automatically on each push to a PR (if automatic Code Review is enabled for that repo)
  • Manually, by commenting @macroscope-app review on any PR in GitHub
We pull diffs from GitHub in unified diff format (u3) and measure diff size by the raw u3 diff bytes.For the first push to a PR (or any force push), we compare HEAD to the merge base of the target branch. For subsequent pushes, we always compare HEAD to the previous reviewed HEAD.Any files Macroscope doesn’t review, such as binaries or files excluded by your .macroscope/ignore.md file, are excluded from the diff, so you only pay for the files Macroscope actually reviews.
Every review has a minimum of 10 KB. If your diff is under 10 KB, you’re charged for 10 KB. At standard pricing ($0.05/KB), that’s $0.50.
The effective dollar amount may vary if you’re on a plan with custom rates.
Most reviews are under 10 KB and thus cost $0.50. Assuming the standard rate of $0.05/KB, here are some ballpark approximations:
Yes.That said, we try to be clever and detect trivial force pushes and rebases to save you money.

​
Per-Repo Code Review Controls

Configure in Settings → Repos. Learn more about repo settings.
Skip and force-review controls apply to both Correctness checks and Check Run Agents. Skipping a PR (by label, author, target branch, draft status, or Dependabot) skips both, and a force-review label runs both — even when auto-review is off. The one exception: a Check Run Agent that defines its own authors, labels, or targets filter follows that filter instead of the repo-level skip on that axis.

​
On-Demand Reviews

Even if automatic Code Review is off for a repo, you can always invoke a review manually by commenting @macroscope-app review on any PR in GitHub.

​
Excluding Files from Code Review

You can exclude specific files from review using a .macroscope/ignore.md file. See .macroscope/ignore.md for details.

​
Status

Status is powered by per-commit summarization. This feeds your dashboards, weekly digests, productivity metrics, and sprint reports.
Code Review runs on PRs and analyzes the diff for bugs and correctness issues. Status runs on individual commit summaries and powers features like executive summaries and productivity insights. They’re separate processes billed independently.
A commit is charged after Macroscope successfully summarizes it. All branches are in scope and each commit is billed at most once.Not charged:
  • Commits pushed while your balance is exhausted or spend limit is hit (skipped)
  • Commits on repos with Status disabled
Bot commits (e.g. Dependabot, CI) are processed and billed like any other commit.
Commits on that repo won’t be summarized, classified, or included in productivity metrics. No Status charges for that repo.

​
Common Questions

Per-seat pricing charges a fixed rate per developer regardless of activity. Usage-based pricing means you only pay for what Macroscope actually processes. Teams with lighter activity pay less; teams that push more code pay proportionally more.
Yes. New workspaces receive a one-time $100 in free usage to get started.

​
Annual Discounts

If you’re interested in discounted rates, reach out and we can discuss options for annual commitments. Contact enterprise@macroscope.com.
Questions? Email support@macroscope.com or reach out in your shared Slack channel.