Skip to main content

Viewing Credits Consumption

Track your organization’s credit usage in real time. See how many credits and seats are assigned, monitor current and past consumption, and download detailed reports.

Steven Silverstone
Updated by Steven Silverstone

The Credits Consumption panel helps you understand how your organization is using LinearB credits. It shows how many credits are available, how many have been used, and when your credits will renew.

This article also explains what consumes credits and what happens if your organization exceeds its allocation.

Accessing the Consumption Screen

  1. In LinearB, click Settings in the left-side menu.
  2. Open the Consumption tab.
  3. The Credits Consumption panel displays your organization’s usage.

What Consumes Credits

Credits are consumed when gitStream analyzes a pull request.

Each pull request is charged once per month. If the same pull request is analyzed multiple times during the same month, it does not consume additional credits during that month. If the same pull request is analyzed again in a new month, it consumes credits again for that new month.

Example

  • A pull request is analyzed in February → credits are consumed.
  • The same pull request is analyzed again later in February → no additional credits are consumed.
  • The same pull request is analyzed again in March → credits are consumed again.
Credits are tied to pull request analysis, not to the number of times a pull request is viewed or re-opened within the same month.

Understanding the Credits Dashboard

The dashboard includes the following information:

  • Days remaining to credits renewal: Shows how many days remain before your credit balance resets.
  • Credits used / total available: Shows how many credits are included in your plan and how many have already been consumed.
  • Seats assigned: Shows how many seats are currently assigned out of the total available.
  • Current month usage: A bar chart shows how many credits have been consumed during the current billing month.
  • Previous months: Historical usage is shown for past months, including a Full report option to download a detailed breakdown.

Credit Over-Usage Behavior

If your organization exceeds its allocated credits, LinearB allows limited temporary over-usage before restrictions are applied.

Over-usage thresholds

Up to 140% of allocated credits

Your organization may exceed its credit allocation up to 140% twice, whether those months are consecutive or non-consecutive.

After the second occurrence, gitStream automation is disabled for the remainder of that month. Starting with future months, usage is limited to 100% of the allocated credits.

180% of allocated credits

If usage reaches 180% of the allocated credits, gitStream automation is automatically disabled immediately until the next credit cycle begins or additional credits are added.

What happens when credit limits are reached

  • gitStream will not run on new pull requests.
  • Existing pull requests are not reprocessed.
  • Automation rules will not trigger until credits reset or additional credits are added.
Credits reset according to your organization’s billing cycle. If you expect to exceed your allocation, contact LinearB Support to purchase additional credits.

Managing Seats

Click Manage Seats to assign or unassign seats. Adjusting seat allocation helps you control which users have access to LinearB features.

Buying More Credits

If you are approaching your credit limit, click Buy More Credits to contact LinearB Support and purchase additional credits.

How did we do?

Contact