Pricing that fits before your first deploy.
From $10 per seat/mo (or $8/seat/mo billed annually). All prices are in Canadian dollars (CAD). No long-term commitment on monthly plans. Cancel any time; your plan runs to the end of the period you have paid for.
Trial
- 3 PR reviews per developer, one-time
- Card required to start, never charged
- 30-day bug genealogy history
- Risk Heat Map (read-only)
Developer
Save 20% billed annually ($8/seat/mo).
- 1 person: the subscriber
- 150 PR reviews / month (daily and monthly limits apply)
- Full bug genealogy history
- Recurrence Firewall — 5 rules
Team
Save 20% billed annually ($20/seat/mo).
- Everything in Developer
- Everyone on your team, billed per seat, minimum 2 seats
- 100 PR reviews / seat / month (at least 300; daily and monthly limits apply)
- Unlimited recurrence rules
- Priority support
Enterprise
Self-hosted, SSO/SAML/SCIM, BYOK, audit logs, SLA, custom DPA — subject to contractual negotiation.
- Everything in Team
- PR review allowance agreed with you
- Dedicated support
Production Lock (Feature 6b) is live at no extra charge on Team and Enterprise, supporting Sentry and Rollbar today. It isn't available on Trial or Developer. Its regression-test runs don't count toward your PR review limit, but they pause once your plan's monthly reviews are used up. See Features for how it works and current limitations.
bugweg is not currently offered to customers located in Quebec. See our Terms of Service.
What each plan covers
Every plan is priced per seat. A seat is one GitHub account (a person, or on Team a bot account such as dependabot[bot]) that authors a pull request that bugweg reviews on your repositories in a calendar month (UTC). Here is exactly how many people each plan covers and what you are billed for.
| Plan | People covered | Seats you pay for | PR reviews (allowance) | Daily review limit | Monthly review limit | Price |
|---|---|---|---|---|---|---|
| Trial | Anyone on your connected repositories | None (card verified, never charged during the trial) | 3 per developer, one time (see the free trial) | None (the trial reviews are the limit) | None (the trial reviews are the limit) | $0 |
| Developer | 1 person: the subscriber. To subscribe to Developer, an organization admin connects their GitHub account to their bugweg login, and the seat goes to that GitHub account. An organization admin can later move the seat to themselves on the billing page (bugweg emails the organization's admins when that happens). If the seat is ever unset, for example after a change from the Team plan to the Developer plan, the first person on your team whose pull request bugweg reviews each month holds it until an admin takes it. Pull requests from anyone else on your team are not reviewed: bugweg marks the pull request's check as skipped and, when the pull request is opened, comments saying why. Outside contributors to public repositories are reviewed (see below); pull requests from GitHub bot accounts are not reviewed on Developer. | Always 1 | 150 per month | 30 reviews a day (UTC) | 225 reviews a month (UTC) | $10/mo, or $8/mo billed annually ($96/yr) |
| Team | Every person on your team (and every bot account) who authors a reviewed pull request, with no upper limit | At least 2. Each renewal is billed for the higher of this month's and last month's number of seats, so the amount goes up or down with your team. | 100 per seat per month, at least 300 | 15 per seat a day, at least 40 | 150 per seat a month, at least 450 | $25 per seat/mo, or $20 per seat/mo billed annually ($240 per seat/yr) |
| Enterprise | Agreed with you | Agreed with you | Agreed with you | Agreed with you | Agreed with you | Custom |
Who counts as a seat
- The author of each pull request bugweg reviews, counted once per calendar month however many pull requests they open. Pushing to someone else's pull request does not make you a seat; the pull request's author is counted.
- Outside contributors to public repositories are not counted. Their pull requests are reviewed and use reviews from your allowance, but they are not seats and they never take the Developer seat. Outside contributor means GitHub does not list them as an owner, member or collaborator of the repository. On private repositories everyone who authors a reviewed pull request counts.
- GitHub bot accounts count as seats on Team (for example dependabot[bot] or renovate[bot]), one seat each, on public and private repositories (a bot is never treated as an outside contributor; if one you did not add or install was counted, we refund that seat on request within 30 days of the renewal). A bot can never hold the Developer seat. Machine users that are ordinary GitHub accounts are counted.
- On Team, if your monthly review allowance is used up or a daily or monthly review limit is reached, the pull requests that are skipped do not add seats.
How reviews are counted: allowance and daily/monthly review limits
- On Developer and Team, a pull request uses at most one review per day (UTC) from your allowance. The first review of a pull request on a day counts; further pushes to it that day are reviewed without using another, up to 10 reviews of one pull request a day (UTC).
- Why the monthly review limit (225 on Developer) is above the allowance (150). Repeat reviews of a pull request on the same day use none of your allowance, but they do count toward the daily and monthly review limits (the review ceilings in the Terms). The limits are there so repeat reviews cannot run without bound; the allowance is what you pay for. Every review that starts counts toward the limits, even if it then fails or does not complete.
- Worked example (Developer). You open a pull request and push to it 4 more times the same day. bugweg runs 5 reviews: 1 uses your allowance (149 of 150 left this month) and all 5 count toward the limits (25 of 30 left today, 220 of 225 left this month). A second pull request opened that day uses another review from the allowance and counts once more toward each limit.
- The limits. Daily, per UTC day: 30 on Developer; on Team 15 per seat, at least 40. Monthly, per UTC calendar month: one and a half times the monthly allowance, 225 on Developer; on Team 150 per seat, at least 450. Seats are counted as for the allowance. The limits are those of the plan you are on when a review starts, and reviews already counted that day or month still count after a change of plan.
- When a limit is reached, further reviews do not run and use none of your allowance: the check is marked "Review skipped" with the reason (and, for the monthly limit, a comment when the pull request is opened). A refused review is not run again on its own: after 00:00 UTC for the daily limit, or from the 1st of the next calendar month (UTC) for the monthly one, the next push to a pull request, or a newly opened one, is reviewed. The free trial and prices are not affected.
- The Behavioral Contract Validator, Dependency Blast Radius and Test Coverage Gap Localizer checks run on Team and Enterprise (and during the trial), not on Developer.
How Team is billed
- At checkout you pay for at least 2 seats. We update the seat count on your subscription once a day; a change is charged from your next renewal, never in the middle of a billing period.
- Example: 3 people in September and 5 in October, all counted by our daily update before your renewal. Your renewal on November 1 is billed for 5 seats: 5 × $25 = $125 a month, plus applicable taxes. A person first counted after the last daily update before a renewal is billed from the following renewal. On the annual plan, the seat count at renewal is billed for the whole year.
- The billing page in your dashboard shows this month's seats and the seat count on your subscription for the next renewal, which we update once a day (around 03:00 UTC).
The full rules are in section 4 of the Terms of Service.
Choosing a plan
Start with the trial if…
you want to see bugweg's review quality and genealogy matching on your own codebase before paying anything. The trial gives each developer 3 real PR reviews, one time, for up to as many developers as your bugweg team has members — verify a card to start (a $0 authorization, never charged during the trial), no monthly reset. Once you've used them, upgrade to keep getting reviews.
Move to Developer if…
you've used your trial reviews and want ongoing coverage, or you want more than 5 active recurrence rules. Full genealogy history (not just 30 days) also means bugweg's pattern-matching gets meaningfully more accurate over time — more history to match against.
Move to Team if…
more than one developer opens pull requests (Developer covers one), you're approaching the 150/month Developer allowance (Team allows 100 reviews per seat, at least 300), or you want unlimited recurrence rules across multiple repos rather than the 5-rule cap.
How does per-seat pricing work?
A seat is a GitHub account that authors a pull request bugweg reviews on your repositories in a calendar month (UTC). On Team this includes GitHub bot accounts such as dependabot[bot]. People who are outside contributors to public repositories are never counted; bot accounts are counted on public repositories too. Developer covers one person: the subscriber. Team is billed per seat, with a minimum of 2: each renewal is charged for the higher of this month's and last month's number of seats. See what each plan covers.
Is my source code stored?
Raw diffs and full file contents are never persisted — confirmed directly in the pipeline code, not just claimed. What is stored is the LLM's written description of each flagged issue (which can quote a short line of code, since it's free text an LLM wrote) and an embedding used for genealogy matching. Full detail on Security.
What counts as a PR review?
Each new pull request, and each push to one, triggers a review. On Developer and Team, a pull request uses at most one review a day (UTC) from your monthly allowance: the first review of a pull request on a day counts, and further pushes to it that day are reviewed without using another. On Developer and Team, every review that starts, repeat reviews of a pull request included, also counts toward your team's daily and monthly review limits (the review ceilings), even if it then fails or does not complete: on Developer 30 a day and 225 a month; on Team 15 per seat a day (at least 40) and 150 per seat a month (at least 450). Days and months are UTC calendar days and months. A pull request is reviewed at most 10 times a day. A review refused by a limit is not run and uses none of your allowance, and it is not run again on its own: after 00:00 UTC, or from the 1st of the next month for the monthly limit, the next push to a pull request, or a newly opened one, is reviewed. On the trial, every review counts, including the review of each new push, against the pull request author's one-time 3 trial reviews, which never reset on their own.
Why does the trial need a card?
The trial is counted per card and per developer: each verified card gives 3 reviews to each developer (the GitHub account that authored the pull request), for up to as many developers as there are members of your bugweg team. Pull requests from outside contributors share one further set of 3. Each bot account gets its own 3 instead, for up to 3 bot accounts per card; further bots share the outside contributors' 3. GitHub accounts are free to make, cards aren't: the card, and the limit of as many developers as your team has members, limit how far one person can restart the trial with new GitHub accounts, and the Terms forbid it. We verify the card with a $0 authorization and never charge it during the trial.
What happens after the trial reviews are used?
bugweg stops reviewing that developer's pull requests under the trial and comments on the pull request to let you know. The GitHub App install stays active — reviews resume immediately once you start a paid plan, no reinstall needed.
How does annual billing work?
Annual billing saves 20% versus monthly, charged as one upfront payment per seat per year — $96/seat/yr on Developer, $240/seat/yr on Team. Your price and usage limits (the monthly review allowance and the review ceilings) stay the same for the 12-month term, and we tell you about a higher price or lower limits at least 30 full days, and not more than 60 days, before they apply to your subscription. A renewal is charged at the price per seat, and has the limits, in effect on the renewal date, after that notice; if you do nothing, it renews automatically, and if you cancel before the renewal date, you are not charged the new price. An annual subscription (Developer or Team) is a 12-month commitment from your checkout date, or from the date you switch from monthly billing: if you cancel, it ends at the end of that term (Terms, section 4).
Is there a free trial for paid plans?
The free trial is 3 PR reviews for each developer, one time, for up to as many developers as there are members of your bugweg team, before any paid plan. Verify a card to start (a $0 authorization, never charged during the trial); once the trial reviews are used, subscribe to Developer or Team to keep getting reviews.
What happens if I cancel?
Your plan stays active until the end of the period you've paid for (month or year), then reverts to the trial tier. If your trial reviews are already used, PR reviews pause until you resubscribe — existing analysis history, genealogy data, and recurrence rules are kept, not deleted. An organization admin can delete your data at any time on the Data & privacy page of the dashboard.