We’re excited to announce that Bitbucket Packages will be launching later this year. Packages will provide a central place to publish, manage, and consume artifacts, starting with container images.
The first release of Packages will include support for Docker images via a built-in container registry. Over time, we’ll expand Packages to cover additional languages and ecosystems, making Bitbucket a single home for your code, pipelines, and artifacts.
Important: To access Packages when it becomes available, you need to link your Bitbucket workspace to your company’s Atlassian organization.
Why we’re introducing Packages
Today, many Bitbucket users depend on external registries and artifact services. This approach introduces several pain points:
- Context switching: Teams must jump between Bitbucket and third-party systems, disrupting productivity.
- Separate permission management: Access has to be configured and maintained in multiple places, increasing risk.
- Multiple vendors: Using separate tools for code, CI/CD, and artifact storage leads to fragmented workflows and duplicated costs.
Our Packages feature is designed to simplify your workflow and save you money.
What you will get
When Packages launches, you’ll have:
- A workspace-level namespace for container images, integrated directly into Bitbucket Cloud.
- Repository-linked images that inherit repository permissions by default.
- A unified developer experience, where your source code, pipelines, and artifacts live together in one place.
Availability and pricing
Packages will be available for Bitbucket Standard and Premium workspaces on monthly plans, with annual plans coming soon.
- Packages will be a consumption-based feature, with base limits for storage and network transfer included in your plan.
- Additional usage will be billed based on actual consumption, giving you flexibility, and ensuring that you only ever pay for what you actually use.
We’ll share more details about limits, tiers, and billing closer to launch.
Prerequisites to get access
To access Packages as soon as it becomes available, you’ll need to take one important step: Link your Bitbucket workspace to your company’s Atlassian organization.
This will unlock access to our new billing experience (required for packages billing), which you will be automatically migrated to once you have successfully linked your workspace to an organization.
Looking ahead
We’re thrilled to introduce container image support in Bitbucket Packages this year, with plans to expand to additional package types in the future. To learn more about how permissions will be handled with Packages, visit our community thread . We’d love to hear your feedback and questions there.
We’re excited to launch this feature in the next few months to help you simplify your workflows.