Sonatype Nexus Repository | Upgrade to Pro

Sonatype Nexus Repository Pro

Designed to Scale with Your Organization

Are you experiencing usage warnings? Your instance of Nexus Repository OSS uses OrientDB, an embedded database not intended for demanding and high concurrency usage.

Deploy appropriately at scale with Nexus Repository Pro using PostgreSQL (a scalable external database) to avoid disruptive outages, data corruption, and long, unplanned recovery times. Available in the Sonatype Cloud, Self-Hosted, or On-Prem — let us help you migrate.

Upgrade to Sonatype Nexus Repository Pro

#### Features Sonatype Nexus Repository OSS Sonatype Nexus Repository Pro
High Availability no yes
Staging & Build Promotion no yes
SAML/SSO, LDAP, Auth Tokens no yes
Runtime Storage Expansion/ Migration no yes
Content Replication no yes
Custom Component Metadata no yes
World Class Support no yes
Universal Repository Support yes yes
Private Hosted Repositories yes yes
Role-Based Access Controls yes yes
REST APIs yes yes

Frequently Asked Questions

Why am I seeing warnings?

Usage warnings appear at 75% of usage, and are designed to warn Repo Administrators that you’re utilizing your database beyond its intended levels. Going over recommended usage levels make your database prone to:

What is the intended usage for Sonatype Nexus Repository OSS?

Sonatype Nexus Repository OSS is designed for smaller projects and usage scenarios that fall into:

Why should I upgrade?

Nexus Repository Pro offers expanded capabilities and support for larger workloads.

By upgrading your Nexus Repository from OSS to Pro, customers avoid the following obstacles:

What are my deployment options?

Sonatype Nexus Repository is used every day by millions of developers to manage and secure billions of component and application downloads. Sizing correctly is super important to ensure that developers can develop, test, and ship code quickly at scale without costly interruptions.

Please see our Reference Architectures for Nexus Repository to ensure your deployment is appropriately sized to meet the ever growing need to serve components and application binaries at scale.