We push our images and Helm charts to the JFrog Container Registry. Since we have a Kubernetes-based environment, these images and Helm charts are pulled from the Kubernetes cluster and deployed.
The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
We push our images and Helm charts to the JFrog Container Registry. Since we have a Kubernetes-based environment, these images and Helm charts are pulled from the Kubernetes cluster and deployed.
We have integrated JFrog Xray, and we use it for storage purposes.
The solution's documentation available over the internet is not straightforward and customer-friendly. The documentation is mostly for the on-prem services, and there's no documentation for the cloud offering, which could be improved. The pricing is not readily explained over the internet, and I had to manually check a lot of forums to get an insight into how we are getting charged.
We were on a pro plan, and JFrog could have suggested optimization or plan upgrades based on our utilization. That didn't happen unless we manually looked into it, and now we are considering moving away from this platform.
The solution's storage costs are getting too high. Last month, we were charged around two and a half terabytes, which is a lot of data. We are considering moving towards a cost-effective platform.
I have been using JFrog Container Registry for one and a half years.
JFrog Container Registry is a stable solution.
I rate the solution an eight out of ten for stability.
We are a team of 35 developers using the tool in our organization.
I rate the solution’s scalability an eight out of ten.
The technical support’s response time could be improved.
Neutral
Since one of our team members had prior knowledge of it, the initial setup of the solution wasn't difficult for us.
The solution’s deployment took around a week.
JFrog Container Registry is a very expensive solution.
On a scale from one to ten, where one is expensive and ten is cheap, I rate the solution’s pricing a two out of ten.
We are using the cloud-based version of JFrog Container Registry. I would not recommend the solution to other organizations.
Overall, I rate the solution a six out of ten.
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.
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.
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.
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.
We've been using it in my organization for about two and a half years now.
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.
Based on my observations across multiple projects, I'd estimate that around 50-70% of our teams use JFrog in some capacity.
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.
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.
It offers valuable features and is worth the money.
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.
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.
