Sonatype Nexus Repository Overview

Sonatype Nexus Repository is the #1 ranked solution in our list of top Software Distribution tools. It is most often compared to JFrog Artifactory: Sonatype Nexus Repository vs JFrog Artifactory

What is Sonatype Nexus Repository?
Nexus Repository is powered by Repository Manager, the same technology engine found in our OSS version deployed at more than 100,000 organziations world-wide. It is Built on the shoulders of Maven, Repository Manager supports all popular component formats and brings your entire development organization together. It includes staging and release functionality that provides support for operations and quality assurance processes prior to production and gives you instant insight into potential component security, license, and quality issues, enabling teams to take corrective action early and quickly.

Sonatype Nexus Repository is also known as Nexus Repository, Nexus Repository Manager.

Sonatype Nexus Repository Customers
Goldman Sachs, Toyota, Disney, Deutsche Bank
Sonatype Nexus Repository Video

Pricing Advice

What users are saying about Sonatype Nexus Repository pricing:
  • "One of the challenges we had around licensing was how to deal with anonymous requests. According to the letter of the contract, an anonymous request consumes a license. We had to do some work to get over the fact that any anonymous interactions with the Repository product had to be put back to an end-user account."

Filter Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
ColinStandish
Project Manager at a hospitality company with 10,001+ employees
Real User
Top 20Leaderboard
Vastly improved our whole release cycle; automated processes help to deliver code

What is our primary use case?

We happily use containers as a way of scaling out microservices so we use Nexus Repository for the management of containers, as a kind of repository. That's about 50 percent of what we use it for. The other side is that it is used for application and development artifacts. We use it to track artifacts in a repository so we can deploy software code. It's not a code library because we GitLab as well. It's more for the compartmentalized aspect that fits in and we can redeploy those on-demand. The way we deploy it is private cloud, ultimately. We have an internal cloud infrastructure that we… more »

Pros and Cons

  • "The key benefit we get from it is speed to delivery. It has improved our overall time to get new applications out with new code. That's true whether from a platform perspective, where we are quickly deploying up-to-date docker containers, or whether we are looking to deploy new code out to deliver a new application."
  • "We've had some challenges around the database they use. We've had some big outages and it's due to the fact that we haven't found the database they use is all that stable... We've had some really positive conversations with Sonatype around that and they've provided us with the support and special services to help us migrate off of that, on to another type of database platform which we have more control over."

What other advice do I have?

Talk to Sonatype about how flexible they can be around their licensing. We did purchase 500 licenses, but initially we were around 20. Rather than paying for the whole thing, I would say, "If we commit to the 500 over a particular period of time..." and have that conversation about what a realistic ramp-up would be. See if you can be charged for the number of users you have, rather than paying for 500 users but only using 20, which is what we did. It wasn't an effective use of money at that point. If I was doing it again, I'd have a better commercial conversation with them around how we could…