JFrog Software Supply Chain Platform

My main use case for JFrog Artifactory  is hosting artifacts for products, ranging from Docker  images to Helm charts, and regular binaries.

I can give you a specific example of how I use JFrog Artifactory  in my workflow: we have automated steps in our pipelines where once we build our artifact, such as Docker  images, we push them to JFrog Artifactory, and then in the deploy pipeline, we have automated steps that pull the artifact from JFrog Artifactory and deploy them to different environments.

The best features that JFrog Artifactory offers are that you can have all kinds of artifacts, supporting many different ones such as Docker images, Helm charts, and different binaries from different software languages. It has versioning that you can use, proxying as well that you can use as a mirror proxy, and there is also nice access control around it, so you can limit who has access to which parts of your JFrog Artifactory tree.

Regarding access control and proxying, those features help my team by making it easy to provide read access to many different teams for different artifact repositories, which works really nicely when you have many teams requiring the same package but then have one team that is actually the developer of that package or artifact. In terms of the proxy, you can use it as a mirror proxy so that all your pulls for an image can go through JFrog Artifactory before they reach Docker or something, adding an extra layer of security in the company.

JFrog Artifactory has impacted my organization positively by helping us have a standard artifact management solution, so everybody is aligned, allowing us to use the same best practices and same documentation, making it easy to implement in many different pipelines.

Having a standard solution such as JFrog Artifactory has affected productivity and collaboration positively. Documentation is available for everybody that is using it, so my team, as clients to JFrog Artifactory, finds it easy to pull the documentation and implement it in our pipelines or for whatever needs we have related to JFrog Artifactory, which eases up collaboration by providing a single way of doing package management.

I cannot say much about how JFrog Artifactory can be improved.

I appreciate the opportunity to add more about the needed improvements, even small ones. Maybe around user experience, I think one improvement could be the UX, which shows its age, as it has not changed for a bit, but other than that, it is fine.

I do not think JFrog Artifactory needs any other improvements. I cannot think of anything else apart from the UX that I mentioned already.

I have been using JFrog Artifactory for about seven years.

JFrog Artifactory is stable.

JFrog Artifactory scales very well for large organizations and is a nice enterprise solution.

I think JFrog Artifactory's customer support is good.

I have not used a different solution before JFrog Artifactory.

I do not have much experience with pricing, setup cost, and licensing, as it was set up by a different team.

My company does not have a business relationship with this vendor other than being a customer.

I have seen a return on investment with JFrog Artifactory. It saves time by being a standard go-to product that every team uses, which avoids different paths to explore and spend time figuring out different solutions. When many teams collaborate on one solution for artifact management, it results in significant time cost savings.

I would estimate that my teams have saved around 70% of the time compared to figuring out their own solutions and using custom-built team solutions.

I do not have much experience with pricing, setup cost, and licensing, as it was set up by a different team.

I have not evaluated other options before choosing JFrog Artifactory.

My advice for others looking into using JFrog Artifactory is to give it a try. Once you set it up, it is very easy to use and teach other teams how to use it. I would rate this product an 8 overall.