JFrog Software Supply Chain Platform

What do you like best about the product?

I like that everything is in one place and it’s pretty easy to find the packages we need. It saves us time when we’re working across multiple projects because we don’t have to go through multiple sources to get the right package or version. It also helps us manage our builds more easily.

What do you dislike about the product?

I find JFrog’s UI confusing for a new user, and there are too many options, which can feel overwhelming. Finding certain settings is always a ride in itself, and the UX for repository settings and permissions needs work. The setup is pretty straightforward, but dialing in settings and permissions took a considerable amount of time.

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

JFrog keeps our packages and versions in one place instead of all around the place, and it helps us manage our builds more easily.

What do you like best about the product?

I like being able to store all our image repositories in an organized way. Setting up Maven repositories is straightforward, and it’s easy to download older ones that were lost during newer deployments.

What do you dislike about the product?

The interface could be more aesthetically pleasing and interactive. As a software developer, the work can get boring as it is, and a nicer-looking interface would make it feel a bit less monotonous.

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

I keep all my repositories and Docker images in one consolidated place, which makes it easier to track them and maintain a clear record of everything from the first deployment through to the latest one.

What do you like best about the product?

What I value most about JFrog Artifactory is having one place to manage all our packages. Our team works on a React Native app, so we deal with npm packages, CocoaPods, and Gradle dependencies, and Artifactory lets us proxy and cache all of them through a single platform instead of juggling separate registries.

The remote repository caching has made a real difference in our day-to-day work. Before, our CI builds would occasionally fail when a public registry was slow or a package was temporarily unavailable. Now dependencies are served from our Artifactory cache, so builds are faster and much more reliable. It also protects us if a package gets removed from the public registry, since we still have the cached version.

We also use it to host our internal libraries privately. Publishing a shared component to our own npm repository and installing it like any other package is simple, and the access controls let us decide exactly who can read or publish to each repository.

An unexpected benefit has been visibility. Being able to search for an artifact, see its versions, and check where it came from has saved us time when debugging dependency issues, because we can quickly confirm which version a build actually used. With JFrog Xray, we also get alerts about known vulnerabilities in our dependencies, which helps us catch security problems before they reach production

What do you dislike about the product?

The biggest challenge with JFrog Artifactory is the learning curve. The interface has a lot of options, and for new team members it isn’t always obvious where to find settings or how repositories, permissions, and virtual repositories fit together. Setting up our first remote and virtual repositories for npm and CocoaPods took longer than expected because we had to piece together the correct configuration from several documentation pages. A guided setup wizard for common stacks, such as React Native with npm, CocoaPods, and Gradle together, would make onboarding much faster.

The documentation could also be more consistent. Some pages refer to older versions of the UI, so the screenshots and menu names don’t always match what we see. This sometimes sends us to community forums or support to confirm a simple configuration detail. Keeping the docs aligned with the current interface and adding more end-to-end examples would help a lot.

Storage management needs more attention than we’d like. Cached artifacts and old build versions accumulate quickly, and setting up cleanup and retention policies isn’t very intuitive. Clearer built-in retention rules, along with a simple dashboard showing which repositories use the most space, would make it easier to keep storage under control and costs predictable.

Finally, pricing can be hard to evaluate for smaller teams, since some useful features like advanced security scanning are tied to higher tiers. More flexible options for small teams would make it easier to adopt the full platform.

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

Before JFrog Artifactory, our React Native team pulled dependencies directly from public registries like npm, CocoaPods, and Maven. We struggled with unreliable CI builds, because a slow or unavailable registry could break a build that had nothing wrong with the code. Now all dependencies are cached in Artifactory, so builds no longer depend on outside services being up. This has cut our dependency-related build failures by about 20% and reduced average CI build time by around 10 minutes, since packages are served from our own cache.

We also struggled to share internal code between projects. Shared components were copied between repositories or installed from Git links, which made versioning messy and updates easy to miss. Now we publish internal libraries to a private npm repository in Artifactory and install them like any other package, with proper version numbers. This has saved us roughly 3 hours per week that we used to spend syncing code manually, and it has made our apps more consistent.

Security was another gap. We had no easy way to know if a dependency contained a known vulnerability. With JFrog Xray scanning our artifacts, we now get alerts about vulnerable packages before they reach production, and we have fixed 15 issues that we otherwise would have missed.

Overall, Artifactory has given us a single, reliable source for every package our builds use, which makes our releases more predictable and our team more confident in what we ship.

What do you like best about the product?

Help to manage and version our big size artifactory. It provides useful automation and redemption. It is also quite reliable. Also we like because there is a version that could be deployed on our servers.

What do you dislike about the product?

JFrog Artifactory is a powerful tool, but the UI can feel overly complicated for day-to-day work. Tasks like finding specific artifacts, navigating between repositories, and managing permissions aren’t always intuitive. Troubleshooting can also be difficult, since error messages are sometimes vague and end up forcing you to dig through logs to understand what’s going on. On top of that, the platform can be resource-intensive and tends to require ongoing maintenance to keep it running smoothly.

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

JFrog Artifactory helps us manage build artifacts and dependencies in a centralized place. It gives us a reliable repository for Docker images and software packages, which makes our CI/CD pipelines more consistent and reproducible. It also streamlines artifact versioning and access control, so we spend less time managing multiple package registries and our deployments are easier to maintain over time.

What do you like best about the product?

I like JFrog’s ability to securely manage, store, and distribute software artifacts in one centralized platform, making CI/CD pipelines more efficient, reliable, and scalable.

What do you dislike about the product?

JFrog can be complex to configure and manage, and its licensing costs can be high. The user interface could also be more intuitive, with better documentation and simpler integrations.

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

JFrog helps solve challenges around software artifact management, security, and release automation. It provides a centralized platform to store, manage, and distribute artifacts, improving CI/CD efficiency

What do you like best about the product?

I work for quite a large company where having a single source of truth like JFrog is super helpful. Internally, we use npm, maven, docker and Go and having JFrog as our global repo manager is great.

What do you dislike about the product?

The cost. Especially for the smaller internal teams, where the free tier is not quite enough for our use cases. I also personally found it quite a steep learning curve to use and integrate into my workflows.

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

It is our universal artefact support. Our teams work with Maven, npm, Docker etc and having a single source of truth we can all access is needed. We have it integrated into our CICD pipelines making automated releases more robust.

What do you like best about the product?

I like JFrog's smooth integration. It helps me build artifacts across different projects and store and manage Docker images. The initial setup was pretty straightforward.

What do you dislike about the product?

I find JFrog's user interface could be easier to navigate.

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

JFrog helps me build artifacts across different projects.

What do you like best about the product?

I like JFrog for its speed and ease of use. It's much faster and more convenient compared to our previous tool, Minio. The faster the product, the more efficient the programmer can be, which is a real advantage for my work. Setting up JFrog was also straightforward — we had no problems getting it started.

What do you dislike about the product?

I find it frustrating that there's no auto-clean feature, or maybe our admins aren't using it, which frequently leads to issues with "disk out of space."

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

JFrog keeps our packages safe and organized. It's faster and easier to use than Minio, speeding up our programming efficiency.

What do you like best about the product?

I like how JFrog makes navigating to relevant tabs and filtering suppliers easy. Adding new suppliers for connecting with them is a feature I value. The initial setup was smooth, which was a pleasant surprise.

What do you dislike about the product?

All feature great so far

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

JFrog helps me manage vendor locations and navigate relevant tabs efficiently, especially for adding and connecting with new suppliers.

What do you like best about the product?

What I like most about JFrog is how much it simplifies managing and delivering software. It’s reliable, integrates smoothly with our existing tools, and saves us a lot of time when handling artifacts and deployments.

What do you dislike about the product?

The pricing can feel a bit high, and some features take time to learn. The interface could also be simpler for new users and teams, and the documentation could be clearer to make onboarding and day-to-day use easier.

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

JFrog makes it easier for us to manage software packages and deployments, which saves time, reduces errors, and keeps our development process more organized overall.