We didn't look at any of the competing products at the time because we were happy with what we're getting from the open-source product. And we were happy with the conversation that we had with Sonatype around their Repository enterprise product. So we went with that.

Our company used JFrog. 

For Repository Manager we did a comparison with Artifactory. Regarding Nexus IQ, we did a comparison with Palamida which is now Flexera. We also did a comparison with Black Duck.

There were not that many competitors in this space. It was between Nexus and Artifactory. It was a pretty straightforward decision.

We began to evaluate different Maven-based repository managers, so we had Artifactory, Nexus, Archiva from Apache, and IBH SYSTEMS. After an evaluation period of three to four months, we decided to go for Nexus, as it is one of the most important players in the field. We also had a vision of incorporating Docker images and the like, which was only supported in Nexus at that point of time.

Another difference between them is that Nexus provides Enterprise Support. That is available with Artifactory, but the biggest argument for Nexus was that you could use stuff like Docker proxying, Docker repositories, proxying NPM repositories, etc. We needed a system that's not only for the Java toolchain, but also for C#.

It was already in place, but I am satisfied with it.

There are a couple of solutions that I have used in the past, before using Nexus. They're as effective as Nexus. When I joined the team, they were already using Nexus and it was being used very effectively in the company, within our team, and across all the different users. I didn't see any reason to ask that we go ahead and switch a different tool.

There were other options. Veracode was one of them.

I'm not sure if they evaluated other products. But people have used Nexus a lot and they are quite comfortable with it.