Read reviews of JFrog Artifactory alternatives and competitors

Joseph_Lim - PeerSpot reviewer
Principal Engineer at Interos Solutions, Inc.
Real User
Top 10Leaderboard
Feature-rich and seamless integration with our other tools
Pros and Cons
  • "Navigation on the UI is easy and simple to understand."
  • "Lacks an end-to-end solution for developers to sign and store an image."

What is our primary use case?

Our primary use case of this solution is for our CICD pipeline, to build and store our artifacts in the repository. I'm the principal engineer and we are customers of Sonatype. 

How has it helped my organization?

We previously used a clunky system that required logging on to AWS IAM before reaching out to the CodeArtifacts and it would then expire after 12 hours. This required additional maintenance for developers so we were looking for a more efficient solution. Nexus provides a single sign-on that doesn't expire unless you change your password. The developer logs in once for the entire day which increases efficiency and helps the developer to more easily maintain the workflow.

What is most valuable?

In comparison to solutions like JFrog, Nexus provides ease of use. Navigation on the UI is easy and simple to understand. In addition, the integration with the rest of our CICD tools like Jenkins and GitLab CI is pretty seamless with very little additional work that needs to be done. Sonatype is feature-rich, even in the open-source version and what they offer is easy to understand, nicely documented and it fits very well into our environment.

What needs improvement?

One issue is that Nexus Repository doesn't have an end-to-end solution that helps developers easily sign an image and store it or to deploy that image if it's not signed. We're looking for other tools to help us with that. We'll continue to use Nexus but only for storing our artifacts. It would be great if Nexus had some features to help us maintain our container images as well. The solution could be more intuitive.

We are using goharbor for our container registry. It has a feature that helps us to define a pattern and other features that have allowed us to configure the container images more easily. In that sense, Nexus is not as feature-rich. I'm hoping that the features we use on goharbor will be integrated into Nexus and then we won't need as many tools to run our infrastructure. 

For how long have I used the solution?

I've been using this solution for five years. 

What do I think about the stability of the solution?

Stability is not entirely the responsibility of Nexus. The cloud provider needs to provide stability on the backend side as well. We haven't had any problems and the solution is stable. 

What do I think about the scalability of the solution?

We haven't reached the scalability stage yet but I'm quite sure that it is pretty solid because as long as you're using a backend that supports high availability, it will be fine. We have around 150 users who are mainly engineers.

How are customer service and support?

We haven't needed to use technical support. 

How was the initial setup?

The deployment is straightforward and the solution is very easy to set up. If the solution is only for a lab playground, everything will run in one container, and that's easy. If additional configuration is required for production usage in a high availability area then deployment will be more complex. We have in-house engineers who do this for us. 

What's my experience with pricing, setup cost, and licensing?

We are using the open-source solution which is free.

What other advice do I have?

It's important to know that the solution will not be able to fit perfectly with your use case and other tools will be required.

I would rate this solution nine out of 10. 

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate