Efficient, Scalable Artifact Management That Streamlines the Software Delivery Lifecycle
What do you like best about the product?
The thing that I appreciate most about JFrog is its efficiency in managing artifacts, distributing software, scanning for security vulnerabilities, and handling DevOps practices in one single platform without adding any extra operational complexity.
In rapidly scaling engineering setups, where there is constant creation, deployment, and management of cloud-based applications from multiple engineering teams, having control over software packages, their dependencies, and the release pipelines has been a challenge. JFrog has been immensely useful for streamlining and improving the entire software delivery lifecycle.
The ability to manage artifacts and packages via JFrog Artifactory stands out as one of the main advantages for me.
Performance and scalability have also been strong in my experience, particularly when handling large-scale artifact storage, container registries, and high-frequency deployment pipelines.
What do you dislike about the product?
Dislikes about JFrog include its complexity to be configured and managed in large environments with customized CI/CD workflows. In other words, while the platform is indeed very useful and powerful in enterprise DevOps and artifact management use cases, at times it could be somewhat complicated to set up.
One particular difficulty I've encountered is the necessity to understand various aspects of repository management, including permission handling, pipeline integration, and software supply chains. It becomes somewhat burdensome to onboard engineers into using the platform if there are not so many of them or their background is somewhat simple.
In terms of usability and user experience, one might say that the platform is very efficient and offers lots of opportunities but some administrative functions may come as challenging. Namely, working with multiple repositories, access controls, and distributed environments at once can require certain skills and experience.
Finally, I would mention some of the difficulties I had with some of the integrations and automation processes. While JFrog works excellently within different CI/CD ecosystems in general, it might take some effort to make the most out of advanced workflow configurations and automations.
What problems is the product solving and how is that benefiting you?
In the past, our development process had an inefficient workflow of artifact storage, dependency management, and CI/CD pipeline. As applications were delivered on cloud, microservice, container, and cross-team levels, it was very hard to maintain transparency and governance of software packages and releases.
The biggest advantage I found with JFrog is its ability to manage artifacts and packages through JFrog Artifactory. Previously, we had to manage different repositories and track dependencies manually, but now it’s way more organized. It's pricing is also balanced.
JFrog Centralized Our Artifacts and Streamlined CI/CD
What do you like best about the product?
JFrog work well for me.Mainly because I noticed a lot of improvement in our build and deployment process due to the centralization of all resources. We had different artifacts and different version numbers of packages before, which created confusion regarding which build to use. In JFrog, I was able to upload all artifacts in a single place and link them to my CI/CD processes. Also, the repositories used here included build packages as well as container images, and I found it very easy to troubleshoot any issues with the deployed build by referring to the version history.
What do you dislike about the product?
The first configuration was a lot harder for me to configure than anticipated. I still vividly recall spending hours comprehending the organizational structure of repositories, permissions, and the classification of various packages. As soon as I began to have many repositories, it took consistent effort on my part to maintain their organization or else they would easily get disorganized. I further realized that there were portions of the interface that were not as user-friendly as I would expect them to be, such as switching from one repository to another or dealing with access problems.
What problems is the product solving and how is that benefiting you?
Prior to using JFrog, the builds and dependencies were done in an uncontrolled fashion that led to problems with consistent versions and reliable deployments. There were instances where the various environments had different packages causing the debugging process to be much more difficult than it ought to have been. The use of JFrog for artifact management made it easy to keep track of the deployed version as well as its origin point. This made it possible to avoid deployment errors that could have easily occurred otherwise.
Artifact management has simplified CI/CD pipelines and continuously improves security insights
What is our primary use case?
Currently, we are using
JFrog Artifactory to store artifacts and we are using JFrog to scan those artifacts by using Xray scan.
JFrog Artifactory allows you to create many repositories. Currently, I'm using Docker, so it is very easy for me to create repositories in Docker and we can push Docker artifacts to that repository and pull and use them. It's very straightforward.
Currently, we have many different repositories created in JFrog Artifactory. We use them for versions. We can create multiple repositories and store artifacts in different packages.
I haven't experienced any downtime for JFrog Artifactory because we are currently operating at a small scale with small units stored in JFrog Artifactory, not a large volume. This is why we haven't faced any issues yet.
Currently, I'm using Docker and Kubernetes for JFrog Artifactory. My Docker creates images and pushes them to JFrog Artifactory, which stores my artifacts and images. When it comes to pulling, my Helm chart retrieves those artifacts and deploys my newer version if I change anything. It's a full CI/CD process that I'm using currently.
What is most valuable?
JFrog Artifactory gives us metadata and policies. We can use those policies in our scripts to pull images and artifacts from JFrog Artifactory repositories for use in our deployment process.
Whenever we push artifacts to JFrog Artifactory repository, they are automatically scanned. We just need to enable that feature and it will provide vulnerability scan reports.
JFrog Artifactory provides metadata. Whenever we access the UI and open those artifacts, it gives you information about which version is present. You can also tag those versions in your script file and we can automate that dynamically to create those tags in the script.
JFrog Artifactory also provides authentication features. If we are using JFrog with an enterprise grid, we can invite users who can access the same repository. We can add those users so they can access and view the repository. We can also share repositories with others and generate authentication tokens there. It provides encrypted tokens.
What needs improvement?
Even when creating any application, there are parts we need to focus on. Currently, JFrog Artifactory doesn't have AI features, which is an area they could update in the future.
For how long have I used the solution?
I have been working with JFrog Artifactory for almost two years.
How are customer service and support?
I haven't used any technical support yet. However, when my organization purchased the enterprise grid, they handled some vendor-related activities.
Which solution did I use previously and why did I switch?
When we started using JFrog Artifactory, it provided a 14-day trial feature. We could try JFrog Artifactory and check whether it would be suitable for our organization and test those features. It also provided a server for the 14-day trial. When it came to the enterprise grade, we were previously using Nexus and we migrated from Nexus to JFrog Artifactory because JFrog Artifactory offers more features than Nexus.
The offerings are almost the same in both JFrog Artifactory and Nexus in some aspects. I cannot define those differences precisely right now, but there are some distinctions. Vulnerability scanning is one feature where they differ, and there are some other differences as well.
How was the initial setup?
I think the setup process in JFrog Artifactory is pretty simple and straightforward. If we know what we want to implement, we can configure those things there. Even if we are using JFrog CLI, we can use some commands and it will create things for you. That is pretty simple.
Which other solutions did I evaluate?
Nexus is an alternative solution to JFrog Artifactory.
What other advice do I have?
I think JFrog Artifactory is good whether we use it for small scale or large scale operations. It provides features that allow you to store artifacts and have vulnerability scanning for your artifacts, which is a good feature. I would rate JFrog Artifactory as an eight because I have invested significant time in it and have accomplished many things with it.
Reliable for deployments but it has a learning curve
What do you like best about the product?
I love how JFrog keeps software versions consistent across multiple machines, which is crucial for my work. It helps reduce errors during installs and upgrades, saving me a lot of time. Additionally, the fact that JFrog works very well with automation allows me to automate processes and focus on other tasks simultaneously.
What do you dislike about the product?
To be honest it is not beginner friendly. I think you must provide free training for the beginners. Lol it was not easy but through research and help from my team I managed.
What problems is the product solving and how is that benefiting you?
I use JFrog to keep software versions consistent across machines, reducing errors during installs and upgrades. It saves me a lot of time by automating tasks, allowing me to focus on other things.
Powerful Central Artifact Repository, but Feels Heavy for Simple Hosting Needs
What do you like best about the product?
I think it provides a bery good central repository to store libraries and artifacts, that can be shared across the organization
What do you dislike about the product?
Nothing specific. But It can feel heavy and “enterprise”y. Artifactory is powerful, but that usually comes with more operational complexity, more knobs, and more moving pieces than teams actually need if all they want is “host Maven/npm/Docker reliably.”
What problems is the product solving and how is that benefiting you?
It also has good enterprise plumbing. The repository model of local, remote, and virtual repos is useful in practice, and replication support helps when you need caching, regional distribution, or controlled synchronization across sites.
A comprehensive solution for package management and software security
What do you like best about the product?
I love JFrog's support for all types of packages, as it acts like a 'joker' and supports more than 30 types of technologies in one place. I am impressed by the proactive security provided by JFrog Xray, which automatically and continuously scans for vulnerabilities, alerting us immediately if a new vulnerability appears. I also appreciate the version and metadata management, where JFrog maintains a complete identity for each file, greatly facilitating error tracking. Additionally, I like the lifecycle automation tool that ensures what has been tested is what will be deployed to the public, along with the very seamless cloud setup that eliminates concerns about infrastructure, and the interface that helps in quickly creating the first repository.
What do you dislike about the product?
The learning curve due to the vastness of the platform and its numerous features causes new users to struggle initially. The problem: The user interface (UI) is filled with complex options and settings.
What problems is the product solving and how is that benefiting you?
I use JFrog to accelerate downloads and support continuity by storing libraries locally and enhancing security by scanning for vulnerabilities and licenses. JFrog helps reduce technical debt with a unified interface and increases confidence with version tracking and automation capabilities.
Efficient Monitoring with Seamless Cloud Integrations
What do you like best about the product?
I use JFrog for learning more about the services and product offered, as well as Cloud deployments with features like end-to-end visibility. I like the features, especially the ones doing the heavy lifting of the work, including monitoring and flows. Also, I like the integrations available like ServiceNow and Sonar for code quality. The initial setup of JFrog was quite easy.
What do you dislike about the product?
I would like to see more integrations where things can be out of the box
What problems is the product solving and how is that benefiting you?
JFrog helps with monitoring and logging, offering features that do the heavy lifting and provide integrations like ServiceNow and Sonar for code quality.
Centralized Management with User-Friendly Interface
What do you like best about the product?
I really like how easy to use JFrog is and its user-friendly UI. It helps me navigate dependencies easily and search for required repositories under the central and virtual repo. The setup process was also straightforward, taking just a day to complete.
What do you dislike about the product?
API key expiring and rotating every 30 days
What problems is the product solving and how is that benefiting you?
I use JFrog for managing builds and artifacts, and it solves having a central repository across the organization. The easy-to-use UI helps me navigate dependencies and search for required repositories efficiently.
Ultimate Safety Net for Large Teams
What do you like best about the product?
I primarily use JFrog Artifactory as a centralized repository manager to handle the lifecycle of my software packages, and it effectively eliminates the friction that slows down a high-stakes development cycle. I love how it serves as the ultimate safety net and speed booster for our entire software supply chain. Thinking of JFrog as a 'safety net' and 'speed booster' isn't just marketing—it literally describes the difference between a smooth release and a weekend spent fixing a broken production environment. It's particularly beneficial when juggling the responsibilities of a Senior Full Stack Developer in a fast-paced environment. JFrog acts as the 'connective tissue' that links my code to my infrastructure, and its key integrations keep my workflow moving smoothly.
What do you dislike about the product?
While I’m a big advocate for JFrog, being a Senior Java Full Stack Developer means I also have to deal with its 'rougher' edges. No tool is perfect, especially one that tries to do as much as the JFrog platform. Based on my experience as a Senior Java Full Stack Developer, there are several technical and workflow-specific areas where I’d like to see JFrog push further. While it’s the backbone of our supply chain here in Seattle, these improvements would significantly reduce the daily 'to-do' list for a senior dev.
What problems is the product solving and how is that benefiting you?
I use JFrog Artifactory as a centralized repository manager, eliminating friction in development cycles and acting as a safety net and speed booster for our software supply chain.
JFrog Xray Stands Out Among DevOps Tools
What do you like best about the product?
JFrog Xray have not seen that in actio i nother dev ops softwares
What do you dislike about the product?
not a lot of people know about it, it should have more reach
What problems is the product solving and how is that benefiting you?
stream line ci/cd deployment and artifact management
