Bitbucket Pricing & Licensing

View the Bitbucket pricing page to learn what’s included in each plan.

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.

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.

If you’re on a monthly plan, you will continue to get billed for extra usage at the end of each billing period.

If you’re on an annual plan, extra usage charges will apply starting Dec 3, 2026. You can configure your billing frequency within Atlassian Administration.

Yes! To learn more, visit the below application link relevant to you:

• Social Impact License Request
• Academic License Request

• Classroom Licenses

A user is anyone with a Bitbucket account. Once you give a user access to a private repository they count as a user for your billing plan.

A workspace is how you organize different streams of work in an account. Anything you create in Bitbucket Cloud (repositories, branches, etc) will live under a workspace. All users start with one workspace and one workspace ID, and you can create additional workspaces as needed, and invite other users into them. For more information, please see our Workspace documentation.

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.

We have two tiers for self-hosted runners.
Standard runners are free to register and use up to a max of 100 runners.

Premium runners are priced at $15 per concurrent build slot used.

To manage your budget, you can set the maximum number of concurrent build slots for your workspace.
You are only billed for the maximum number of concurrent slots you actually use. For example, if you set a max of 20 but only use a max of 15 concurrent slots in the month, you get billed for 15. 

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. 

Like all other Atlassian meters, Bitbucket usage allowances will be pooled at the organization level for both annual and monthly customers. This means your included monthly allowances (build minutes, Git LFS storage, Packages storage and Packages network) are shared across all workspaces within your Atlassian organization, not siloed per workspace.

What you should know:

• Organization-level pooling gives you flexibility. If a workspace uses fewer build minutes in a given month, that capacity is available to other workspaces in your organization without the need to manually reallocate.
• Usage transparency. The Platform usage dashboard in Atlassian Administration shows total organization-level usage and allows you to drill into workspace-level breakdowns, so you can see which teams or projects are driving usage.

Why organization-level pooling?
Many organizations have multiple workspaces for different teams or projects. Organization-level pooling prevents situations where one workspace hits its limit while another has unused capacity, reducing waste and avoiding unnecessary extra usage charges.

Bitbucket usage is measured across four meters: Pipelines Build Minutes, Git Large File Storage (LFS), Packages Storage, and Packages Network.

If you’re on a Bitbucket monthly plan, you are paying for these meters already. If you are on an annual plan, these meters will apply starting Dec 3, 2026.

How usage is measured across these meters:

Bitbucket Packages is a built-in artifact registry that lets your team publish, version, and consume Docker images and language packages (npm, Maven, PyPI, and NuGet), all within Bitbucket. With source code, CI/CD, and artifact storage in one platform, your developers reduce context switching, and can manage the entire delivery pipeline from a single place.

If you’re on an annual plan, Packages will be enabled on Dec 3, 2026.

If you’re on a monthly plan, you should see Packages in your left navigation menu under each repository.

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.

To prevent your existing pipelines from breaking, extra usage 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 extra usage or have reached an extra usage cap that you set for your organization, your pipelines will stop running until your usage resets the following month. All other 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 do not 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 do not 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 extra usage enabled. If uninterrupted CI/CD is critical, keep extra usage billing turned on.
• Monitor threshold notifications. Admins will start receiving alerts when usage reaches 80% and 100% of the usage limits, giving teams time to optimize workflows or plan ahead to purchase additional capacity.
• Manage usage. Audit your pipelines to find optimization opportunities, for example, skip builds on non-critical branches, cache dependencies, and leverage Bitbucket Packages to cut redundant download time.

Starting December 3rd, you can purchase prepaid annual usage packs to lock in a lower rate. Contact your sales team for details

• Annual usage packs let you purchase additional capacity beyond your included allowance and are used to top up your monthly allowances. Allowances do not roll over to the next month.
• Committed packs (coming soon) are a prepaid balance your organization can draw from at any time during the 12-month commitment period. This acts like a gift card - the balance depletes as you use it. They are valid for 12 months and do not roll over to the following year.

We recommend buying the pack that meets your current usage levels. 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 going beyond your monthly allowance or 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 you need.

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 across each meter, pooled at the organization level.