Sonatype Nexus Repository Pro (Self-Hosted)

We have other tools we use integrated into the pipelines, so when we run the pipeline, part of it is the scanning.

The benefit of Sonatype Nexus Repository  is that you get an idea about open source or third-party libraries vulnerabilities.

The Health Check feature for repositories is for identifying vulnerabilities, and vulnerabilities normally come from the tool itself. I use the Health Checks to identify whether a vulnerability really applies to what we have or not.

Sonatype has features for managing NPM , Docker , and Maven, which helps with development environments by connecting with those third-party libraries.

Having it centralized in Sonatype Nexus Repository  is a major benefit for any organization, as it helps maintain a secure environment.

I see a great feature that allows waving vulnerable components that cannot be fixed immediately due to various limitations.

It would be great if notifications were implemented for waivers, as currently we rely on users to inform us or check manually.

Sonatype Nexus Repository is on the high side regarding price, especially for components such as Firewall.

I have been using Sonatype Nexus Repository for more than two years now.

Sonatype Nexus Repository is reliable, and I believe it is scalable, but I do not have personal experience with scaling.

My impression of Sonatype's customer support and technical service is positive.

I have not worked with other competitors yet, so I cannot compare it right now, but I know they are one of the top ones in the market.

The installation process for Sonatype Nexus Repository is managed by a team that is not involved with security directly, so I am not sure how complex it is.

Time definitely is saved by using Sonatype Nexus Repository, as security is a requirement.

I am still using the same products, maybe different versions of it. Last time it was OpenText  Fortify. They contacted me regarding this.

I have not worked with OpenText Contact Center Analytics  for customer data analysis, though I have heard of it.

I am also using Sonatype Nexus Repository now.

I get the vulnerabilities, and you get what it is doing.

Recently, they acquired something called Firewall, which is another component on top of this, so you can block things and allow things, which is very useful for security.

They stand out in their field.

Sonatype Nexus Repository is doing our purpose well. My overall review rating for this product is 9.

I use Sonatype Nexus Repository  for downloading packages. My application was Java-based and Spring  Boot-based, so I was downloading packages from Sonatype Nexus Repository  and uploading the WAR file that was built during the CI process to Sonatype Nexus Repository.

In my CI/CD process, there was a Sonatype Nexus Repository upload stage that was executed after completing stages such as build, Sonar  scan, Sonatype Nexus IQ scan, and testing. Once all these stages were completed and the WAR file was built, the Sonatype Nexus Repository upload stage would upload the WAR file of my Java application to Sonatype Nexus Repository. In the deployment stage, I would download those WAR files to the servers.

Sonatype Nexus Repository was very helpful because currently, there are around 20 to 30 microservices in our application and my client was a big network provider in the UK with many projects. They used Sonatype Nexus Repository to store the JAR and WAR files of all their applications that were being built. This helped with efficiency because before using Sonatype Nexus Repository, everyone was using Jenkins  and storing the JAR and WAR files on their local server where Jenkins  was running. After implementing Sonatype Nexus Repository, we could have JAR and WAR files and all packages in a central place where they could be stored for a longer time. Additionally, files could not be accidentally deleted, and I could maintain different versions of the JAR and WAR files by tagging them with different names.

For version management in Sonatype Nexus Repository, I could have multiple versions of the same WAR file. For example, if an application was being built during the CI process, I could tag it with 'A-1' and upload it to Sonatype Nexus Repository. During another stage, I could upload it as 'A-2'. In this way, I could manage versioning and it helped with long-term storage. I could use the same JAR file after six to seven months, and if I had not deleted that WAR file and had not used any lifecycle policy, I could still access it.

The user interface of Sonatype Nexus Repository was fine and not too bad overall. However, some aspects of the user interface were not ideal because if a JAR or WAR file was uploaded, I might find it difficult to delete that particular JAR or WAR file, as it was somewhat embedded deep within the UI and required significant navigation to delete the WAR file. This was the UI problem I experienced. Otherwise, I have not encountered any other problems with the UI.

