Integrated pipelines have improved enterprise deployments and now automate secure dependency flows
What is our primary use case?
My main use case for JFrog Artifactory involves integrations such as Amazon RDS, Amazon EBS, and CloudWatch, which generally help me improve our processes. It is a standard artifactory that helps me scale enterprise workloads, especially when building high-volume pipelines or managing multiple projects to ensure reliability. Additionally, DevSecOps automation is where JFrog Artifactory comes into play.
A specific example of how I use JFrog Artifactory in one of my projects involved a project where we had several artifacts on our AWS S3 buckets and a hard dependency on AWS's security competency. JFrog Artifactory helped us achieve that because it has DevSecOps automation capabilities that assist in preventing modern-day supply chain hacking and cybersecurity attacks, making those integrations with AWS particularly valuable.
I do not have anything else to add about my main use case or that project without breaching confidentiality.
How has it helped my organization?
JFrog Artifactory has positively impacted my organization by initially being part of two vertical divisions and later extending to four or five verticals as positive stories were shared. Thus, it has had a good positive impact.
As for specific outcomes about the positive impact from expanding to four or five verticals, we have achieved faster deployment speeds, faster time to market, and lower pipeline failure rates. These were the key metrics monitored mostly by the DevOps and NOC teams, while I had limited involvement with those metrics.
What is most valuable?
The best features JFrog Artifactory offers include automating dependency management, which reduces the risks of failing builds and broken builds, making the CD pipelines much smoother when I use JFrog Artifactory with AWS CodeBuild or EKS-based CI runners. I really appreciate the security competency aspects because it helps me ensure that JFrog Artifactory meets the requirements for the supply chain, and I find both of these features very useful.
What needs improvement?
Regarding improvements for JFrog Artifactory, I remember that the documentation was more focused on the on-premises JFrog version. I was mostly redirected toward that, so I found a lack of specific or clear documentation on using JFrog Artifactory with AWS. I felt this gap two years ago, and there were capabilities such as X-ray or integrations with other AWS features that I found lacking at the time.
I do not have much more to say about the needed improvements in integration or documentation, but I want to mention that, coming from a quality background, I think built-in quality gates for intelligent automation, vulnerability checks, or improved visibility and communication during slow responses or service downtime would be useful for visibility in distributed environments.
Looking back, I think the learning curve for JFrog Artifactory could be eased, and the installation process could feel less overwhelming. While it is not that difficult, I have seen new joiners struggle with the initial setup.
I think JFrog Artifactory could improve with some UX revamps since many tools these days provide very intuitive user experiences, and I believe that could be something to look into for the future.
For how long have I used the solution?
I have used JFrog Artifactory across multiple jobs, so my total experience would be more than three years.
What do I think about the stability of the solution?
In my experience, JFrog Artifactory is quite stable.
What do I think about the scalability of the solution?
The scalability of JFrog Artifactory was decent for our organization of 2,500 people, as we used it across three or four verticals, but my exposure to scalability was limited due to my QA background.
Which solution did I use previously and why did I switch?
I do not recall using a different solution before JFrog Artifactory. It was JFrog on-premises, and later, JFrog Artifactory on AWS, which is all my organization has used.
Which other solutions did I evaluate?
Before choosing JFrog Artifactory, we evaluated some options such as GitLab packages, which were somewhat relevant, and I would not say they were direct alternatives. We also used a package repository called Cloudsmith and Docker Hub at different stages. While these might not be direct competitors, they were tools I have used.
What other advice do I have?
My advice for others looking into using JFrog Artifactory would be to work with someone who has previously set up and onboarded themselves on JFrog Artifactory because it might be challenging for first-timers. I would not recommend the official documentation but suggest using blogs or guides created by the community instead. For places such as banks or financial institutions, I would recommend ensuring there are more security features as security is a high focus. I would rate this product highly based on my overall experience with JFrog Artifactory.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Centralized builds have improved CI workflows and ensure consistent packages across services
What is our primary use case?
Our main use case for JFrog Artifactory is for Maven builds and Docker images as an artifactory support, so anytime someone builds an image or creates a Maven build, we upload it to JFrog Artifactory. We use it for Maven builds, Docker builds, and for our CI/CD.
How has it helped my organization?
JFrog Artifactory has positively impacted our organization by ensuring that unified package management is happening at a central place, which has been helpful for our distributed service mesh because otherwise, everyone would be rebuilding their own versions of the central package, eventually leading to problems. Unified management is welcoming.
Better consistency across services is perhaps the bigger point we have seen as an outcome. Once a new service goes in or a new build for any existing service goes in, we are at least certain that it is picking up the latest code that we had pushed to the central package, ensuring that if an observability fix or security fix went in, we just need to ensure a rebuild happened on all services after that build and it is now reflecting.
What is most valuable?
The best features JFrog Artifactory offers are a unified store for our builds, Docker, and everything, and its integration into CI/CD, which is quite smooth for us as we are using it across several different repositories and two different package types including Go and Java Spring Boot.
The integration of JFrog Artifactory into our CI/CD has been smooth because the documentation was pretty clear on how we had to do it. We did not have any issues since, and I was well aware of when it was happening, so the part that stood out was the clear documentation that I think was available online.
What needs improvement?
JFrog Artifactory could be improved for simpler workflows without dedicated infra teams or dedicated DevOps, as it could be difficult to configure. For us, it was slightly easier because we have a lot of senior engineers and people with CI/CD experience, but it could be slightly problematic in those cases.
For how long have I used the solution?
I have been using JFrog Artifactory for about three months since we configured it.
What do I think about the stability of the solution?
JFrog Artifactory has been stable for us.
What do I think about the scalability of the solution?
JFrog Artifactory's scalability has been good as we have 14 to 15 services today, and it will increase to maybe 30 over the next few months. We have not had any issues so far.
How are customer service and support?
I have not interacted with customer support yet.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We did not previously use a different solution because we started with JFrog Artifactory itself.
How was the initial setup?
JFrog Artifactory is deployed in our organization on our VPN right now, so it is on the private cloud. We purchased JFrog Artifactory through the AWS Marketplace.
What about the implementation team?
I was not involved in the licensing and pricing part, but the setup cost was I think one or two days, so whatever engineers were required, it was about the specific pay for those two days.
What was our ROI?
The return on investment has been more on productivity, although we have not quantified it, so there are no metrics to share.
What's my experience with pricing, setup cost, and licensing?
I was not involved in the licensing and pricing part, but the setup cost was I think one or two days, so whatever engineers were required, it was about the specific pay for those two days.
Which other solutions did I evaluate?
Before choosing JFrog Artifactory, we evaluated Nexus and JFrog, but we realized JFrog Artifactory is slightly better because Nexus does not provide that smoother experience for CI/CD and for Java Maven builds, so that is why we went ahead with JFrog Artifactory.
What other advice do I have?
If you have some Maven builds or Gradle builds and Docker repositories that you want to store at a central place, JFrog Artifactory can be a solution one can look into. It should be one of those options that you evaluate. I give this review an overall rating of 9.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Global teams have managed artifacts efficiently and reduce latency in daily CI CD workflows
What is our primary use case?
I have been using JFrog Artifactory for the past three years. We primarily use JFrog Artifactory for storing our Docker images, packages, artifacts, and other files that we use in our applications on a day-to-day basis.
In a CI/CD pipeline, there are several workflows and steps where you bundle your code as an image or as an artifact so that you can use it for running the image in containers using Kubernetes. In those stages of the CI/CD pipeline, we generally build the image using Docker. After building the image, we need to store it for future usage. For storing the images that we build using those CI/CD pipelines, we use JFrog Artifactory in our current environment.
What is most valuable?
One of the greatest features JFrog Artifactory can offer is RTFS, which stands for Real-time Federation Service. If we have two Artifactorys in two different regions, RTFS is the feature of JFrog Artifactory that can help us in federating those two repositories in real time. It is definitely helpful and it reduces the latency, and it is a brilliant feature that I love.
We have teams working across the globe. For that reason, if we have JFrog Artifactory in a single region, the people who are working far away from that region will definitely face latency. For that reason, we have deployed JFrog Artifactory in two different regions so that our users can access it without any latency. If we have two Artifactorys in two different regions, there will be a gap in data or a data mismatch between two JFrog Artifactorys. What the RTFS feature does in JFrog Artifactory is that it federates and syncs all the data from one repository to the other repository and vice versa. It always maintains the same data in both repositories and in both JFrog Artifactorys. This feature helps us in syncing these two repositories all the time without any manual effort, and it happens in real time within seconds.
There are many features such as user management, administration, and service management and different types of features, but this one is the most standout feature.
What needs improvement?
The most significant thing that I can express is that upgrading JFrog Artifactory to the new version is a bit cumbersome and it is a tedious process. If that could be addressed, then everything would be very smooth and very useful. There are no other challenges except this.
For how long have I used the solution?
I have been working in this same field for the past three years.
What do I think about the stability of the solution?
JFrog Artifactory is pretty stable.
What do I think about the scalability of the solution?
It is very scalable. I would rate it a ten out of ten.
How are customer service and support?
Customer support is brilliant.
How would you rate customer service and support?
What was our ROI?
I can share that JFrog Artifactory definitely has a very good return on investment and it has saved a lot of time, money, and manpower, though I cannot share the specific numbers.
What's my experience with pricing, setup cost, and licensing?
The pricing is very competitive and fits well within our budget.
What other advice do I have?
JFrog Artifactory has definitely impacted our organization in a positive manner. Approximately 20,000 people or 20,000 pipelines use JFrog Artifactory on a day-to-day basis. If we had any other tool instead of JFrog Artifactory, it would definitely not work as effectively as JFrog Artifactory.
Most of the time JFrog Artifactory saves time because it is very fast. The tools, the services, and the features it has are really brilliant and no other tool can match it. If you are a large organization with multiple JFrog Artifactorys in multiple regions, JFrog Artifactory with RTFS is a brilliant tool. I would rate this review a ten out of ten.
High scalability for enterprise environments
What do you like best about the product?
JFrog scales efficiently to accommodate large teams, high build volumes, and multiple projects, making it suitable for organizations of all sizes.
What do you dislike about the product?
High resource consumption on self-hosted deployments.On-premises installations require significant server resources and storage, which is costly and difficult to maintain for us.
What problems is the product solving and how is that benefiting you?
JFrog automatically manages dependencies between packages, reducing the need for manual intervention. This speeds up build processes, ensures accurate compilation, and decreases the risk of broken builds.
Great environment for Networking and Knowledge Sharing
What do you like best about the product?
The event was organised by so nicely, that I would love to come back again.
What do you dislike about the product?
Nothing much really. In fact it was great.
What problems is the product solving and how is that benefiting you?
Repository Management, SCA, DevOps
One of the best tool helping us in ML model deployment
What do you like best about the product?
JFrog is one of the best tool we have come across for ML model build and deployment from end to end. It also provides central model repository to store artifacts and all other related data. It is very easy to implement and very easy to use.
What do you dislike about the product?
JFrog has all the required features for ML model build and deployment so I don't think it has any dislike from my end.
What problems is the product solving and how is that benefiting you?
Our problem is to have a tool which will provide antifactory repo also it should helps us end to end while ML model build and deployment. JFrog helped us to solve this issue.
Comprehensive artifact management for DevOps pipelines
What do you like best about the product?
JFrog provides a centralized platform to manage artifacts efficiently, ensuring that software components are stored, tracked, and shared securely across development and production environments.
What do you dislike about the product?
The platform’s advanced artifact management and DevOps integrations can be overwhelming. New users often require extensive training to fully utilize all functionalities effectively.
What problems is the product solving and how is that benefiting you?
JFrog provides a single platform to store, track, and manage all software artifacts. This solves the problem of scattered binaries, reduces version conflicts, and ensures that development, testing, and production environments use consistent components.
Overhyped, barely bets the job done.
What do you like best about the product?
It does what it claims to ie managing artifacts and repos. Have support of wide range of packages.
What do you dislike about the product?
The interface is very cluttering, have way too many features which creates a mess and complicate things
What problems is the product solving and how is that benefiting you?
It was suppose to help us unify our entire system like repos and microservices.
Supports a wide variety of packages with robust security features but needs tighter cloud integration
What is our primary use case?
JFrog Artifactory is designed for software management. We used it for storing all assets and packages that were downloaded from external package systems, making them available for our development teams to use in their builds.
It primarily supported a fail-fast approach, where vulnerabilities were identified ahead of time, enabling us to alert our development team to use the latest packages without those vulnerabilities.
JFrog Artifactory proved very helpful in supporting a variety of package types for different projects.
What is most valuable?
The best features of JFrog Artifactory include the core functionality of package management and software management, along with scanning capabilities to prevent vulnerabilities from being introduced.
The metadata management feature was particularly useful for managing packages within JFrog Artifactory.
We utilized Xray integration with JFrog Artifactory, which was instrumental in managing vulnerabilities overall.
JFrog Artifactory has robust functionality in terms of access control, which helped us ensure minimal access to various artifacts.
I would rate it eight out of ten because it is a great product that is widely used in the industry. It has excellent features from an artifact management perspective and maintains good integrations.
What needs improvement?
JFrog could improve this product with tighter integration capabilities.
For how long have I used the solution?
I used JFrog Artifactory in the last twelve months.
How are customer service and support?
I would rate their support for JFrog Artifactory as seven out of ten.
How would you rate customer service and support?
What other advice do I have?
I am no longer using JFrog Artifactory in my current role as I moved away from the team. The metadata management features were very useful, particularly for managing packages inside JFrog Artifactory. We were customers of JFrog. Based on my experience, I would rate JFrog Artifactory eight out of ten.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Perplexing Engineering
What do you like best about the product?
1. The unification of all the requirements for a DevOps team
2. Ability to support various out-of-the-box registry support
What do you dislike about the product?
1. It is difficult to get started and understand how to use CLI from your local environment to the cloud
2. Cloud Pro account requires business email but logging in from Github works with personal account (perplexing access policies)
3. JFrog CLI is separately downloadable and configurable, the use of which remains a big mystery since we can use cURL to do pretty much everything in Artifacts (again perplexing strategy)
4. Setting multiple Repositories is required for simple task of pulling packages from public registries
What problems is the product solving and how is that benefiting you?
Caching the public registries for speeding up the SDLC
