We usually use it to store our artifacts, version them, and use them in production. We use it in CI/CD pipelines. All our R&D uses it as do all our development teams that need to release software. It doesn't matter what, they use it.
External reviews
External reviews are not included in the AWS star rating for the product.
Good artifact storage tool
JFrog : The core of DevOps automation
1. Efficient dependency management: Artifactory helps to reduce the time and effort required to resolve and manage dependencies for your builds. It acts as a cache for external dependencies, so you don't have to download them repeatedly from external sources.
2. Improved build speeds: By using a local repository manager such as Artifactory, you can significantly improve the speed of your builds.
3. Enhanced security: Artifactory includes fine-grained permissions and access control, which can help secure your artefacts and ensure that only authorised users have access.
4. Simplified deployment: The JFrog platform includes tools such as Bintray and Xray that can help streamline distributing and deploying your artefacts.
5. Better traceability: Artifactory tracks all deployments and resolves dependencies, making it easier to understand how your artefacts are being used and trace any issues that may arise.
6. Improved collaboration: The JFrog platform makes it easier for teams to collaborate and share artefacts, improving communication and productivity.
Another potential issue is that the JFrog platform is complex and can have a steep learning curve. It includes a range of tools and features, and it may take some time to become proficient.
Finally, the JFrog platform requires a dedicated server, which can be an additional overhead for some organisations. This may not be a problem for larger companies that already have the infrastructure, but it could be a challenge for smaller organisations or individual developers.
Some specific business problems that the JFrog platform can help to solve include:
1. Reducing build times: By using a local repository manager such as Artifactory, you can significantly improve the speed of your builds by avoiding the need to download dependencies from external sources repeatedly.
2. Improving collaboration: The JFrog platform makes it easier for teams to share artifacts and collaborate, improving communication and productivity.
3. Enhancing security: Artifactory includes features such as fine-grained permissions and access control, which can help secure your artifacts and ensure that only authorized users have access.
4. Simplifying deployment: The JFrog platform includes tools such as Bintray and Xray that can help streamline distributing and deploying your artifacts.
5. Providing better traceability: Artifactory tracks all deployments and resolves dependencies, making it easier to understand how your artifacts are being used and trace any issues that may arise.
JFrog - Great Platform for Container and Artifact Management
Review for JFROG Artifactory
Great solution to store artifacts
Save us the time and mundane work of maintaining multiple repositories for different types of artifacts
What is our primary use case?
How has it helped my organization?
JFrog Artifactory is very essential to us. Without it, we could not use the artifacts, the products that our developers are writing. We would need to maintain a lot of different artifactory repositories in a lot of places. It would be more difficult. You definitely need some kind of artifactory solution. It doesn't necessarily need to be JFrog, but in my opinion, it's better to use it because it's a good, centralized solution. I haven't found any good competitors.
The way to explain to C-suite executives why they should continue to invest in JFrog is that it saves a lot of time and a lot of mundane work that would be required to maintain many solutions that JFrog gives you in one solution.
We don't have to maintain a lot of repositories. We get the same outcome with JFrog with less maintenance. With the SaaS solution, we don't even need to maintain the installation, the server, or whatever infrastructure is around it. There is less involvement in artifactory management.
We don't need to use all kinds of artifactories like Docker Hub or different PyPI repositories for Python. Everything is there and we don't need to pay different companies for all these solutions or to maintain them.
It gives us a good workflow in terms of how we create software because we use it for all of our artifact types. It's good that it's centralized and it helps us in our CI/CD flows, to release software. You don't need to create different scripts or automations to upload different kinds of artifacts to different vendors or repositories. It simplifies our workflow.
What is most valuable?
The most valuable feature is that it is a centralized repository and that you can open multiple repositories for different types of artifacts. That is very good.
Also, the fact that you can integrate artifacts with authentication systems, like Active Directory or Okta is valuable.
And for binary management, versioning them, it does a very good job and it gives us a good API to work with.
What needs improvement?
In some of the latest versions of JFrog's SaaS solution, they changed the user interface, the SSO settings, how you interact with them over API, and how you generate tokens. It was very confusing for me. The overall user management is very complicated.
Also, their documentation about how to do things could be better. It was very confusing. I had been using it for a couple of years and then they completely changed how it works—the user and token management.
For how long have I used the solution?
I have been using JFrog Artifactory for three or four years. I have used it in almost every workplace.
What do I think about the stability of the solution?
It's very stable. I don't think I have had many problems. There may have been some many years ago, maybe, but not something critical.
What do I think about the scalability of the solution?
It scales very well. In a previous company, we used it in a couple of locations globally and it was also an on-premises installation. We used the syncing options for repositories and it worked very well. We didn't have a lot of problems setting it up or using it.
In my current company, we have about 200 users.
We use it all the time. If we have another artifact type to throw in it, we will increase our usage of it. Every new software that we have developed and released has gone to JFrog Artifactory. We're always increasing its use.
How are customer service and support?
The technical support is an eight out of 10.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Before JFrog Artifactory, we used all kinds of solutions, like Docker Hub and PyPI, but we didn't have a centralized solution like JFrog.
What was our ROI?
drop database *;
What other advice do I have?
It's very good that they have SaaS and non-SaaS solutions. You can take the SaaS solution and simply use and get support. But for small companies that don't want to invest in paying them for the solution, their free, on-premises solution is very good. It's almost the same as the paid version, minus the support and some features. It's very important that they have both options.
Because we use the SaaS solution, there is no maintenance involved for us. They maintain it. We maintain our versions and artifacts within it, but not the system itself.
Artifact did not affect how long it took us to fix the Log4j issue because our company was part of some cybersecurity companies that detected the breach and we fixed it for ourselves.
I would recommend using it because it's a great tool. Everyone is using it, most companies, as far as I know. It's a very well-known solution. It's a good, centralized solution.