I was experiencing some network connection issues with Sonatype Nexus Repository because of high RAM usage. However, I was not certain whether that was the issue with Sonatype Nexus Repository or internal errors. Otherwise, I have not experienced any other issues with Sonatype Nexus Repository. Overall, it was a very good product.

I used Sonatype Nexus Repository for around 3.5 years.

Everyone was using Jenkins and storing the JAR and WAR files on their local server where Jenkins was running.

Time saved is what I can highlight with Sonatype Nexus Repository. There was no need for additional employees because that could be managed by a CI/CD pipeline. Typically, one or two people are needed for Sonatype Nexus Repository management.

Money saved is not significant because a license needs to be purchased. However, if choosing the free license, some money can be saved with Sonatype Nexus Repository.

Sonatype Nexus Repository is good for storing packages such as JAR and WAR files. I have not used it for other packages such as Python or other programming languages. However, for Java and Spring Boot  JAR and WAR files, there is flexibility in using Sonatype Nexus Repository. It can also use a small amount of storage if there is a small company. If there is a big company, NFS can be used and Sonatype Nexus Repository can also be installed on-premises or on the AWS  side. Both paid and free versions of Sonatype Nexus Repository are available.

I used Amazon Web Services  for AWS deployment purposes.

I am not certain about the pricing and licensing details because that was not handled by me. My overall review rating for Sonatype Nexus Repository is 7.5 out of 10.

I have been working with Sonatype Nexus Repository  for more than five years to manage different artifacts in my project.

Sonatype Nexus Repository  is used to maintain different private repositories. We create different private hosted repositories wherein we can maintain our artifacts including Java JAR files or WAR files. We create Docker  repositories to maintain our Docker  images. Helm repositories are created to manage our Helm charts. Additionally, we create Python repositories, pip repositories for managing Python packages, NuGet repositories for managing .NET artifacts, and NPM  repositories for managing Node packages. We also use Sonatype Nexus Repository for creating proxy repositories to cache artifacts, so once any particular machine accesses a public artifact from maven.com or npmjs, those artifacts are cached inside Sonatype Nexus Repository, and then those artifacts are served to the different project machines.

These are the primary use cases to manage all the artifacts across different projects. We mainly create hosted repositories and proxy repositories. We integrate these repositories with different CI/CD pipeline tools, for example, Jenkins , and we also integrate them with build tools like Maven. Using the build tool lifecycle phases, we deploy the artifacts to the artifactories. Additionally, we create different users on Sonatype Nexus Repository and assign them specific roles according to the user and job requirements. By implementing RBAC or Role-Based Access Control, we control access to our Sonatype Nexus Repository repositories. We also ensure to set up cleanup policies so that our Sonatype Nexus Repository server does not run out of disk space.

The integration with CI/CD tools is a standout feature for me in daily work. I also appreciate artifact management because compared to other artifact repositories like Jfrog, I find Sonatype Nexus Repository quite user-friendly in terms of its integration with different CI/CD tools and the different artifact management features. The security features are also quite useful; for example, you can install your SSL certificates to secure your Sonatype Nexus Repository. Additionally, the documentation of Sonatype Nexus Repository is quite comprehensive and very easy to follow. I find all the features quite user-friendly in Sonatype Nexus Repository.

Sonatype Nexus Repository has positively impacted our organization by configuring these proxy repositories, which have significantly reduced artifact management time. We have observed more than 50 percent time efficiency. Sonatype Nexus Repository allows us to maintain different hosted repositories within the company's network, which we would otherwise have to maintain over the internet. The internet push and pull for artifacts usually takes a lot of time, and our organization policies often do not allow accessing the internet for these kinds of artifacts due to security reasons. Sonatype Nexus Repository has significantly saved us efforts as well as time. We take a very good amount of control over our own repository management, which is something we really appreciate about Sonatype Nexus Repository.

I would like to explore the AI features in Sonatype Nexus Repository, such as the Sonatype MCP servers for automating the creation of repositories and user management. I have gone through some of the documents, but I have not explored this area much. I would be more interested in exploring these areas of Sonatype Nexus Repository now.

