Alternatives to JFrog Artifactory logo

Alternatives to JFrog Artifactory

jFrog, Sonatype Nexus, BinTray, GitHub, and JitPack are the most popular alternatives and competitors to JFrog Artifactory.
247
245
+ 1
0

What is JFrog Artifactory and what are its top alternatives?

It integrates with your existing ecosystem supporting end-to-end binary management that overcomes the complexity of working with different software package management systems, and provides consistency to your CI/CD workflow.
JFrog Artifactory is a tool in the Java Build Tools category of a tech stack.

Top Alternatives to JFrog Artifactory

  • jFrog

    jFrog

    Host, manage and proxy artifacts using the best Docker Registry, Maven Repository, Gradle repository, NuGet repository, Ruby repository, Debian repository npm repository, Yum repository. ...

  • Sonatype Nexus

    Sonatype Nexus

    It is an open source repository that supports many artifact formats, including Docker, Java™ and npm. With the Nexus tool integration, pipelines in your toolchain can publish and retrieve versioned apps and their dependencies ...

  • BinTray

    BinTray

    Bintray offers developers the fastest way to publish and consume OSS software releases. With Bintray's full self-service platform developers have full control over their published software and how it is distributed to the world. ...

  • GitHub

    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

  • JitPack

    JitPack

    JitPack is an easy to use package repository for Gradle/Sbt and Maven projects. We build GitHub projects on demand and provides ready-to-use packages. ...

  • NuGet

    NuGet

    A free and open-source package manager designed for the Microsoft development platform. It is also distributed as a Visual Studio extension. ...

  • GitLab

    GitLab

    GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers. ...

  • Apache Maven

    Apache Maven

    Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects. ...

JFrog Artifactory alternatives & related posts

jFrog logo

jFrog

