LinearB Pricing and Credits

LinearB's pricing model is designed with your flexibility in mind. It's a hybrid system that empowers you to manage your costs effectively. There are two components to our pricing system:
  • A fixed seat price is based on the number of contributors in your organization that are tracked and measured by LinearB.
  • Usage-based credits are consumed when LinearB automates a PR for any member of your organization.
One PR consumes 100 credits, regardless of the number or type of tasks — like an AI-based code review or policy-based routing — that LinearB runs. It also doesn’t matter if a contributor or a bot created the PR — any PR automated by LinearB consumes 100 credits.

How contributors and bundled credits work

A contributor is a team member for whom LinearB measures and calculates engineering metrics, using features such as DORA, Developer Satisfaction Surveys, Project Tracking, or Resource Allocation. You only pay for contributors that are being measured; you can add unlimited users (e.g., not on a team, no metrics) at no additional cost. Bots are not counted as contributors even if they generate PRs. The number of contributor seats determines the amount of bundled credits included in your plan.

The number of contributor seats determines the amount of bundled credits included in your plan

Plan
Price per Contributor
Bundled Credits per Contributor
Essentials
$19/month
1,000 credits/month
Enterprise
$59/month
1,500 credits/month
Your credit allocation is a shared pool for the entire organization, so managing credits at the contributor level is not required. If you want to add users who are not contributors, they can consume credits from your shared pool. Credits reset on the first of each month. If usage exceeds the bundled allocation, you can add credits at any time by purchasing credit packs, which are added to your monthly allocation.

What happens if you exceed your credit limits?

Our overage policy is designed to be flexible and fair so you can predictably manage your costs during your initial ramp and easily navigate any changes that occur in the future. Here’s how we do that: 1. You get a buffer period
  • You can exceed your monthly credit allocation in any two months per contract year at no charge.
  • These months don’t need to be consecutive.
2. We cap overages to protect you
  • To prevent accidental runaway use, we cap the free overage at 120% of your credit allocation to prevent accidental runaway use or abuse.
  • The 120% cap is removed during the first two months of your deployment to allow time for right-sizing.
  • If you reach the cap, automations pause until the next monthly reset or until you purchase additional credits.
3. You can purchase additional credits at any time
  • Credits are sold in packs of 5,000 & 10,000 (e.g., 50 or 100 additional PRs).
  • Additional credits are recurring monthly credits. Once purchased, they are added to your account through the end of your contracted period.
  • Volume discounts are available for large deployments.

What if I need additional credits?

The product's usage dashboard shows your credit balance and current consumption. You will also receive usage notifications and alerts if you are approaching credit limits. If you need additional credits, simply click the button on your billing dashboard to contact a LinearB representative. Credit packs are priced as follows, with volume discounts available for large deployments.

Credit packs are priced as follows, with volume discounts available for large deployments

Pack Size (credits)
Monthly Price
Cost per Credit
5,000
$67.50
$0.0135
10,000
$125.00
$0.0125
Contracts and billing are offered on an annual basis only. Your contract will be adjusted when additional credit packs are purchased. Extra credits will be applied for the duration of your contracted period.

How to estimate your credit usage

For example, assume a developer team of 50 contributors looking to purchase our Essentials plan. The monthly bundled credit allocation works out to:
  • 50 contributors x 1,000 credits/contributor = 50,000 credits/month
  • 50,000 credits support 500 automated PR/month or 10 PR/contributor/month
Next, estimate your monthly PR volume based on the number of commits. Include PRs generated by both developers and bots. When you initially setup LinearB for your free trial we backfill the previous 90 days of data so you can make an accurate assessment. Once you have the total PR volume, estimate the percentage of PRs that LinearB will automate. This number can vary significantly between companies, but a good rule of thumb is to start with 50% and adjust up or down depending on your goals.

Scenario A

Total PR/month
700
% Automated
50%
Automated PR/mo.
350
Estimated Credits Required
35,000

Scenario B

Total PR/month
1,000
% Automated
60%
Automated PR/mo.
600
Estimated Credits Required
60,000
Finally, compare the estimated credits required to bundled credits. In Scenario A, you would expect no additional credits to be needed in the short term. In Scenario B, you should purchase 10,000 additional credits and evaluate usage to see if more are required. In all cases, teams should validate these assumptions based on actual usage during the free trial period and/or the first two months of production, i.e., the buffer period. This is enough time to determine steady-state usage and growth so that you can plan and budget accordingly.

Still have questions?

Please contact us if you need help estimating your usage or have other questions.