AI capabilities are an area for improvement, but I have not had the chance to work much with its AI features yet. Additionally, I think Sonatype Nexus Repository's free version could use more features. There are two versions of Sonatype Nexus Repository: a paid version and a free version. If the free version had more features, it could help people conduct effective proofs of concept, as the limited features often impact decision-making when evaluating tools against real-time use cases. If the free version includes more features while maintaining some usage limitations, it would greatly aid others in effectively validating Sonatype Nexus Repository for their actual needs.

If Sonatype Nexus Repository focuses more on integrating AI features to make usage more efficient, that would be great. User management and artifact management are all fine, but integrating AI capabilities effectively is something I would like to see in upcoming versions of Sonatype Nexus Repository.

I have been working in my current field for more than 10 years.

Sonatype Nexus Repository is very stable, and I have not experienced any issues with downtime or reliability.

Sonatype Nexus Repository is scalable. We have installed the repository inside Docker containers, and we have scaled those Docker repositories up easily without any issues.

We did not get a chance to interact directly with Sonatype's support team because the documentation is so well laid out that we managed to resolve any issues by referring to it. I would really appreciate the documentation team of Sonatype Nexus Repository for their excellent work.

We previously used Jfrog, but we switched to Sonatype Nexus Repository due to its user-friendliness and being feature-rich. These are the main reasons, as Sonatype Nexus Repository is straightforward to set up, user-friendly, and more feature-rich.

The setup cost for Sonatype Nexus Repository is not much, and it is easy to follow. The licensing is also reasonable, and we have no complaints regarding the costs associated with Sonatype Nexus Repository. We are quite satisfied with it.

We have seen a return on investment by saving significant time, more than 50 percent of our build and deploy pipeline time, leading to a clear ROI. Additionally, we save money because we transitioned from maintaining a lot of private repositories over public artifactories to Sonatype Nexus Repository. The efficiency and saved time are substantial. We have saved more than 50 percent of our time and money by shifting all artifact management to Sonatype Nexus Repository.

The setup cost for Sonatype Nexus Repository is not much, and it is easy to follow. The licensing is also reasonable, and we have no complaints regarding the costs associated with Sonatype Nexus Repository. We are quite satisfied with it.

To be very honest, we did not evaluate other options before choosing Sonatype Nexus Repository. We were convinced that it would be the best solution to replace Jfrog, so we went ahead with it without looking into anything else.

I would give eight out of ten for Sonatype Nexus Repository. I chose eight out of ten because it is feature-rich, and you can create all kinds of repositories. The installation process is also very easy, and the documentation is comprehensive and user-friendly. The overall user-friendliness of all features, from user management to artifact creation, is something I appreciate, which led to my rating of eight.

I haven't explored the AI features of Sonatype Nexus Repository much, but I have heard about some AI capabilities around governance and security. I have not worked on these features, so I cannot comment on them currently. Once I try these features and implement them in my project, I would be able to provide feedback.

Regarding accuracy and reliability, I believe there should be a focus on ensuring accuracy while minimizing any potential hallucination. I would like to see AI capabilities particularly around user management and artifact factory management, expecting around 85 to 95 percent accuracy and reliability from the AI capabilities of Sonatype Nexus Repository.

I would definitely recommend Sonatype Nexus Repository as it is a stable and user-friendly product. I believe that other teams can also achieve similar returns on investment as we have after implementing Sonatype Nexus Repository.

We are quite happy with Sonatype Nexus Repository, and I hope the Sonatype team will continue to serve us as they have for many years. My overall rating for this product is eight out of ten.

My main use case for Sonatype Nexus Repository  was as the repository for storing internally developed artifacts. As a developer while building applications, I pulled dependencies from Sonatype Nexus Repository . Dependencies such as Log4j, Spring Boot , and any other dependencies used in our applications would be pulled from Sonatype Nexus Repository.

As a big organization, Sonatype Nexus Repository positively impacted us by providing a centralized repository for storing all internally developed artifacts and third-party artifacts. Apart from speed and productivity, Sonatype Nexus Repository helped with security, which was possibly the main reason or outcome.

When I was using Sonatype Nexus Repository, I found the storage and pulling of dependencies to be really fast, and it was definitely a reliable tool.

