Answers: <p><strong>TL;DR:</strong> </p>
  
  <ul>
  <li><strong>Bintray</strong> 
  
  <ol>
  <li>Software for other people's use.</li>
  <li>Publishing platform</li>
  <li>Released software</li>
  <li>Selective, distributed, download optimized, network heavy</li>
  </ol></li>
  <li><strong>Artifactory</strong>
  
  <ol>
  <li>Software for your own use.</li>
  <li>Caching platform</li>
  <li>All derived objects and binary dependencies for CI/CD</li>
  <li>Inclusive, centralized, upload optimized, storage heavy</li>
  </ol></li>
  </ul>
  
  <p><strong>Disclosure</strong>: JFrog did not offer me a job. :)</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-01-04T00:28:05.787Z
Answers: regarding the disclosure, it's not too late :)
Answers: JBaruch
Answers: CC BY-SA 4.0
Answers: 2019-01-03T22:09:49.457Z
Answers: 2019-01-03T22:09:49.457Z
Answers: Jiri Klouda
Answers: <p><a href="https://www.jfrog.com/artifactory/" rel="nofollow noreferrer">JFrog Artifactory</a> and <a href="https://www.jfrog.com/bintray/" rel="nofollow noreferrer">JFrog Bintray</a> both manage binaries (and any other file type you can think of). I'd like to see them as two different parts of your CI/CD pipeline.</p>
  
  <p><strong>Artifactory</strong> is mostly meant to be used inside the organization. For managing all binaries coming in as dependencies (like maven central jars) and being produced by your build process (like your <code>pack.rpm</code> or <code>org/pack-docker</code> docker image). These can later be used by others in the org or released to <strong>Bintray</strong>.</p>
  
  <p><strong>Bintray</strong> is meant to provide a universal distribution platform for your end deliverables. For example, the <code>pack.rpm</code> you want to be available for your customers to download. And also that <code>org/pack-docker</code> docker image.</p>
  
  <p>Look into the features lists of each and see how they differ in order to best match their intended role.  </p>
  
  <ul>
  <li><a href="https://www.jfrog.com/artifactory/features/" rel="nofollow noreferrer">Artifactory features</a></li>
  <li><a href="https://jfrog.com/bintray/features/" rel="nofollow noreferrer">Bintray features</a> </li>
  </ul>
  
  <p>I hope this helps explaining the differences.</p>
  
  <p><strong>Disclosure</strong>: I work at JFrog</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-07-17T09:06:34.777Z
Answers: 2018-01-12T16:29:14.043Z
Answers: 2018-01-12T16:29:14.043Z
Answers: Eldad Assis
Body: <p>We are actually looking for a package management system for our project.
  The target is simple, have a centralized system to keep our packages ( apps and middlewares ) and use them with our CI/CD tools (Jenkins, Ansible, Docker ...)</p>
  
  <p>Looking for options I discovered <a href="https://www.jfrog.com/artifactory/" rel="noreferrer">JFrog Artifactory</a> and <a href="https://bintray.com/" rel="noreferrer">JFrog Bintray</a>. they both seems to do the same job but I don't believe JFrog is maintaining two concurrent products with the same options.</p>
  
  <p>What is the difference between Artifactory and Bintray?<br>
  How do we choose one over the other and why?</p>
  
Comments: CC BY-SA 4.0
Comments: 2019-01-03T19:35:12.793Z
Comments: Please check [this answer](https://stackoverflow.com/questions/38877177/what-is-the-difference-between-jfrog-artifactory-and-bintray/38979659#38979659) to the similar question on StackOverflow.
Comments: JBaruch
Tags: <continuous-integration><artifacts><artifactory>
Title: JFrog Artifactory or JFrog Bintray , when to use one over the other?
UserDisplayName: storm
ThreadText: # JFrog Artifactory or JFrog Bintray , when to use one over the other?
  
  (Asked by: username_0 on 2017-07-16)
  
  We are actually looking for a package management system for our project.
  The target is simple, have a centralized system to keep our packages ( apps and middlewares ) and use them with our CI/CD tools (Jenkins, Ansible, Docker ...)
  
  Looking for options I discovered [JFrog Artifactory](https://www.jfrog.com/artifactory/) and [JFrog Bintray](https://bintray.com/). they both seems to do the same job but I don't believe JFrog is maintaining two concurrent products with the same options.
  
  What is the difference between Artifactory and Bintray?  
  How do we choose one over the other and why?
  
  **Tags:** continuous-integration, artifacts, artifactory
  
  > **Comments:**
  > **username_1**: Please check [this answer](https://stackoverflow.com/questions/38877177/what-is-the-difference-between-jfrog-artifactory-and-bintray/38979659#38979659) to the similar question on StackOverflow.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2017-07-17. Score: 8 | Accepted answer
  
  [JFrog Artifactory](https://www.jfrog.com/artifactory/) and [JFrog Bintray](https://www.jfrog.com/bintray/) both manage binaries (and any other file type you can think of). I'd like to see them as two different parts of your CI/CD pipeline.
  
  **Artifactory** is mostly meant to be used inside the organization. For managing all binaries coming in as dependencies (like maven central jars) and being produced by your build process (like your `pack.rpm` or `org/pack-docker` docker image). These can later be used by others in the org or released to **Bintray**.
  
  **Bintray** is meant to provide a universal distribution platform for your end deliverables. For example, the `pack.rpm` you want to be available for your customers to download. And also that `org/pack-docker` docker image.
  
  Look into the features lists of each and see how they differ in order to best match their intended role.
  
  * [Artifactory features](https://www.jfrog.com/artifactory/features/)
  * [Bintray features](https://jfrog.com/bintray/features/)
  
  I hope this helps explaining the differences.
  
  **Disclosure**: I work at JFrog
  
  
  ---
  
  ### Answer by username_2 on 2019-01-03. Score: 0
  
  **TL;DR:**
  
  * **Bintray**
    1. Software for other people's use.
    2. Publishing platform
    3. Released software
    4. Selective, distributed, download optimized, network heavy
  * **Artifactory**
    1. Software for your own use.
    2. Caching platform
    3. All derived objects and binary dependencies for CI/CD
    4. Inclusive, centralized, upload optimized, storage heavy
  
  **Disclosure**: JFrog did not offer me a job. :)
  
  > **Comments:**
  > **username_1**: regarding the disclosure, it's not too late :)  
  
  ---
  
  