What I like best about JFrog is how it simplifies the entire artifact management process in one place. Managing dependencies, builds, and releases becomes much more organized and reliable, especially when working across multiple environments and teams. It reduces a lot of manual effort and helps keep deployments consistent. Review collected by and hosted on G2.com.

One challenge with JFrog is managing repository storage as artifacts grow over time. However, implementing automated cleanup policies and regular monitoring helps keep repositories organized, optimize storage usage, and maintain smooth CI/CD performance. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

We experienced latency issues for our remote developers in Europe, which were initially a challenge. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

The thing that I appreciate most about JFrog is its efficiency in managing artifacts, distributing software, scanning for security vulnerabilities, and handling DevOps practices in one single platform without adding any extra operational complexity.

In rapidly scaling engineering setups, where there is constant creation, deployment, and management of cloud-based applications from multiple engineering teams, having control over software packages, their dependencies, and the release pipelines has been a challenge. JFrog has been immensely useful for streamlining and improving the entire software delivery lifecycle.

The ability to manage artifacts and packages via JFrog Artifactory stands out as one of the main advantages for me.

Performance and scalability have also been strong in my experience, particularly when handling large-scale artifact storage, container registries, and high-frequency deployment pipelines. Review collected by and hosted on G2.com.

Dislikes about JFrog include its complexity to be configured and managed in large environments with customized CI/CD workflows. In other words, while the platform is indeed very useful and powerful in enterprise DevOps and artifact management use cases, at times it could be somewhat complicated to set up.

One particular difficulty I've encountered is the necessity to understand various aspects of repository management, including permission handling, pipeline integration, and software supply chains. It becomes somewhat burdensome to onboard engineers into using the platform if there are not so many of them or their background is somewhat simple.

In terms of usability and user experience, one might say that the platform is very efficient and offers lots of opportunities but some administrative functions may come as challenging. Namely, working with multiple repositories, access controls, and distributed environments at once can require certain skills and experience.

Finally, I would mention some of the difficulties I had with some of the integrations and automation processes. While JFrog works excellently within different CI/CD ecosystems in general, it might take some effort to make the most out of advanced workflow configurations and automations. Review collected by and hosted on G2.com.

What I like best about JFrog is its support for multiple package types and its centralised artifact management. It makes it easy to store, organise, and share artifacts across different projects from a single platform. The built-in security scanning is also very useful, as it helps detect vulnerabilities early. Overall, JFrog simplifies the software delivery process and integrates well with modern CI/CD pipelines. Review collected by and hosted on G2.com.

One downside of JFrog is that it has a steep learning curve, especially for new users. Setting up repositories, permissions, and integrations can take some time if you're not familiar with the platform. It can also feel overwhelming due to the number of features available, and troubleshooting configuration issues isn't always straightforward. However, once everything is set up, it becomes much easier to manage. Review collected by and hosted on G2.com.