Atlassian Announces Tiered Pricing and New Operating Model for Bitbucket Self-Hosted Runners to Balance Scalability and Accessibility

In a significant update to its DevOps ecosystem, Atlassian has unveiled a revised operating model and pricing structure for Bitbucket self-hosted runners, a move designed to reconcile the company’s need for continued infrastructure investment with the community’s demand for accessible entry-level tools. This announcement follows an initial declaration made in December 2025, where Atlassian first signaled its intention to introduce a paid model for self-hosted runners. The primary objective behind the shift is to generate the necessary resources to provide enhanced technical support, maintain a rigorous schedule of security updates, and accelerate the development of advanced features for Bitbucket Cloud users who manage their own CI/CD (Continuous Integration and Continuous Delivery) infrastructure.

The decision to introduce a dual-tier system—comprising a robust Free tier and a feature-rich Premium tier—comes as a direct response to feedback from the Bitbucket user base. Following the December 2025 announcement, many customers expressed that maintaining a free option was critical for smaller development teams and open-source projects. By pivoting to this new model, Atlassian aims to support the diverse needs of its global clientele, ranging from independent developers to multinational corporations with complex compliance and scaling requirements.

The New Tiered Structure: Free vs. Premium

The cornerstone of this update is the introduction of the Free tier, which is specifically engineered to serve the needs of small to medium-sized development teams. Under this tier, workspaces can utilize up to 100 basic runners. This ensures that teams with moderate automation needs can continue to run their pipelines on their own infrastructure without incurring additional costs, provided they stay within the 100-runner limit. These runners allow for the execution of Bitbucket Pipelines on the user’s local hardware or private cloud, offering privacy and control over the build environment.

For organizations with more demanding requirements, Atlassian is launching the Premium runners tier. This offering is tailored for enterprise-scale operations that manage complex workloads, require high-level scalability, or must adhere to strict regulatory compliance standards. The Premium tier is designed to unlock advanced orchestration capabilities, which allow for more sophisticated management of build tasks across a large fleet of runners. Additionally, Premium subscribers will benefit from higher operational limits and access to Atlassian’s premium support services, ensuring that critical CI/CD bottlenecks can be addressed with urgency.

Shift in Billing Methodology

Parallel to the introduction of the Premium tier is a fundamental change in how Atlassian calculates billing for runner usage. Previously, the pricing model was anchored to a flat rate of $15 per concurrent build per month. This was calculated based on the maximum concurrency limit set at the workspace level, regardless of whether that capacity was fully utilized throughout the billing cycle.

The new billing model introduces a more flexible, usage-based approach. Under the revised system, charges will be determined by the maximum number of concurrent build slots actually utilized by runners during a given month. In this configuration, the workspace concurrency limit no longer acts as the sole driver of the bill; instead, it serves as a management tool and a financial cap. This allows administrators to set a ceiling to prevent unexpected costs while ensuring they only pay for the peak capacity they actually required during that period. This shift is intended to provide a more equitable reflection of real-world usage patterns, particularly for teams with fluctuating development cycles. All changes to billing will be processed on a monthly cycle and reflected in the customer’s standard monthly statement.

The June 2026 Milestone and Technical Updates

A critical date for all Bitbucket Cloud administrators is June 3, 2026. On this day, Atlassian will release a new version of the runner software. This update is mandatory for both Free and Premium users, as it contains essential system updates, stability patches, and critical security fixes. This release serves as the official technical transition point for the new tiered model. Administrators will need to ensure their self-hosted environments are prepared to adopt this new version to maintain service continuity and ensure their infrastructure remains protected against emerging vulnerabilities.

Detailed Migration Scenarios and Action Required

To facilitate a smooth transition, Atlassian has outlined three distinct migration scenarios based on the current configuration of a user’s workspace. These scenarios determine whether the Premium features will be enabled by default following the June 2026 update.

In the first scenario, workspaces currently utilizing only v5 runners will be migrated with Premium runner functionality enabled by default. The "max concurrent builds" setting for these workspaces will remain unchanged, ensuring that existing build workflows are not interrupted. Following the migration, all v5 runners in these environments will be classified as Premium runners.

The second scenario applies to workspaces using only v3 runners. These workspaces will be migrated with Premium runner functionality disabled. All v3 runners will continue to operate under the Free tier. These users can continue to utilize up to 100 free runners. If a workspace in this category eventually requires the advanced features of the Premium tier, the administrator can manually upgrade at any time.

The third scenario involves workspaces that currently employ a combination of v3 and v5 runners. These workspaces will be migrated with Premium runner functionality enabled. Consequently, all runners—regardless of whether they were originally v3 or v5—will operate as Premium runners post-migration. Atlassian has clarified that there will be no immediate increase in the workspace’s bill during this migration, provided the "max concurrent builds" setting is not increased beyond the amount set at the time of the transition.

Impact on Throughput and the Path to the Free Tier

Atlassian has issued a specific technical note for customers in the "mixed version" category (using both v3 and v5). In some instances, customers may have significantly more v3 runners than v5 runners. Because the "max concurrent builds" setting will apply globally to all runners post-migration, these teams might experience a decrease in total build throughput if their previous v3 usage was not strictly capped by the concurrency setting.

For organizations that prefer to remain strictly on the Free tier and avoid the Premium classification, proactive steps are required. To ensure a workspace is migrated with Premium runners disabled, administrators must deprovision all v5 runners prior to the migration deadline. This action will place the workspace into the second migration scenario, preserving the Free tier status.

Premium Features and Future Enterprise Investments

The Premium runner offering is not merely a pricing change but a platform for new functionality. The initial rollout of Premium runners will include advanced orchestration tools designed to optimize how jobs are distributed across infrastructure. Looking ahead, Atlassian has committed to further investments in Enterprise-grade features. These include enhanced compliance tools to help organizations meet auditing requirements and sophisticated administrative controls to manage large-scale runner deployments more efficiently.

By separating the runner offerings into two tiers, Atlassian aims to provide a scalable path for growth. Small teams can start with the Free tier to establish their CI/CD pipelines, while growing enterprises can opt into the Premium tier as their workloads become more complex and their need for high-availability support increases.

Support and Community Engagement

Recognizing that changes to pricing and infrastructure models can be complex, Atlassian is encouraging users to utilize available resources for guidance. Detailed technical documentation is available through the Bitbucket Cloud support pages, covering the specifics of runner installation, version management, and billing configurations. Furthermore, the Atlassian Community platform has been designated as a central hub for discussion, where users can ask questions, share feedback, and interact with Atlassian product teams regarding these changes.

As the June 2026 deadline approaches, Atlassian advises all Bitbucket Cloud administrators to review their current runner versions and workspace settings to determine which migration path they will follow. By providing a clear roadmap and a variety of options, Atlassian seeks to ensure that self-hosted runners remain a sustainable and powerful component of the Bitbucket ecosystem for years to come.