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.
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.
We use the solution to compile the codes before publishing them. We utilize third-party containers and codes, downloading them to the JFrog Container Registry. Developers then access it from the JFrog Container Registry, and there's a specific job responsible for running and validating all security checks, ensuring compatibility. If there are any issues or if packages require updates, we manage those updates through this system.
The product offers a centralized repository.
JFrog Container Registry's most valuable feature is code scanning.
One challenge we face is related to performance. Our integration involves GitHab and JFrog Container Registry, with pipelines fetching data from GitHub and JFrog Container Registry for third-party code. However, there are instances where this process can slow down the pipeline.
I have been using the product for a couple of years.
I rate the solution an eight out of ten.
I rate JFrog Container Registry's scalability an eight out of ten.
JFrog Container Registry's tech support team is responsive.
Positive
We used ProGet before JFrog Container Registry. JFrog Container Registry is much more advanced.
JFrog Container Registry's deployment was not complex.
We have seen ROI with the tool's use.
The solution is expensive.
I rate the tool an eight out of ten.
