Clarifying Maven Central Publisher Tiers and Commercial Use

Published: September 8, 2026

← Back to News Archive

As the Maven Central publishing-limits rollout continues, we have updated our documentation to clarify how Publisher Tiers and Commercial Use apply.

Maven Central remains free for ordinary community open source publishing. The new publishing limits are designed to focus on sustained high-volume publishing activity, using file count, release size, and release count.

However, publishing volume is not the only factor that determines whether a paid subscription is required.

Two independent considerations

From October 1, 2026, Maven Central Publisher Pro is required if either of the following applies:

1. Your organization's publishing activity exceeds the applicable free publishing thresholds and you do not have an adjusted limit or approved exemption; or

2. Any artifact you publish has a commercial nature, regardless of your organization's publishing volume.

An artifact has a commercial nature if it supports the adoption, integration, or operation of your organization's commercial product or service. This can include service-dependent SDKs, generated clients, drivers, agents, integrations, platform components, build tooling, developer tools, and other software distributed as part of a commercial offering.

Remaining within the free volume thresholds does not create a volume-based exception for commercial-nature artifacts.

What this does and does not mean

Being maintained by a company does not automatically make an open-source project commercial in nature. The relevant question is whether the artifact is part of a commercial product, service, or go-to-market motion. As we've written about separately, defining community open source is harder than it looks, and no single signal, such as license, public repository status, or download volume, settles the question on its own.

A company may also publish a mix of commercial-nature artifacts and genuinely community open-source artifacts. In that situation, publishers may request review of community artifacts that are not part of any commercial go-to-market activity on a per-artifact or per-group-ID basis.

What publishers should do now

Before October 1, please review your organization's publishing activity and the role each published artifact plays:

• Community open-source projects with unusual publishing volumes may request higher limits or an exemption.

• Publishers with commercial-nature artifacts should evaluate Maven Central Publisher Pro.

• Organizations that publish a mixture of commercial and non-commercial community artifacts may request per-artifact or per-group-ID review for the community artifacts.

During the current soft-limit phase, notifications are informational only and publishing continues without interruption. Rate limiting begins on October 1, 2026.

For full details, see the Maven Central Publishing Limits documentation, the Central Publisher Terms, and our blog post on defining community open source.

We appreciate the feedback from publishers that has helped us clarify this rollout, and we will continue to post updates as implementation progresses.