84
57
0
Universal Artifact Management
84
57
+ 1
0
PROS OF JFROG
    Be the first to leave a pro
    CONS OF JFROG
      Be the first to leave a con

      related jFrog posts

      Sonatype Nexus logo

      Sonatype Nexus

      414
      269
      0
      organize, store, and distribute software components
      414
      269
      + 1
      0
      PROS OF SONATYPE NEXUS
        Be the first to leave a pro
        CONS OF SONATYPE NEXUS
          Be the first to leave a con

          related Sonatype Nexus posts

          Joshua Dean Küpper
          CEO at Scrayos UG (haftungsbeschränkt) · | 10 upvotes · 159.9K views

          We use Sonatype Nexus to store our closed-source java libraries to simplify our deployment and dependency-management. While there are many alternatives, most of them are expensive ( GitLab Enterprise ), monilithic ( JFrog Artifactory ) or only offer SaaS-licences. We preferred the on-premise approach of Nexus and therefore decided to use it.

          We exclusively use the Maven-capabilities and are glad that the modular design of Nexus allows us to run it very lightweight.

          See more
          Bryan Dady
          SRE Manager at Subsplash · | 3 upvotes · 216.1K views

          I'm beginning to research the right way to better integrate how we achieve SCA / shift-left / SecureDevOps / secure software supply chain. If you use or have evaluated WhiteSource, Snyk, Sonatype Nexus, SonarQube or similar, I would very much appreciate your perspective on strengths and weaknesses and how you selected your ultimate solution. I want to integrate with GitLab CI.

          See more
          BinTray logo

          BinTray

          53
          54
          24
          Deploy jar and binary files to a public server. Easy integration with Maven, Gradle, Yum and Apt
          53
          54
          + 1
          24
          PROS OF BINTRAY
          • 9
            Free for opensource packages
          • 6
            Easy to use
          • 4
            Cool new UI
          • 3
            Fast CDN
          • 2
            Just because it's great DaaS
          CONS OF BINTRAY
            Be the first to leave a con

            related BinTray posts

            Midhun Harikumar
            Senior Associate at Cognizant Technology Solutions · | 2 upvotes · 73.2K views

            Git and GitHub are excellent tools for hosting this open source project. GitHub enables me to do reviews and provides wiki support via GitHub Pages from anywhere. Travis CI is easy to setup and I can pull up my own Android SDK libraries from BinTray .

            See more
            GitHub logo

            GitHub

            169.5K
            136.5K
            10.2K
            Powerful collaboration, review, and code management for open source and private development projects
            169.5K
            136.5K
            + 1
            10.2K
            PROS OF GITHUB
            • 1.8K
              Open source friendly
            • 1.5K
              Easy source control
            • 1.2K
              Nice UI
            • 1.1K
              Great for team collaboration
            • 857
              Easy setup
            • 496
              Issue tracker
            • 478
              Great community
            • 475
              Remote team collaboration
            • 444
              Great way to share
            • 436
              Pull request and features planning
            • 139
              Just works
            • 125
              Integrated in many tools
            • 112
              Free Public Repos
            • 106
              Github Gists
            • 103
              Github pages
            • 81
              Easy to find repos
            • 60
              Open source
            • 58
              Easy to find projects
            • 56
              Network effect
            • 55
              It's free
            • 47
              Extensive API
            • 42
              Organizations
            • 41
              Branching
            • 33
              Developer Profiles
            • 32
              Git Powered Wikis
            • 29
              Great for collaboration
            • 23
              It's fun
            • 22
              Community SDK involvement
            • 21
              Clean interface and good integrations
            • 19
              Learn from others source code
            • 14
              It integrates directly with Azure
            • 14
              Because: Git
            • 13
              Wide acceptance
            • 10
              Large community
            • 9
              Newsfeed
            • 9
              Standard in Open Source collab
            • 8
              It integrates directly with Hipchat
            • 7
              Fast
            • 7
              Beautiful user experience
            • 6
              Cloud SCM
            • 6
              Easy to discover new code libraries
            • 5
              Smooth integration
            • 5
              Nice API
            • 5
              Graphs
            • 5
              Integrations
            • 5
              It's awesome
            • 4
              Hands down best online Git service available
            • 4
              Reliable
            • 4
              Remarkable uptime
            • 3
              Easy to use and collaborate with others
            • 3
              CI Integration
            • 3
              Free HTML hosting
            • 3
              Loved by developers
            • 3
              Quick Onboarding
            • 3
              Security options
            • 3
              Simple but powerful
            • 3
              Uses GIT
            • 3
              Unlimited Public Repos at no cost
            • 3
              Version Control
            • 2
              Nice to use
            • 1
              Free private repos
            • 1
              Easy deployment via SSH
            • 1
              Beautiful
            • 1
              Owned by micrcosoft
            • 1
              Free HTML hostings
            • 1
              Self Hosted
            • 1
              All in one development service
            • 1
              Easy to use
            • 1
              Good tools support
            • 1
              Easy source control and everything is backed up
            • 1
              Leads the copycats
            • 1
              Never dethroned
            • 1
              Ci
            • 1
              Issues tracker
            • 1
              Easy and efficient maintainance of the projects
            • 1
              IAM
            • 1
              IAM integration
            • 0
              Profound
            • 0
              1
            CONS OF GITHUB
            • 45
              Owned by micrcosoft
            • 36
              Expensive for lone developers that want private repos
            • 15
              Relatively slow product/feature release cadence
            • 10
              API scoping could be better
            • 8
              Only 3 collaborators for private repos
            • 3
              Limited featureset for issue management
            • 2
              GitHub Packages does not support SNAPSHOT versions
            • 1
              Have to use a token for the package registry
            • 1
              No multilingual interface
            • 1
              Takes a long time to commit

            related GitHub posts

            Johnny Bell
            Software Engineer at Weedmaps · | 77 upvotes · 1.1M views

            I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

            I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

            I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

            Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

            Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

            With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

            If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

            See more
            Simon Reymann
            Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 2.8M views

            Our whole DevOps stack consists of the following tools:

            • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
            • Respectively Git as revision control system
            • SourceTree as Git GUI
            • Visual Studio Code as IDE
            • CircleCI for continuous integration (automatize development process)
            • Prettier / TSLint / ESLint as code linter
            • SonarQube as quality gate
            • Docker as container management (incl. Docker Compose for multi-container application management)
            • VirtualBox for operating system simulation tests
            • Kubernetes as cluster management for docker containers
            • Heroku for deploying in test environments
            • nginx as web server (preferably used as facade server in production environment)
            • SSLMate (using OpenSSL) for certificate management
            • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
            • PostgreSQL as preferred database system
            • Redis as preferred in-memory database/store (great for caching)

            The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

            • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
            • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
            • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
            • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
            • Scalability: All-in-one framework for distributed systems.
            • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
            See more
            JitPack logo

            JitPack

            30
            59
            11
            JitPack builds GitHub Gradle and Maven projects on demand and provides ready-to-use packages
            30
            59
            + 1
            11
            PROS OF JITPACK
            • 11
              Because uploading to maven central is a ball ache
            CONS OF JITPACK
              Be the first to leave a con

              related JitPack posts

              NuGet logo

              NuGet

              192
              112
              0
              The package manager for .NET
              192
              112
              + 1
              0
              PROS OF NUGET
              • 0
                Best package (and maybe only 1) management for .NET
              CONS OF NUGET
                Be the first to leave a con

                related NuGet posts

                GitLab logo

                GitLab

                38.4K
                31K
                2.3K
                Open source self-hosted Git management software
                38.4K
                31K
                + 1
                2.3K
                PROS OF GITLAB
                • 489
                  Self hosted
                • 418
                  Free
                • 332
                  Has community edition
                • 236
                  Familiar interface
                • 236
                  Easy setup
                • 130
                  Includes many features, including ci
                • 106
                  Nice UI
                • 80
                  Good integration with gitlabci
                • 52
                  Simple setup
                • 32
                  Has an official mobile app
                • 30
                  Free private repository
                • 25
                  Continuous Integration
                • 18
                  Open source, great ui (like github)
                • 14
                  Slack Integration
                • 10
                  Full CI flow
                • 9
                  Free and unlimited private git repos
                • 8
                  User, group, and project access management is simple
                • 7
                  Intuitive UI
                • 7
                  Built-in CI
                • 7
                  All in one (Git, CI, Agile..)
                • 4
                  Both public and private Repositories
                • 3
                  Mattermost Chat client
                • 3
                  Integrated Docker Registry
                • 3
                  Issue system
                • 2
                  Excellent
                • 2
                  Security and Stable
                • 2
                  Free private repos
                • 2
                  Low maintenance cost due omnibus-deployment
                • 2
                  On-premises
                • 2
                  Unlimited free repos & collaborators
                • 2
                  It's fully integrated
                • 2
                  I like the its runners and executors feature
                • 2
                  CI
                • 2
                  So easy to use
                • 2
                  Great for team collaboration
                • 2
                  One-click install through DigitalOcean
                • 2
                  It's powerful source code management tool
                • 2
                  Build/pipeline definition alongside code
                • 1
                  The dashboard with deployed environments
                • 1
                  Multilingual interface
                • 1
                  Native CI
                • 1
                  HipChat intergration
                • 1
                  It includes everything I need, all packaged with docker
                • 1
                  Powerful software planning and maintaining tools
                • 1
                  Groups of groups
                • 1
                  Dockerized
                • 1
                  Beautiful
                • 1
                  Wounderful
                • 1
                  Opensource
                • 1
                  Because is the best remote host for git repositories
                • 1
                  Not Microsoft Owned
                • 1
                  Full DevOps suite with Git
                • 1
                  Many private repo
                • 1
                  Published IP list for whitelisting (gl-infra#434)
                • 1
                  Powerful Continuous Integration System
                • 1
                  Kubernetes Integration
                • 1
                  Kubernetes integration with GitLab CI
                • 1
                  Review Apps feature
                • 1
                  Built-in Docker Registry
                • 0
                  Supports Radius/Ldap & Browser Code Edits
                CONS OF GITLAB
                • 26
                  Slow ui performance
                • 6
                  Introduce breaking bugs every release
                • 5
                  Insecure (no published IP list for whitelisting)
                • 0
                  Built-in Docker Registry
                • 0
                  Review Apps feature

                related GitLab posts

                Tim Abbott
                Shared insights
                on
                GitHub
                GitLab
                at

                I have mixed feelings on GitHub as a product and our use of it for the Zulip open source project. On the one hand, I do feel that being on GitHub helps people discover Zulip, because we have enough stars (etc.) that we rank highly among projects on the platform. and there is a definite benefit for lowering barriers to contribution (which is important to us) that GitHub has such a dominant position in terms of what everyone has accounts with.

                But even ignoring how one might feel about their new corporate owner (MicroSoft), in a lot of ways GitHub is a bad product for open source projects. Years after the "Dear GitHub" letter, there are still basic gaps in its issue tracker:

                • You can't give someone permission to label/categorize issues without full write access to a project (including ability to merge things to master, post releases, etc.).
                • You can't let anyone with a GitHub account self-assign issues to themselves.
                • Many more similar issues.

                It's embarrassing, because I've talked to GitHub product managers at various open source events about these things for 3 years, and they always agree the thing is important, but then nothing ever improves in the Issues product. Maybe the new management at MicroSoft will fix their product management situation, but if not, I imagine we'll eventually do the migration to GitLab.

                We have a custom bot project, http://github.com/zulip/zulipbot, to deal with some of these issues where possible, and every other large project we talk to does the same thing, more or less.

                See more
                Joshua Dean Küpper
                CEO at Scrayos UG (haftungsbeschränkt) · | 17 upvotes · 241K views

                We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.

                While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.

                We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.

                See more
                Apache Maven logo

                Apache Maven

                2.2K
                1.4K
                413
                Apache build manager for Java projects.
                2.2K
                1.4K
                + 1
                413
                PROS OF APACHE MAVEN
                • 137
                  Dependency management
                • 71
                  Necessary evil
                • 59
                  I’d rather code my app, not my build
                • 48
                  Publishing packaged artifacts
                • 43
                  Convention over configuration
                • 18
                  Modularisation
                • 11
                  Consistency across builds
                • 6
                  Prevents overengineering using scripting
                • 4
                  Runs Tests
                • 4
                  Lot of cool plugins
                • 3
                  Extensible
                • 2
                  Hard to customize
                • 2
                  Runs on Linux
                • 1
                  Runs on OS X
                • 1
                  Slow incremental build
                • 1
                  Inconsistent buillds
                • 1
                  Undeterminisc
                • 1
                  Good IDE tooling
                CONS OF APACHE MAVEN
                • 6
                  Complex
                • 1
                  Inconsistent buillds
                • 0
                  Not many plugin-alternatives

                related Apache Maven posts

                Tymoteusz Paul
                Devops guy at X20X Development LTD · | 22 upvotes · 4.4M views

                Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

                It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

                I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

                We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

                If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

                The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

                Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

                See more
                Shared insights
                on
                Apache Maven
                Gradle
                at

                We use Apache Maven because it is a standard. Gradle is very good alternative, but Gradle doesn't provide any advantage for our project. Gradle is slower (without running daemon), need more resources and a learning curve is quite big. Our project can not use a great flexibility of Gradle. On the other hand, Maven is well-know tool integrated in many IDEs, Dockers and so on.

                See more