JFrog Reviews & Product Details

What I like best about JFrog is its comprehensive approach to managing the entire software supply chain. Artifactory acts as a single source of truth for binaries across virtually every package manager and language, which eliminates silos. On top of that, its seamless integration with CI/CD pipelines, robust enterprise scalability, and embedded security scanning with JFrog Xray make managing software artifacts both secure and effortless. Review collected by and hosted on G2.com.

While JFrog is an industry standard for artifact management, the main challenge is its cost and licensing complexity, especially as storage and user seats scale up for enterprise tiers. Additionally, the learning curve and admin overhead for managing fine-grained permissions, repository replication, and self-hosted instances can be steep for smaller teams that might prefer a lighter, plug-and-play solution. Review collected by and hosted on G2.com.

I use JFrog as a universal repository manager and love the best feature: the universal package support. It solves the issue of running separate registries for each technology, supporting over 30 packages so each team can use the same platform. JFrog really ensures my deployments are fast, secure, and reproducible. The initial setup was very easy and quick. Review collected by and hosted on G2.com.

I have some concerns about JFrog's pricing. It's notoriously expensive, particularly for small-to-medium businesses, startups, or individual developers. The tier-based pricing structure often locks crucial features, like advanced security scanning, behind high-tier enterprise licenses. This makes alternatives like Nexus Repository Manager or cloud-native registries more financially appealing for smaller teams. Review collected by and hosted on G2.com.

I find JFrog Artifactory absolutely reliable with its pristine uptime, which is crucial for maintaining our data pipelines. I love how it automates handoff security and ensures our environment remains consistent, removing the need for manual checks. The way it caches our external Python packages is a lifesaver, ensuring our scheduled data pipelines never fail due to public repo outages or deleted internet packages. It also automates compliance processes, so I don't have to manually verify if an open source data connector is secure or carries a risky license. Review collected by and hosted on G2.com.

The UI/UX of JFrog feels clunky and dated, with a highly enterprise-focused design. Setting up fine-grained access, repository chains, and retention policies requires specialized skills, which can be challenging. Review collected by and hosted on G2.com.

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.

What I like most about JFrog is its strong focus on reliable software delivery and developer productivity. I especially like how JFrog connects artifact management, security, CI/CD, and DevOps workflows into a unified platform. As a backend/software engineer, I find the scale, performance, and automation challenges particularly interesting, and I’d be excited to contribute to building reliable tools that developers use throughout the software lifecycle. Review collected by and hosted on G2.com.

One thing I would improve is the learning curve for new users. With a broad platform covering artifact management, security, and DevOps workflows, some areas can initially feel complex. I think more streamlined onboarding and documentation could make it easier for new users to get value quickly. Overall, I see this more as an opportunity for improvement than a major weakness. 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.