Few months back we launched Bitbucket Packages with a native container registry, giving teams a way to manage container images right alongside their code and pipelines.
Today, we’re expanding that functionality and now Bitbucket Packages support Maven and Node Package Manager (npm), bringing JavaScript and Java package management into the same platform where your team already writes code, reviews pull requests, and runs pipelines.
Why we built this?
When we launched container registry support, it addressed a genuine need for teams managing container images. But customers told us containers alone weren’t enough. Their workflows cut across multiple package types, and while container images were taken care of, npm and Maven artifacts still lived in entirely separate registries, each with its own billing, access controls, and learning curve. That fragmentation causes real problems:
- Duplicated permissions: Teams that have already configured repository access shouldn’t have to repeat that setup in a separate artifact tool.
- Broken flow: Jumping between tools mid-workflow slows developers down and opens the door to security gaps.
- Unnecessary cost: Every extra platform in the toolchain adds its own price tag and administrative burden.
What’s included
- Publish and install Maven and npm packages: Create a package in Bitbucket, configure authentication with an Atlassian API token, and start publishing and installing packages using your existing tools like npm, Yarn, Maven, or Gradle. If you’re publishing from Bitbucket Pipelines, built-in environment variables (
BITBUCKET_PACKAGES_USERNAMEandBITBUCKET_PACKAGES_TOKEN) can be used as your authentication credentials. - Unified permissions with no extra setup: Every package is scoped to a Bitbucket repository. That means the repository permissions you’ve already configured (Admin, Write, Read) automatically apply to every package tied to that repo. There’s nothing additional to configure, and no separate access control system to maintain.
- Full visibility into your packages: Browse, inspect, and manage your packages and their versions directly from the Packages page, available at the workspace, project, and repository level. Delete what you don’t need to keep your registry lean and your costs predictable.
How much does it cost?
Maven and npm packages are bundled into the same Packages feature as container images. Storage and network limits for plan inclusions are shared across all package types (containers, Maven, and npm). So the same model, same meters, and same plan inclusions apply. Packages are available on monthly Standard and Premium plans. Annual plan support is on our roadmap for next year.
| Standard | Premium | |
| Included Storage | 1 GB | 2 GB |
| Storage Overage | $0.35 per GB/mo | $0.35 per GB/mo |
| Included Network Traffic | 5 GB | 7 GB |
| Network Overage | $0.70 per GB/mo | $0.70 per GB/mo |
Getting started
To start using Bitbucket Packages, ensure that your Bitbucket workspace is connected to an Atlassian organization. If you haven’t connected your workspace yet, follow these steps to do so. You must be on a paid monthly plan (Standard or Premium), and personal workspaces are not supported.
Once you’ve connected your workspace, you can start to use Bitbucket Packages. You’ll see a Packages tab in the left navigation of your workspace, project, and repository page.
If your workspace is already set up for Packages with container images, Maven and npm registries are ready to use in the Packages tab of your repository. Check out our Maven support documentation and npm support documentation for step-by-step to get started.
What’s next
Maven and npm are the first language registries, not the last. We’re actively working on expanding Bitbucket Packages further:
- More language registries: Python Package Index (PyPI) and NuGet are coming up next, driven by what we hear from you.
- Immutable tags: Prevent accidental overwrites to strengthen deployment confidence.
- Per-type usage breakdowns: Better visibility into how each package type contributes to your storage and network.
Share your feedback
Every expansion of Bitbucket Packages has been shaped by community feedback and this one is no different. Let us know how Maven and npm support is working for your team, what registries you want to see next, and what would make Packages even more useful for your workflow. Drop your feedback and request in the Bitbucket community.
