JFrog Software Supply Chain Platform

What do you like best about the product?

JFrog Artifactory is a great tool for storing packages, keeping them organized by version, sharing them with others, and pulling them into code whenever I need them.

Artifactory’s versioning system is especially solid. I can retrieve any package the rest of my team develops at any time, and the process is straightforward. It works well across different languages, even though I mostly use it for Python packages, and it’s consistently fast and responsive.

I’ve also used JFrog Artifactory for Docker images, and it integrates smoothly with my Dockerfile.

What do you dislike about the product?

The search feature in the Dashboard is rarely useful. Even when I enter the full package name in the UI, it often doesn’t return the correct result. Sometimes I have to navigate into subfolders before the right package finally appears.

What problems is the product solving and how is that benefiting you?

JFrog mostly addresses the universal binary repository manager use case: storing, tracking, securing, and distributing software packages, container images, and dependencies. It’s easy to install; in my case, I only needed an API key and URL to set it up locally, and that’s essentially the only onboarding a new developer has to do. Overall, it’s straightforward to use and comes with very little overhead.

What do you like best about the product?

I like using JFrog for our CI/CD pipelines because it's seamlessly embedded and makes our operations much easier by hooking in very easily. The universal package management is the best part because we make use of it for multiple things like Kubernetes, Helm charts, and Docker images. The integration of our local Nexus with JFrog is seamless. I particularly like the Artifactory Query Language (AQL) for managing artifacts at scale. It allows me to query artifacts using rich custom metadata, which is great for running automated cleanup scripts. It makes those complex filters trivial, like pruning feature branch builds while preserving compliance-tagged builds. JFrog also helps with automated storage and cost optimization, especially with high-frequency CI pipelines that generate thousands of transient document images and binaries, aiding in cost optimization with precise cleanup scripts and CI/CD pipeline automation using dependency resolution and cross-repo queries. The initial setup was pretty easy, even though we faced some latency issues with global developers, but overall, JFrog has been beneficial for our operations.

What do you dislike about the product?

We experienced latency issues for our remote developers in Europe, which were initially a challenge.

What problems is the product solving and how is that benefiting you?

We use JFrog to seamlessly integrate into our CICD pipelines, making our operations easier. I find it supports universal package management, optimizes our storage costs, precisely targets cleanups, and automates pipelines using dependency resolution.

What do you like best about the product?

I use JFrog mainly for enterprise artifacts management, especially within DevOps and CICD environments. I like the straightforward representative management which makes it easier to maintain different versions of artifacts and control access across different teams. I appreciate that the integration in our pipeline supports automation, as well as artifact upload, download, and deployment processes. The driver tokens make artifact management and integration interesting. Overall, using JFrog has been a strong solution for time management and logs, especially in a DevOps setting.

What do you dislike about the product?

I find the user interface and overall user experience lacking at times, especially when I work with a large number of repositories and artifacts. Better search filtering, visibility into artifacts, and lifecycle management would make the experience even better.

What problems is the product solving and how is that benefiting you?

I use JFrog for managing enterprise artifacts in DevOps and CICD environments. It streamlines artifact upload, download, and deployment while simplifying version control and team access.

What do you like best about the product?

I have used JFROG for storing docker images and maven artifacts so instead of managing separate repositories for docker and maven, JFrog centralises I to single system and one source of truth.

What do you dislike about the product?

I find JFrog UI console is complex and navigation through deep repository settings, modifications and configuration slows down time and high memory requirements

What problems is the product solving and how is that benefiting you?

JFrog is solving maintaining multiple repository maintenance for docker images and maven artifacts and JFrog acting as single source of truth for artifacts so I can build once and deploy everywhere

What do you like best about the product?

I use JFrog Artifactory as the central place for all our build artifacts and Docker images. The universal support for basically every package type, like Docker, npm, and PyPI, is great because we're not juggling different tools for different formats. I love how it stops our artifacts from being scattered across random registries and everything is now in one versioned place, which makes tracing a broken build much easier. The way it proxies and caches our external dependencies has saved us during public registry outages, and its vulnerability scanning is a nice bonus. Xray's vulnerability and license scanning features are valuable because it runs automatically, saving us from manual audits. The setup for remote/virtual repositories effectively handles proxying and caching, preventing builds from breaking during registry hiccups. The REST API integration into our CI pipelines was smooth and hassle-free. Overall, JFrog stays out of the way, and once it's set up, I don't really think about it, which is the highest compliment I can give infrastructure.

What do you dislike about the product?

