cloudparts

Sonatype Nexus Repository

Sonatype’s repository manager, born from Maven: proxy, hosted and group repositories for Maven, npm, PyPI, Docker and more, in a free Community Edition capped by usage or a paid Pro edition.

Type
Commercial product
Made by
Sonatype, Inc.
License
EPL-1.0 core; Community Edition is free with usage limits; Pro is proprietary
Facts checked
24 October 2026

What it is

Nexus Repository is a Java server that hosts components and proxies public registries. A proxy repository caches content from a remote source: it serves from its cache, and checks upstream again once the larger of two settings, Maximum Component Age and Maximum Metadata Age, has passed. A hosted repository is the authoritative store for what you publish, such as maven-releases and maven-snapshots, which enforce release and snapshot version policies. A group repository combines repositories behind one URL, and its order matters: Nexus searches the first member, then the next. A new install comes with maven-public, a group of the Maven Central proxy and the hosted release and snapshot repositories.

It comes in three forms. The open-source core on GitHub, under the Eclipse Public License 1.0, supports only Maven, raw and APT repositories with an embedded H2 database. The free Community Edition binary adds npm, Docker, NuGet, PyPI, Cargo, Hugging Face and other formats and can use an external PostgreSQL database, which allows running it on Kubernetes. Above 40,000 components or 100,000 requests a day, Community Edition stops accepting new components until usage drops again, and Sonatype points users to Pro, which adds high availability, replication and SSO.

Nexus 3.71, in 2024, dropped the embedded OrientDB database that the 3.x line had used since 2016; instances must first migrate to H2 or PostgreSQL from the last 3.70.x release, and must run on Java 17. The current release line is 3.97, from October 2026.

Why teams pick it

  • The most widely deployed free repository manager for Maven, with years of documentation and community answers
  • Clear proxy, hosted and group model, with Maven release and snapshot policies built in
  • Community Edition covers the common formats, Docker included, at no cost for small and medium installations
  • PostgreSQL support makes container and Kubernetes deployments straightforward

Watch out for

  • Community Edition blocks new uploads above 40,000 components or 100,000 requests a day; the threshold was 100,000 components and 200,000 requests when it launched in 2025
  • Most formats are not in the open-source core, so the EPL code alone is not a usable multi-format registry
  • High availability, replication and SSO need a Pro licence
  • Upgrades need planning: leaving OrientDB requires a one-way migration from 3.70.x, and Java 8 and 11 are no longer supported

Alternatives

What all artifact registries have in common →Compare side by side →

How it fits with other technologies

Maven settings.xml: send every request to the maven-public group · text

<settings>
  <mirrors>
    <mirror>
      <id>nexus</id>
      <mirrorOf>*</mirrorOf>
      <url>https://nexus.example.com/repository/maven-public/</url>
    </mirror>
  </mirrors>
</settings>

See it in a real stack

No architecture uses Sonatype Nexus Repository yet. Drop it into the playground and wire it up yourself.Open playground →
Where it came from2005–2026

In December 2005 Tamás Cservenák started Proximity, a small web application that proxied Maven artifacts so his systems could get past a very slow ADSL connection from a Hungarian ISP. In 2007 Sonatype asked him to help build a similar product named Nexus, which absorbed all of Proximity’s code and offered its users a migration path.

Nexus became the most common repository manager in front of Maven Central: Sonatype counted 42,000 instances connecting to Central in September 2014, up from 21,000 fifteen months before. Nexus Repository 3.0, released in April 2016 on a new runtime, added hosting a private Docker registry and better npm support next to Maven and NuGet, and called itself the first completely free repository manager for the most popular formats.

The 3.x line used the embedded OrientDB database, which lost vendor support. In 2024 Nexus 3.71 required moving to H2 or PostgreSQL. In February 2025 Sonatype’s Brian Fox announced Community Edition, replacing the old OSS download: PostgreSQL and formats such as Cargo, Composer and Hugging Face became free, in exchange for usage limits on the largest installations, which Sonatype said were about 5% of instances. Sonatype has since lowered those limits to 40,000 components or 100,000 requests a day.

Why it’s built this way

Group repositories searched in order
A Maven build listing many repositories asks each in turn. Putting them in one group with a set order gives every client a single URL and lets administrators add repositories without touching build files.
Separate release and snapshot repositories
Maven treats release versions as immutable and snapshots as moving targets; hosted repositories with a version policy keep the two apart so a release can never be overwritten.
Usage limits instead of a feature-only free tier
Sonatype said keeping several database backends was unsustainable and heavy free users reached it only after their repositories were overwhelmed; Community Edition gives PostgreSQL to everyone and asks only the largest installations to pay.

Timeline

  1. 2005

    Tamás Cservenák starts Proximity (December)

  2. 2007

    Sonatype asks him to build Nexus, which absorbs Proximity

  3. 2014

    42,000 Nexus instances connect to Maven Central (September)

  4. 2016

    Nexus Repository 3.0 adds a private Docker registry (April 13)

  5. 2024

    3.71.0 drops OrientDB and Java 8 and 11

  6. 2025

    Community Edition replaces OSS, with usage limits (February 4)

  7. 2026

    3.97 is released (October 14)

Sources6 · facts checked 24 October 2026

Improve this page on GitHub