Sonatype Nexus Repository was supposed to be one single storage area for internally developed artifacts. Developers had to pull their dependencies from Sonatype Nexus Repository. Since internally developed artifacts were from Sonatype Nexus Repository, we ensured that only vetted and approved artifacts were being pulled by all developers across the enterprise.

Based on what we had used at that time, I was not sure whether what we had was the full version of Sonatype Nexus Repository, but what we had at that point in time was primarily focused on pulling dependencies. I know Sonatype Nexus Repository now has firewall capabilities and scanning capabilities as well, scanning dependencies for vulnerabilities. At that point in time, it was only the pulling and storage of dependencies.

At that point in time, I was not exposed to all the features that Sonatype Nexus Repository offers today. The firewall feature, which is Nexus Firewall , and overall software supply chain security features that are now there with Sonatype Nexus Repository were not available back then. I believe Sonatype Nexus Repository has most of these features now.

I used Sonatype Nexus Repository for more than two years.

Sonatype Nexus Repository is stable.

Sonatype Nexus Repository was scalable.

One thing at that point in time was that Sonatype Nexus Repository was on-premises, so it did not require authentication. I am not sure how the SaaS model works right now, and I hope authentication and authorization using keyless authentication or workload identity federation is a part of Sonatype Nexus Repository today.

My advice to others looking into using Sonatype Nexus Repository is that if it is an enterprise as big as mine, definitely ensure that enterprise support is covered because a good volume of artifacts is going to be stored in the tool, so enterprise support is definitely recommended.

We use Sonatype Nexus Repository  for our internal repository, for image caching, registry caching, and our custom registry. Sonatype Nexus Repository 's repository function is definitely the most valuable feature I have found.

I did not test it extensively versus other options, but I can tell you that Sonatype Nexus Repository works in a stable manner. It allows us to have geographical disaster recovery, which was one feature that we needed.

We are using Sonatype Nexus Repository's granular access controls, and we needed to use them because we have several teams. Therefore, it is essential for us, and it is one of the features that we are using by design.

It is a requirement for managing Maven, npm , or Docker , so without it, we cannot do it. You need to have a product—this one or another—you need to have one.

Sonatype Nexus Repository's repository function is definitely the most valuable feature I have found.

I did not test it extensively versus other options, but I can tell you that Sonatype Nexus Repository works in a stable manner. It allows us to have geographical disaster recovery, which was one feature that we needed.

We are using Sonatype Nexus Repository's granular access controls, and we needed to use them because we have several teams. Therefore, it is essential for us, and it is one of the features that we are using by design.

I think what can be eventually improved is to introduce as a standard the additional security features that Sonatype Nexus Repository offers, which are basically plugins for the repository itself.

I have been using Sonatype Nexus Repository for 10 years.

I rate how stable and reliable Sonatype Nexus Repository is at a 10. We have had zero issues since we installed it, so it is wonderful.

We have had zero issues with Sonatype Nexus Repository, so I do not see any reason for it not to receive a 10 based on my entire experience with it.

I rate how scalable Sonatype Nexus Repository is at a 10 out of 10.

I often communicate with Sonatype's technical support and customer service. They are very good. I was mainly in touch with the pre-sales team, but they were always able to adjust to the needs that we had. They are absolutely excellent.

We used Sonatype Nexus Repository in the open-source version, which had some limitations.

I participated in the initial setup process of Sonatype Nexus Repository. It was very smooth because the pre-sales team of Sonatype did a very nice job, so it was easy to implement.

I used help from the vendor.

I would say that considering the environment and everything, for one person, I managed to save approximately one hour a month with Sonatype Nexus Repository. However, you need to scale this for the number of people that you have in the company. The bigger your organization is, the more benefit you get.

It is an adequate price for the features that you get.

We did not use the repository health check feature.

I have been working with Sonatype Nexus Repository since 2020, and I have continued working with it since 2022. Moving to the pro version of Sonatype Nexus Repository reduced our time to accomplish what we needed to some extent. My main focus is on the Geo-DR part because it is complex and not commonly offered. Most products handle it using external infrastructure, but Sonatype does not. It is self-contained and really helpful in order to move us to where we need to be.