I like JFrog for its ability to centralize artifact management and integrate seamlessly with CI/CD workflows. The artifact traceability is extremely valuable because it helps us quickly identify which build version was deployed, reducing troubleshooting time during incidents. JFrog is reliable, scalable, and makes release management more organized across multiple environments. The platform improves deployment reliability and version consistency, and it is a valuable solution for teams managing modern DevOps workflows. Review collected by and hosted on G2.com.

One area that could be improved is the learning curve for new users. Some administrative configurations and advanced repository management features can be complex to understand initially. Additionally, troubleshooting permission-related issues sometimes requires deeper knowledge of the platform. More guided documentation and simplified onboarding for new users would make adoption easier. Review collected by and hosted on G2.com.

I like how JFrog keeps all of our build artifacts organized in one place and integrates smoothly with our CI/CD pipeline. It makes our releases more reliable and much easier to manage. Review collected by and hosted on G2.com.

The interface can feel a bit overwhelming at first, and some of the more advanced features come with a learning curve—especially when you’re setting up repositories and configuring permissions. Review collected by and hosted on G2.com.

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

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

What I like most about JFrog is how reliable it is and how smoothly it handles artifact management. It keeps dependency management and our CI/CD pipelines more stable and predictable, which makes day-to-day work easier. Review collected by and hosted on G2.com.

One thing I dislike is that JFrog can feel a bit complex when you’re first setting it up and configuring it. It offers a lot of features, but it can take some time to fully understand how they work and to optimize your configuration. Review collected by and hosted on G2.com.

What I find most helpful about JFrog is that it gives teams a single place to manage software artifacts and dependencies across the entire delivery pipeline. That centralization makes builds, releases, and deployments faster and easier to trace. JFrog Artifactory stands out in particular because it supports many package formats and fits naturally at the center of DevOps workflows. Review collected by and hosted on G2.com.

Pricing, configuration complexity in large environments, and support quality are the main concerns. It can feel heavy when it needs to fit into highly customized CI/CD workflows, and enterprise support may be costly or harder to access. Review collected by and hosted on G2.com.

Its ability to serve as a truly universal repository is unmatched. Instead of juggling separate tools for Docker, npm, and Maven, our team can centralize everything under one roof. The native integration with major CI/CD pipelines makes managing dependencies incredibly smooth." Review collected by and hosted on G2.com.

The internal search and navigation can occasionally be the least helpful part of the experience. When managing thousands of components, finding a highly specific package version or sorting through deeply nested repository structures feels cumbersome without advanced query knowledge. Review collected by and hosted on G2.com.

What I like best about JFrog is its focus on making software delivery faster, secure, and reliable. It aligns with my interests in backend, cloud, AWS, and DevOps, and I would love to contribute to such a product. Review collected by and hosted on G2.com.

Honestly, I don't have any major dislikes. Every product has challenges, but I see them as opportunities to learn and contribute rather than drawbacks. Review collected by and hosted on G2.com.

ne of the standout aspects of JFrog is its exceptional Performance and stability; artifact resolution and repository replication remain lightning-fast even under heavy enterprise loads. Its Integrations with our existing tech stack—including major CI/CD tools like Jenkins and GitHub Actions—worked flawlessly out of the box, making pipeline automation incredibly smooth. From a UI/UX perspective, the platform is clean and highly intuitive, enabling our team to manage complex build artifacts without getting bogged down in messy configurations.

The Support and Onboarding process was remarkably straightforward, backed by comprehensive documentation and a highly responsive technical support team that accelerated our adoption. While the Pricing represents a significant investment, the ROI is undeniable through saved developer hours and drastically reduced downtime. Additionally, their growing AI and Intelligence features add a layer of proactive security and smart dependency scanning that gives us immense confidence in our software supply chain. Review collected by and hosted on G2.com.

While the platform is powerful, the UI/UX has a steep learning curve, making navigation overwhelming for new users during Support and Onboarding. Complex Integrations with our CI/CD stack occasionally require significant manual scripting, which impacts overall setup Performance. Additionally, the premium Pricing makes it difficult to see a high ROI for smaller teams who don't utilize all enterprise features. Finally, the newer AI and Intelligence capabilities still feel rudimentary and could be expanded to provide deeper predictive cost analytics or automated troubleshooting tips. Review collected by and hosted on G2.com.

JFrog is really useful when you need a centralized place to manage build artifacts, Docker images, packages and dependencies across teams. Security scanning and supply chain visibility are nice additions, especially with modern DevSecOps expectations. Review collected by and hosted on G2.com.

The UI feels capable but not always intuitive. Finding specific settings or admin configurations sometimes takes more clicks than it should.

Initial setup can also be heavier than expected if you’re not already familiar with artifact repository concepts. Storage management and cleanup policies need planning too, otherwise things can grow messy fast. Review collected by and hosted on G2.com.

I find JFrog to be simple and user-friendly, which really helps with managing images. It creates a separate folder for every feature build, making it easy to identify which image is mine. This feature is very user-friendly and solves the big issue of managing images. With 10 to 20 repositories, each having around 100 to 200 images, JFrog serves as a one-stop place for image management. Overall, I find it very helpful and I like that about JFrog. Review collected by and hosted on G2.com.

I mean, I use JFrog in our company's network. Basically, most of the time, JFrog is very slow. The website is very slow, and it takes a lot of time to load. Review collected by and hosted on G2.com.