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.

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.

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.

JFrog work well for me.Mainly because I noticed a lot of improvement in our build and deployment process due to the centralization of all resources. We had different artifacts and different version numbers of packages before, which created confusion regarding which build to use. In JFrog, I was able to upload all artifacts in a single place and link them to my CI/CD processes. Also, the repositories used here included build packages as well as container images, and I found it very easy to troubleshoot any issues with the deployed build by referring to the version history. Review collected by and hosted on G2.com.

The first configuration was a lot harder for me to configure than anticipated. I still vividly recall spending hours comprehending the organizational structure of repositories, permissions, and the classification of various packages. As soon as I began to have many repositories, it took consistent effort on my part to maintain their organization or else they would easily get disorganized. I further realized that there were portions of the interface that were not as user-friendly as I would expect them to be, such as switching from one repository to another or dealing with access problems. Review collected by and hosted on G2.com.

JFrog has a strong ecosystem, and a lot of developers use it. It’s no longer just a package manager; it has also become a security system and a CI/CD automation platform. Review collected by and hosted on G2.com.

As far as I know, JFrog is very good at many things, but one area that still feels difficult is the steep learning curve during the initial setup. That early complexity can make it harder for new learners to get started and learn the tool quickly. Review collected by and hosted on G2.com.

I like JFrog most for its artifact management and security scanning. It makes handling binaries smooth, integrates well with CI/CD pipelines, and adds strong, reliable vulnerability checks for DevOps teams, even though it can feel a bit complex for beginners.

In short: scalable, secure, and integration-friendly. Review collected by and hosted on G2.com.

I dislike that JFrog can feel complex to use for beginners, with a steep learning curve. Its pricing is also on the higher side compared to alternatives, and some users find the reporting features limited when it comes to advanced analytics. Review collected by and hosted on G2.com.

I like JFrog because it provides a centralized repository for managing artifacts and dependencies. It integrates well with CI/CD tools, making builds and deployments more efficient. The user interface is easy to navigate, and the platform supports multiple package types, helping teams streamline software development and release management. Review collected by and hosted on G2.com.

JFrog is a powerful platform, but the initial setup and configuration can be complex, especially for new users. Some advanced features have a learning curve, and navigating all the available options can take time. Pricing may also be a concern for smaller teams. Better onboarding documentation and more beginner-friendly tutorials would make the platform easier to adopt. Review collected by and hosted on G2.com.

What I like most about JFrog is how it centralizes everything related to software packages and artifacts in one place. That consolidation has made our release process far more organized and dependable. Instead of juggling packages across multiple repositories, we can store, version, and distribute them from a single platform, which makes deployments noticeably smoother.

A feature I rely on often is Artifactory’s support for multiple package formats. Whether we’re working with Docker images, Maven, npm, or other package types, it all gets handled in a consistent way. Integrating it with our CI/CD pipeline was also straightforward, and once it was connected, it automated a lot of the manual steps we used to do ourselves. As a result, we’ve saved time and seen fewer deployment mistakes.

From a UI standpoint, the interface feels clean and easy to navigate. Finding artifacts, checking versions, and managing repositories doesn’t require digging through complicated menus, which is especially useful when we’re troubleshooting build issues.

Performance has been strong as well. Uploads and downloads are fast, and we’ve rarely run into downtime or delays, even when multiple developers are working at the same time. That level of reliability gives us more confidence during releases.

I’ve also appreciated the documentation and onboarding experience. There are plenty of guides and examples, so getting started wasn’t difficult, and when we’ve needed support, the responses have been helpful and knowledgeable.

Another feature that has added value is JFrog’s AI-powered security and intelligence capabilities. The platform helps surface vulnerabilities and provides useful insights into dependencies, making it easier to identify potential risks early in the development lifecycle instead of discovering them later during deployment.

One unexpected benefit has been improved traceability. Being able to quickly see where artifacts came from, which versions were deployed, and how everything ties together has made debugging and auditing much easier than it used to be.

Overall, JFrog has streamlined our development workflow, improved collaboration across the team, and reduced the time we spend managing artifacts manually. While it’s a premium product, the time savings, automation, reliability, and intelligent security insights have made it a worthwhile investment for our team. Review collected by and hosted on G2.com.

JFrog is a powerful platform, but it does have a fairly steep learning curve, especially when configuring advanced features. While the UI is clean, some settings could be more intuitive.

The pricing can also be high for smaller teams, and the AI-powered features, while useful, could provide more proactive recommendations and automation. Improving onboarding, simplifying advanced workflows, and enhancing the AI capabilities would make the overall experience even better. Review collected by and hosted on G2.com.