An Update on Maven Central Publisher Pro⚓︎
Published: July 16, 2026
Since publishing our Maven Central Publishing Limits announcement, we've heard from many publishers across the community. We want to share where things stand and what to expect next.
Publishing limits implementation date moved to October 1, 2026
We are moving the planned implementation date for publishing limits to October 1, 2026. This gives us more time to incorporate community feedback, adjust limits where appropriate, continue analyzing publishing patterns, and process the requests already in the queue before any additional hard limits are enforced.
Thank You for Engaging With Us⚓︎
First, thank you. The feedback has been substantial, thoughtful, and overwhelmingly constructive. Publishers have explained their release patterns, pointed out edge cases, and raised fair concerns about how these changes could affect their projects.
That is what the soft-limit phase was meant to surface. The feedback is helping us improve the rollout, and we want the community to know it is being heard.
This Has Always Been About Sustainability⚓︎
The goal of this effort has always been the long-term sustainability of Maven Central.
That means two things. First, reducing clear waste and limiting potential abuse, especially publishing patterns that create unnecessary storage, operational load, or support burden without meaningful benefit to the ecosystem. Second, creating ways for commercial entities that derive value from open source infrastructure to help support the infrastructure they depend on.
Maven Central exists for the benefit of the broader open source ecosystem. We do not want to create unnecessary friction for legitimate community open source projects. At the same time, operating reliable global infrastructure at this scale is not free. We need a model that keeps Maven Central open and dependable without placing the burden unevenly on the community.
We're Adjusting the Metrics We Use⚓︎
Your feedback has also changed how we're thinking about publishing limits, usage signals, and Maven Central Publisher Pro pricing.
The clearest lesson is that limits are useful checkpoints. They help identify publishing patterns that deserve a closer look, especially when activity creates avoidable waste, operational strain, or unusual load on the service.
But those same limits do not translate cleanly into commercial pricing. File count, release count, and release size can be useful signals, but they can also reflect project structure, build tooling, platform support, or release practices. They are not always a good measure of commercial value.
We are also exploring additional ways to identify commercial publishing activity. This matters because part of the sustainability challenge is making sure commercial entities that benefit from Maven Central can help support it. We want that work to stay focused on commercial usage patterns, not on creating friction for legitimate community open source projects.
Our original goal was to avoid pricing based on factors commercial publishers cannot fully control, such as project popularity or downstream downloads. At the same time, we've heard that this is the dimension many commercial publishers expect pricing to account for, because it is also the dimension that would drive consideration of self-hosted alternatives.
That is the balance we are working through. Maven Central creates value by keeping the JVM ecosystem connected. Publishers get broad reach and easier access for users, while users get a consistent, trusted place to download dependencies. We want Maven Central Publisher Pro pricing to recognize that value without encouraging fragmentation into thousands of separate commercial repositories.
As a result, publishing limits will remain as reasonable review checkpoints, but we are building separate commercial pricing models rather than using those limits as the primary basis for pricing. This work is still in development. As soon as we have a clearer picture of timing and pricing structure, we will update the community here and in the Usage Center.
OSS Exemptions Are Still Open, and Limits Will Be Adjusted Where Appropriate⚓︎
Legitimate community open source projects can continue to request review if their publishing patterns exceed the standard limits.
As our thinking has evolved, we expect full exemptions from publishing limits to be relatively rare. The primary path will be to increase limits for open source projects where the standard thresholds do not fit their publishing patterns. The goal is not to force maintainers into unnatural release practices, restructure projects, or avoid legitimate publishing behavior. Limits give us a checkpoint to inspect unusual activity, adjust thresholds where appropriate, and identify cases where unnecessary publishing may be creating avoidable waste or operational strain.
Alongside individual requests, we are continuing to analyze different types of projects and publishing patterns across Maven Central. Where we identify categories of legitimate open source activity that are not well served by the standard thresholds, we may make broader adjustments before rolling out any additional hard limits.
Requests submitted to central-support@sonatype.com are being queued and worked through. Every request received before rate limiting begins will be reviewed and resolved before hard limits are enforced against that organization.
If you've already submitted a request and haven't heard back yet, you don't need to resubmit. If you haven't submitted one yet but believe your project's publishing pattern warrants review, see Community Open Source Publishing for what to include.
Pricing for Lower-Tier Commercial Plans Is Coming Soon⚓︎
We've also heard that publishers want to understand Maven Central Publisher Pro pricing before committing to it, particularly smaller commercial publishers that do not need the highest tiers of capacity. We are working on pricing for our lowest commercial offerings and expect to share that shortly.
Questions⚓︎
If you have questions about your organization's usage, an exemption request already in the queue, or Maven Central Publisher Pro, contact central-support@sonatype.com. We'll keep posting updates as these changes take shape, and we appreciate the community's patience and continued feedback.