cloudparts

Bitbucket

Atlassian’s Git host, built to sit next to Jira: pull requests, code review and Bitbucket Pipelines CI, as the Bitbucket Cloud service or the self-managed Bitbucket Data Center.

What it is
Version control
Used for
CI/CD pipelines
Type
Commercial product
Made by
Atlassian
License
Proprietary
Facts checked
20 October 2026
Website

What it is

Bitbucket comes in two products. Bitbucket Cloud, at bitbucket.org, is the hosted service; Bitbucket Data Center is the version you run yourself, the successor of Stash and Bitbucket Server. Both host Git repositories (Mercurial was removed from Cloud in 2020) and review changes as pull requests. Data Center can keep repositories on Bitbucket Mesh, added in 8.0, which replicates each repository across several nodes instead of a shared NFS volume, so losing one node doesn’t make its repositories unavailable.

What sets it apart is Atlassian’s other products. Put a Jira work item key such as JRA-34 in a branch name, commit message or pull request title and the work item links to it; Smart Commits go further, so JRA-34 #time 2h #comment fixed #resolve in a commit message logs time, comments and moves the item through its workflow. Bitbucket Pipelines, its built-in CI, reads bitbucket-pipelines.yml from the root of the repository and runs each step in a Docker container in Atlassian’s cloud; a pull-requests pipeline first merges the destination branch into the source branch, so it tests the result of the merge. Since April 2026 Pipelines can also run AI agent steps through Atlassian’s Rovo Dev, in open beta.

Cloud is free for up to 5 users with 50 build minutes a month, then $3.65 per user a month for Standard and $8 for Premium, which adds enforced merge checks, IP allowlisting and deployment permissions. A Cloud repository should stay under 2 GB and stops accepting new commits at 4 GB. Atlassian ended support for its Server products on February 15, 2024, and in September 2025 announced that its other Data Center products reach end of life on March 28, 2029; Bitbucket Data Center is exempt and continues, with a hybrid license covering both Data Center and Cloud. The latest Data Center release is 10.5 (September 29, 2026), and 10.2 is the current long-term support version.

Why teams pick it

  • The tightest link to Jira: a work item key in a branch, commit or pull request links them, and Smart Commits update work items from commit messages
  • Cheap per user, with CI included: $3.65 per user a month on Standard, and Pipelines minutes shared across the workspace
  • Still self-hostable: Bitbucket Data Center continues after Atlassian’s 2029 Data Center end of life, with Mesh for replicated storage
  • Pull request pipelines test the merge with the destination branch, not just the branch on its own

Watch out for

  • Small hard limits: a Cloud repository stops accepting new commits at 4 GB, and a Free workspace gets 1 GB of repository storage in total
  • The Free plan stops at 5 users and 50 build minutes a month; enforced merge checks need Premium
  • Self-hosting now means Data Center: Server licenses lost support on February 15, 2024
  • Pull requests from forks don’t trigger pull request pipelines, and AI agent steps need a separate Rovo Dev license

Alternatives

What all version control have in common →Compare side by side →
GitHubCommercialThe largest Git host: repositories, pull requests, code review, issues and packages in one web service, owned by Microsoft since 2018 and used by more than 180 million developers.GitLabCommercialA Git forge sold as one application for the whole software lifecycle, from issues and merge requests to built-in CI/CD, packages and security scanning, that you can use on GitLab.com or run yourself.GiteaOpen sourceA lightweight, self-hosted Git forge in one Go program: repositories, pull requests, issues, a package registry and GitHub Actions-style CI, under the MIT license.ForgejoOpen sourceA self-hosted Git forge, like a small GitHub you run yourself: repositories, pull requests, issues, a package registry and built-in CI in one Go program, developed by a community under the non-profit Codeberg e.V. as a hard fork of Gitea.CodebergCommercialA public, non-profit Git forge for free and open-source projects, run on Forgejo by Codeberg e.V., a member-owned association in Berlin: repositories, issues, pull requests, CI, static pages and translations without a company behind them.RadicleOpen sourceA peer-to-peer code forge built on Git: every user runs a node that stores and shares repositories, and issues, patches and reviews travel inside the repository as signed Git objects, with no central server.

How it fits with other technologies

bitbucket-pipelines.yml: test every pull request merged with its destination · yaml

image: node:lts
pipelines:
  pull-requests:
    '**':                      # every pull request, whatever its branch name
      - step:
          name: Test the merge result
          script:
            - npm ci
            - npm test
  branches:
    main:
      - step:
          script:
            - echo "Runs on every commit to main"

See it in a real stack

No architecture uses Bitbucket yet. Drop it into the playground and wire it up yourself.Open playground →
Where it came from2010–2025

Bitbucket began as an independent hosting service for Mercurial repositories, run by its co-founder and CEO Jesper Nøhr. When Atlassian bought it on September 29, 2010 it had more than 60,000 accounts. Atlassian switched it to pricing per user with unlimited repositories, free for up to 5 users with private repositories, and said it would stay neutral about version control. A year later, on October 3, 2011, Bitbucket added Git repositories next to Mercurial ones.

For companies that wanted Git behind their own firewall, Atlassian released Stash 1.0 on May 1, 2012, and renamed it Bitbucket Server with version 4.0 on September 21, 2015. Meanwhile Git won: in August 2019 Atlassian announced it would remove Mercurial from Bitbucket Cloud, because fewer than 1% of new Bitbucket users chose it. New Mercurial repositories were blocked from February 1, 2020, and every Mercurial repository was disabled on August 26, 2020.

Atlassian then pushed customers toward its cloud. Server products lost support on February 15, 2024, and on September 8, 2025 Atlassian set the end of life of its Data Center products for March 28, 2029. Bitbucket was the exception: Bitbucket Data Center continues, and its customers get a hybrid license that also covers Bitbucket Cloud.

Why it’s built this way

Start with Mercurial, then go Git-only
Bitbucket was the main host for Mercurial when Atlassian bought it. By 2019 under 1% of new users picked Mercurial, while Stack Overflow’s 2018 survey had almost 90% of developers on Git, and Atlassian decided supporting two systems split its engineering effort.
Built around Jira
Atlassian sells Bitbucket as part of a suite. Work item keys in branches, commits and pull requests link code to Jira, and Smart Commits let developers comment, log time and change a work item’s status without leaving Git.
Keep a self-managed Bitbucket after all
Atlassian retired Server in 2024 and is retiring Data Center for Jira, Confluence and its other products by 2029, but it exempted Bitbucket Data Center and offered a hybrid license, so customers can keep source code on their own machines.

Timeline

  1. 2010

    Atlassian buys Bitbucket, a Mercurial host with 60,000 accounts (September 29)

  2. 2011

    Git repositories added alongside Mercurial (October 3)

  3. 2012

    Stash 1.0, a self-hosted Git server, released May 1

  4. 2015

    Stash renamed Bitbucket Server with version 4.0 (September 21)

  5. 2020

    Mercurial removed from Bitbucket Cloud; all Mercurial repositories disabled August 26

  6. 2024

    Bitbucket Server and other Atlassian Server products lose support (February 15)

  7. 2025

    Atlassian sets Data Center end of life for March 2029, with Bitbucket exempt (September 8)

Sources13 · facts checked 20 October 2026

Improve this page on GitHub