What is our primary use case?
JFrog Container Registry acts as a single solution for storing and managing all of our software artifacts. This includes packages, files, and containers throughout our software supply chain.
We have a central JFrog server, and we integrate various tools with it. The artifacts are stored there. It helps us manage the process from build to release.
How has it helped my organization?
There are several aspects. We use it to store container access information securely. We've also implemented authentication mechanisms like SAML, download blocking, and virtual IT consoles.
For repository optimization, we've used the file store feature within JFrog Container Registry.
The security features in JFrog Container Registry have helped protect the integrity of the Docker images.
What is most valuable?
From my perspective, it allows us to integrate our development and operations workflows seamlessly. It's self-hosted and works well in hybrid SaaS environments. Plus, it supports multi-cloud deployments across AWS, Azure, and GCP.
What needs improvement?
In my experience, there was a bit of a learning curve at the beginning. It can be somewhat challenging to install and get started. However, once you gain some experience, working with JFrog becomes much easier.
Overall, it's manageable for beginners, but there might be a bit of a learning curve. I'd call myself an intermediate user.
For how long have I used the solution?
We've been using it in my organization for about two and a half years now.
What do I think about the stability of the solution?
From my experience, it's stable. I've used it heavily for CI/CD workflows, and the automation is fast without any breakdowns. We've even integrated it with IoT device management.
What do I think about the scalability of the solution?
Based on my observations across multiple projects, I'd estimate that around 50-70% of our teams use JFrog in some capacity.
Which solution did I use previously and why did I switch?
The companies I've worked with, like Walmart and others, already had JFrog deployed when I joined. Often, with larger companies, it's not feasible to switch major tools once they're in place.
How was the initial setup?
As a DevOps engineer, I found the initial setup straightforward to install and use. I've even set up and managed JFrog Artifactory instances from scratch earlier in my career. I know JFrog well from the artifact storage perspective.
Assuming everything is set up correctly, it should take about half an hour – maybe 15 to 30 minutes.
It's cloud-based. We use AWS.
What was our ROI?
It offers valuable features and is worth the money.
What's my experience with pricing, setup cost, and licensing?
The pricing is somewhat expensive compared to its competitors.
We use the Pro version because we have a data consumption of 6GB in our organization. We considered the Enterprise plan as well, which is around $750, but we're still evaluating that option. For now, we're sticking with the base Pro package.
What other advice do I have?
I'd definitely recommend it. It's a good choice for those starting out, especially if you're focused on container-based workflows. It's easy to understand and deploy, and you can even use the JFrog interface directly. There might be even better options depending on your specific needs.
Overall, I would rate the solution an eight out of ten.
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)
Disclosure: I am a real user, and this review is based on my own experience and opinions.