The admin and permission side can get clunky. Setting up repo permissions across multiple teams and projects took more trial and error than I expected, and the UI for that part feels a little dated compared to how polished the rest of the platform is. Storage costs also crept up faster than we anticipated once we started keeping more Docker image versions around. Adding to that, onboarding new people onto it is not super intuitive. There's a real learning curve before someone feels comfortable navigating repos and permissions on their own.

What problems is the product solving and how is that benefiting you?

JFrog stops us from having artifacts scattered across registries, centralizing everything for easy tracing of builds. It shields us from public registry outages and rate limits, saving time. The vulnerability scanning with Xray is invaluable for our AI pipelines, and its universal package support simplifies our workflows.

What do you like best about the product?

I like JFrog for its seamless integration with CI/CD tools and the central management it offers for artifacts. The support for multiple package formats is valuable because it lets us handle all our dependencies and artifacts in one place, reducing tool sprawl and making our builds and deployments more consistent and efficient. Additionally, the performance is reliable, and the user interface is intuitive, making version control and dependency management straightforward. This platform helps to simplify the software release processes while improving team productivity by streamlining CI/CD pipelines, reducing deployment issues, and enhancing security through artifact scanning and access control.

What do you dislike about the product?

I find the user interface complex as a new user, and the initial setup and configuration take time for me. Performance can slow down when I'm managing very large repositories, and I feel the licensing cost might be high for smaller teams like mine.

What problems is the product solving and how is that benefiting you?

I use JFrog to centralize artifact management, streamline CI/CD pipelines, reduce deployment issues from inconsistent dependencies, and improve release reliability. It enhances security with artifact scanning and access control, making our processes more efficient and saving time during builds and deployments.

What do you like best about the product?

Honestly, I haven't explored too much but have some basic idea. We use it mainly for the package / asset distribution. Few GitHub actions are set up to push the builds / artifacts which are later used across applications.

What do you dislike about the product?

Sorry but don't have in depth knowledge, so cannot talk about that. The UI is okiesh, I think the authentication workflow could be improved. I see within few minutes my session expires and have to relogin.

What problems is the product solving and how is that benefiting you?

Asset storage, delivery (securely), regular scanning and much more.

I also like the GitHub, Attlasian integration features inhouse. Overall all good.

What do you like best about the product?

What I like most about JFrog is its centralized artifact management and its seamless integration with CI/CD pipelines. It offers a dependable way to store, manage, and distribute binaries across development teams, while also strengthening traceability and security. I also appreciate the user-friendly interface, the automation features, and the support for multiple package types, which together help streamline software delivery and improve overall development efficiency.

What do you dislike about the product?

One area where JFrog could improve is the learning curve for new users. Some advanced features and repository configurations can be complex to understand initially. Additionally, troubleshooting permission issues or repository settings can sometimes require more detailed documentation and administrative support.

What problems is the product solving and how is that benefiting you?

JFrog solves the challenge of managing and distributing software artifacts and dependencies across the development lifecycle. It provides a centralized repository that helps ensure build consistency, version control, and traceability. For our team, this has streamlined CI/CD processes, reduced dependency-related issues, improved release reliability, and made it easier to manage and secure software packages across multiple projects and environments.

What do you like best about the product?

I like the universal package management feature of JFrog, as it really makes life easier for us. We were pushing Docker images, Helm charts, Maven artifacts, and packages, and having a centralized system saves us a lot of time and configuration overhead. Furthermore, the initial setup was pretty easy, thanks to the help from the professional services and onboarding teams.

What do you dislike about the product?

I think there is room for improvement in the areas of permission and onboarding. The permission targets and the role-based access control models are powerful but can be overly complex sometimes, making managing permissions a bit complicated. The UI responsiveness could also be better. Additionally, I find the pricing for smaller teams to be an issue. The cost difference between basic usage and enterprise functionality is hard to justify, particularly for smaller teams, and I think this could be looked into by the CFO.

What problems is the product solving and how is that benefiting you?

I rely on JFrog for universal package management. It centralizes docker images, home charts, and Maven artifacts into a single source, eliminating manual tasks and multiple registry tools, saving a lot of configuration overhead and simplifying our work.

What do you like best about the product?

The best thing about JFrog is how accessible it makes artifacts. They’re arranged so everything is easy to find and not scattered across projects. It also has many features that enable you to audit supply chain risk, with Xray being the best of them.

What do you dislike about the product?

From the perspective of people who have a hard time using JFrog, I’d say that finding different artifacts can be confusing. Sometimes the artifact is there, but we still have to go to different places to locate it.

What problems is the product solving and how is that benefiting you?

It helps us solve the problem of removing vulnerabilities from the artifacts our organization uses. We decided that we won’t use any artifact with critical vulnerabilities, and JFrog Xray reports help us achieve that.