Usage-based billing starts December 3, 2026. To prepare, review your included allowance, current usage, and forecast in Atlassian Administration.View your usage
Bitbucket Pricing & Licensing
Bitbucket Billing Engine
What is changing for me as an annual Bitbucket customer on Dec 3, 2026
Starting Dec 3, 2026, annual plans work the same way as monthly plans: usage beyond your included allowances is billed at published rates, and all plan features, including Packages, will be available on your plan.
Organization-level allowance tracking: Your meter allowances are tracked at the organization-level, covering all workspaces linked to your Atlassian organization. For example, if one workspace uses fewer build minutes, that unused capacity is automatically available to other workspaces in your organization.
Usage controls: Organization and billing admins can set pay-as-you-go limits to cap spending and keep within budget.
Usage notifications: As teams approach usage limits, organization and billing admins receive alerts so teams have time to optimize workflows or can plan to budget for additional capacity.
Centralized billing access: Billing is now managed at the organization level for unified oversight. To manage usage and set limits, ask your Organization Admin to grant you the Billing admin role in Atlassian Administration.
To monitor usage at the organization level, go to Atlassian Administration. select your organization, navigate to Usage > Meters, and select the Bitbucket meter you'd like to review.
To monitor usage at the workspace or repo level, in Bitbucket, go to your Workspace settings > Plans and billing, and select the meter you'd like to review.
Note: At this time, premium runners usage will be visible in the Atlassian Administration but max concurrency settings will continue to be managed within the Bitbucket UI at the workspace level.
Questions? If you have questions or concerns about how this change impacts your usage or costs, contact our support team or reach out to your account executive — we're happy to help you review your usage, model scenarios, and find the most cost-effective path forward.
What is changing for me as a monthly Bitbucket customer after usage based billing migrates to Atlassian Administration?
We are in the process of migrating pay-as-you-go billing for monthly plans from Bitbucket billing pages to Atlassian Administration. Migration rollout cohorts started Oct 26, 2026 and will complete in the coming months.
This migration is designed to give you more flexibility in using your allowances and centralizes billing controls.
As part of this migration:
Organization-level allowance tracking: Your meter allowances are tracked at the organization-level, covering all workspaces linked to your Atlassian organization. For example, if one workspace uses fewer build minutes, that unused capacity is automatically available to other workspaces in your organization.
Spend controls: Organization and billing admins can set pay-as-you-go limits to cap spending and keep within budget.
Usage notifications: As teams approach usage limits, organization and billing admins receive alerts so teams have time to optimize workflows or can plan to budget for additional capacity.
Centralized billing access: Billing is now managed at the organization level for unified oversight. To manage usage and set limits, ask your Organization Admin to grant you the Billing admin role in Atlassian Administration.
To monitor usage at the organization level, go to Atlassian Administration. select your organization, navigate to Usage > Meters, and select the Bitbucket meter you'd like to review.
To monitor usage at the workspace or repo level, in Bitbucket, go to your Workspace settings > Plans and billing, and select the meter you'd like to review.
Note: At this time, premium runners usage will be visible in the Atlassian Administration but max concurrency settings will continue to be managed within the Bitbucket UI at the workspace level.
What Bitbucket actions count towards usage based pricing and how does pricing work?
Bitbucket usage is measured across four meters: Pipelines Build Minutes, Git Large File Storage (LFS), Packages Storage, and Packages Network.
How usage is measured across these meters:
Meter | Unit | How it's measured |
|---|---|---|
Bitbucket Pipelines | Build minutes | Build minutes measures CI/CD pipeline execution time that your organization consumes each month. Total build minutes is calculated based on runner size used, for example, a 5-minute step on a 2× runner would count as 10 build minutes. |
Git LFS Storage | GB stored | Git LFS is the total size of all binary assets (videos, datasets, design files) stored in Git LFS. For example, if your team stores 5 GB of design mockups, you consume 5 GB of storage. |
Packages Storage | GB stored | Packages Storage is the disk space used by container images and language packages (npm, Maven, PyPI, NuGet) that you publish and host in Bitbucket’s built-in package registry. For example, if your engineering team has 3 container images that are 500 MB each, with 10 stored versions, the total storage is 15 GB (3 * 500* 10). |
Packages Network | GB transferred | Packages Network is the monthly total volume of data transfer (egress) from Bitbucket Packages (npm, Maven, PyPI, NuGet registries). For example, if a 1 GB package is downloaded 10 times either by a user or via a CI/CD pipeline, that's 10 GB transferred. |
What does NOT count as usage:
Hosting repositories, including code, branches, and pull requests.
Pull request reviews, comments, and approvals.
Browsing code, viewing diffs, or using the Bitbucket UI.
Standard Git push and pull operations.
Merge checks, deployment permissions, and access controls.
Builds that run on self-hosted runners do not count towards build minutes.
How pricing works:
Each meter includes a monthly allowance as part of your plan. When you exceed these monthly allowances, we bill you based on the resources you use. Unused allowances don't roll over month to month.
Each of these meters is tracked at the organization level i.e., all workspaces under your Atlassian organization share these resources.
Here are the monthly allowances per workspace that are included in your plan.
Meter | Standard | Premium |
|---|---|---|
Build minutes | 2,500 min/mo | 3,500 min/mo |
Git LFS storage | 5 GB | 10 GB |
Packages storage | 1 GB | 2 GB |
Packages network | 5 GB | 7 GB |
Pay-as-you-go billing:
If you’re on a monthly plan, pay-as-you-go usage is billed at the rates below on your next monthly invoice,
If you’re on an annual plan, you are billed based on the billing frequency you select in your account. For annual customers, these rates apply starting Dec 3, 2026.
Meter | Pricing |
|---|---|
Build minutes | $10 per 1,000 additional minutes |
Git LFS storage | $10 per 100 GB additional storage |
Packages storage | $0.35 per additional GB/month |
Packages network | $0.70 per additional GB/month |
Annual usage packs (prepaid):
If you’re on an annual plan, you can purchase prepaid usage packs to lock in a lower rate. These are available via your Atlassian account executive or customer success manager. There are two types of prepaid packs.
Annual usage packs: Pre-purchase a fixed monthly pack on an annual contract. Best for consistent, predictable month-over-month usage above your included allowance. Unused capacity in a month does not roll over to the next month.
Committed packs: Pre-purchase a fixed amount of usage that you can use over 12 months. Best for variable, seasonal, or growing usage where you want a flexible annual pool without monthly use-it-or-lose-it resets.
If you require a usage pack only for a specific month, you can also purchase a monthly usage pack.
Example:
If you’re on a Premium plan with an allowance of 3,500 build minutes per month:
If you buy an annual usage pack of 100,000 build minutes, it’s prorated to 100,000 / 12 = 8334 minutes and increases your monthly allowance to 3,500 + 8,334 = 11,834 min/mo.
If you use 12,834 minutes in a month, you’ll be billed $10 for the extra 1,000 minutes per our standard postpaid pricing. Or if you have purchased a discounted committed pack, the extra minutes will be deducted from that balance.
If you foresee usage consistently exceeding your monthly allowance each month, we recommend contacting us to purchase an annual usage pack. If your usage varies significantly from month to month due to your operational needs, we recommend buying a committed pack so you can draw from it as needed.
Note: At this time, premium runners usage will be visible in the Atlassian Administration but max concurrency settings will continue to be managed within the Bitbucket UI at the workspace level.
Where will I access my bill for Bitbucket Cloud following the billing platform migration?
You’ll find all your Bitbucket Cloud billing information in Atlassian Administration after the migration. This centralizes your billing activities across seats and usage in one place for easier access and management.
What new payment methods will be available for Bitbucket on Atlassian Administration?
You’ll now be able to pay using PayPal, ACH debit, and credit card, in addition to all the payment methods you used before.
How will usage-based pricing affect multi-year subscriptions?
For annual and multi-year subscriptions, starting Dec 3, 2026, usage beyond your included allowances is billed at published rates.
Do I need to enable pay-as-you-go on these features?
To prevent your workflows from breaking, pay-as-you-go on these meters is automatically enabled on your account.
To manage your budget, organization admins and billing admins can track usage within Atlassian Administration. You can set and adjust pay-as-you-go limits, get alerts when you approach your usage limits, or you can choose to disable pay-as-you-go usage.
If you are on a monthly plan, your credit card on file will be billed at the end of each monthly billing cycle.
If you’re on an annual plan, you will be billed based on the frequency you choose within your account.
Bitbucket Cloud
What does Bitbucket Cloud cost?
View the Bitbucket pricing page to estimate your costs by number of users.
What is the difference between Bitbucket Standard and Bitbucket Premium?
The Standard plan gives growing teams everything they need to collaborate on code and build CI/CD pipelines.
The Premium plan gives you larger monthly allowances of build minutes, LFS storage and other meters. You also get additional admin and security controls like enforced merge checks, deployment permissions, IP allowlisting, and more.
View the Bitbucket pricing page to learn what's included in each plan.
What are build minutes?
Build minutes measure CI/CD pipeline execution time on Atlassian cloud runners. Total build minutes is calculated based on runner size used, for example, a 5-minute step on a 2× runner would count as 10 build minutes.
As a Bitbucket Free user, how do I pay for extra build minutes or file storage?
On free plans, you cannot buy extra build minutes or LFS storage beyond your plan allowances. If you wish to purchase additional allowances please upgrade to a paid plan.
Does Bitbucket offer discounts to nonprofits, social enterprises, academic institutions, students and teachers?
Yes! To learn more, visit the below application link relevant to you:
What is a user? What is a workspace?
A user is anyone with a Bitbucket account who has access to a private repository on your workspace.
A workspace is how you organize different streams of work in Bitbucket. Anything you create in Bitbucket Cloud (repositories, branches, etc.) will live under a workspace. When you sign up for Bitbucket, you start with one workspace and one workspace ID. You can create additional workspaces as needed, and invite users into each workspace.
For more information, please see our workspace documentation.
How are Bitbucket Packages priced?
Packages pricing is based on package storage and package network usage. For example:
If you have two containers saved – one is 1 GB, and the other is 2 GB → Total = 3 GB package storage
If 100 devs download the 1 GB package, and 20 download the 2 GB package. Your total network usage is 140GB
For rates, please view our pricing page.
How are self-hosted runners priced?
We have two tiers for self-hosted runners. Standard runners are free and you can register up to 100 runners.
Premium runners allow you to register up to 1,000 runners per workspace with priority build queueing, dedicated support, pluggable storage, runner groups, automatic updates, and other advanced capabilities.
They are priced at $15 per concurrent build slot used. A concurrent build slot is the number of builds you run simultaneously using self-hosted runners. You are only billed for the maximum number of concurrent slots you actually use in the given month. For example, if you set a limit of 20 concurrent runners but only use a maximum of 15 concurrent slots in the month, you get billed for 15.
To manage your budget, you can set the maximum number of concurrent build slots for your workspace in your Bitbucket workspace settings.
I have more questions!
Bitbucket Cloud Standard and Bitbucket Cloud Premium customers are welcome to contact our Bitbucket Support Team at any time for assistance.
Bitbucket Cloud Free subscribers are eligible for support through the Atlassian Community.
Usage-Based Pricing & Meters
Why is Bitbucket usage measured across separate meters rather than as a single bundled allowance?
Each Bitbucket meter (build minutes, LFS, package storage, and packages network) tracks a different type of resource and uses different units of measurement. Tracking them as separate meters means you only pay for the resources that you actually use.
With individual per-meter tracking, you can also track how your usage is trending for each resource and manage it accordingly. For example, if usage is trending up in build minutes, you can optimize CI/CD workflows to manage your budget, or, if you need additional capacity, you can purchase prepaid or committed usage packs specifically for build minutes.
Do failed builds still consume build minutes?
Yes, failed builds consume build minutes. Build minutes are measured based on the execution time of each pipeline step, regardless of whether the step (or overall pipeline) succeeds or fails. If a step runs for 3 minutes on a 2× runner before failing, that consumes 6 build minutes.
Why it works this way:
Compute resources (CPU, memory, network) are consumed the moment a step begins executing, whether the outcome is a pass or a fail. This is consistent with how all major CI/CD platforms measure usage.
What you should know:
A pipeline that fails on step 3 of 5 will only consume minutes for steps 1–3 (steps 4 and 5 never execute and are not charged).
Manually cancelled pipelines consume minutes up to the point of cancellation.
How to minimize wasted minutes from failures:
Use caching to speed up steps so failures are caught faster.
Place fast-failing checks (linting, static analysis) early in the pipeline so expensive steps don't run unnecessarily.
Use conditional steps or pipeline triggers to avoid running full builds on non-critical branches.
What happens when build minutes are exhausted?
Pay-as-you-go billing for build minutes is automatically enabled on your account. When build minutes allowances are exhausted, your usage will continue to be tracked, and you will be billed during your next billing cycle.
However, if you have disabled pay-as-you-go or reached the pay-as-you-go limit you set for your organization, your pipelines will stop running until your usage resets the following month. Non-metered Bitbucket features will continue to work normally.
What you should know:
Core functionality is not affected. Repositories, code hosting, pull requests, code review, branching, merging, deployment permissions, merge checks, access controls, and AI features all continue to function without interruption because these features don't consume build minutes.
Self-hosted runners are not affected. Pipelines configured to run on your own self-hosted runner infrastructure will continue to execute because they don't count towards build minutes.
Other meters are independent. Exhausting build minutes has no impact on Git LFS storage, Packages storage, or Packages network because each meter operates independently.
How to avoid disruption:
Keep pay-as-you-go enabled. If uninterrupted CI/CD is critical, keep pay-as-you-go billing turned on.
Monitor threshold notifications. If you’re an admin and see an alert that your team is approaching usage limits, plan to increase your limits based on your teams needs.
Optimize usage. Audit your pipelines to find optimization opportunities, for example, skip builds on non-critical branches, right-rize runner sizes, cache dependencies, and leverage Bitbucket Packages to cut redundant download time. View our optimization guide.
How can I track and forecast my usage and costs?
We provide several tools to help you understand your included allowances, monitor current usage, and forecast future costs, all accessible from Atlassian Administration.
1. Know your included allowances
Your plan includes monthly allowances per workspace across each meter, pooled at the organization level.
Meter | Standard | Premium |
|---|---|---|
Build minutes | 2,500 min/mo | 3,500 min/mo |
Git LFS storage | 5 GB | 10 GB |
Packages storage | 1 GB | 2 GB |
Packages network | 5 GB | 7 GB |
If your usage stays within these allowances, there are no pay-as-you-go charges.
2. Monitor current usage in real time
The Usage dashboard in Atlassian Administration shows:
Current usage across all meters in a single view.
Usage trend data to help understand patterns over time.
3. Forecast future costs
Use your historical usage levels to estimate future usage needs.
If you’re not currently using these meters or if historical trends are not representative of future needs, here are some examples of how you can estimate usage:
Build minutes: 4000 builds/mo × 30 minutes per build x 2x step size = 240,000 projected monthly build minutes.
Git LFS storage: 100 repositories × 20 GB/month = 2,000 GB projected Git LFS storage per month.
Packages storage: 30 package versions/month × 2 GB each = 720 GB projected package storage per month.
Packages network: 5,000 container or package downloads/month × 1 GB each = 50,000 GB network usage per month.
4. Calculate costs
Once you’ve estimated your usage, subtract the allowance that is part of your plan and calculate pricing for the remaining.