Sonatype Nexus Repository is a repository manager sold as Pro, Pro+ and Enterprise, with a free Community Edition capped by usage limits; these pages cover replacing it with self-hosted Pulp for packages and Harbor for container images.
Comparing Nexus Repository with Pulp for Maven, npm, Python, RPM, Debian and container content: format coverage and plugin maturity, proxying and hosting, high availability, the REST API and CLI against Nexus's UI, and licensing on each side.
For teams that mainly host Docker images and Helm charts in Nexus: Harbor's projects, RBAC, Trivy scanning, replication and proxy cache against Nexus Docker repositories, and why Maven and npm repositories would still need another home.
Moving Nexus hosted and proxy repositories to Pulp: inventorying formats and repository types, syncing proxy content from upstream again, re-uploading hosted artifacts, pointing Maven, npm and pip clients at new URLs, and checking 0.x Pulp plugins first.
Moving Nexus Docker hosted and proxy repositories to Harbor: pulling images through Harbor replication from a Docker registry endpoint, re-creating proxy repositories as proxy cache projects, mapping roles and LDAP groups, and updating image references in clusters.
Nexus Repository Community Edition blocks new components above 40,000 components or 100,000 requests per day. This page weighs buying Pro, staying on the EPL open-source core with its narrower formats, or moving to Pulp and Harbor.
Cost of ownership by component: Nexus Pro self-hosted or cloud subscriptions and consumption, PostgreSQL and high availability, against Pulp and Harbor infrastructure, object storage, migration effort and support.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.