Bitbucket — The Atlassian Git Host

• Bitbucket Cloud — SaaS. Pipelines as CI, branch permissions, code insights. Per-user pricing.
• Bitbucket Data Center — self-hosted, formerly "Bitbucket Server". Runs in your network for regulated workloads. Atlassian retired the cheaper "Server" tier in 2024; Data Center is the only on-prem path now.

Atlassian Cloud is the default the company is investing in. New features land there first.

• Jira ↔ Bitbucket. A branch named PROJ-123-fix-foo auto-links to ticket PROJ-123. PR status, build results, deployments all surface on the Jira issue.
• Smart Commits. Type PROJ-123 #close #time 2h in a commit message to transition the ticket and log time without leaving the editor.
• Pipelines. CI defined in bitbucket-pipelines.yml. Container-based, parallel steps, deployment environments. Capable but smaller marketplace than Actions/GitLab.
• Code Insights surface coverage, lint, and security results inline in PRs from any third-party scanner.

• Smaller community than GitHub or GitLab. Fewer pre-built pipeline pieces, fewer Stack Overflow answers when something is weird.
• UX leans enterprise. Slower iteration than competitors; users sometimes wait years for parity features.
• Mercurial support is gone. Bitbucket dropped Hg in 2020 — repos that didn't migrate were deleted. Today it is Git-only.
• Best fit: shops already standardised on Jira + Confluence. Outside that gravity well, GitHub or GitLab is usually the better default.