<p>To add more info to John's answer above: the author of that comparison article updated it at <a href="https://www.eficode.com/blog/artifactory-nexus-proget" rel="nofollow noreferrer">https://www.eficode.com/blog/artifactory-nexus-proget</a></p>
<p>From my opinion, I left jFrog and went with Nexus because Nexus free version has all my needs (repo type: Maven, yum, pypi and Docker; feature: proxy repo, private repo, group repo; authentication: LDAP/Active directory).
Since I am neither using CI/CI feature nor opening my repo to the internet, I couldn't (and shouldn't) give any comments on that point.</p>

CC BY-SA 4.0
2021-02-01T00:40:55.797Z
2021-02-01T00:40:55.797Z
hlv_trinh
<p>I have used both in enterprise settings a fair bit, but I had never really thought this through until reading the question.  Artifactory seems much more complete/impressive to me, but I have used it more recently than Neuxs, so I was worried that I might be biased.</p>

<p>I just spent ~30 minutes reading online.  Virtually every comparison or article is either totally biased (literally JFROG or Sonatype supported), or is just lacking in detail.</p>

<p>I eventually did find this though, which is fairly in line with my initial thoughts:  <a href="https://www.praqma.com/stories/artifactory-nexus-proget/" rel="noreferrer">https://www.praqma.com/stories/artifactory-nexus-proget/</a>:</p>

<ul>
<li>Artifactory supports far more repository types.</li>
<li>Atifactory has a far better REST API (and has often been ahead on feature development, though it seems like Nexus does catch up over time).</li>
<li>Nexus is a little more extensible.</li>
<li>Artifactory costs significantly more.</li>
</ul>

<p>So... both are good.  If you aren't amazingly cost conscious and want the best overall tool, probably choose artifactory.  If you have specific needs and Nexus covers your required repository types, it might be worth using it to save some money as it is a solid product in the end.</p>

CC BY-SA 4.0
2020-02-28T21:54:41.120Z
Thank you very much for your comment, and for taking the time to find a good article!! The link you posted was full of good information :)
Ivy
CC BY-SA 4.0
2020-02-28T03:42:54.333Z
2020-02-28T03:42:54.333Z
John Humphreys
<p>Am using both right now.  </p>

<p>Nexus will support more repo types with the free version than Artifactory</p>

<p>but</p>

<p>Artifactory will have more repos support in the paid tier</p>

<p>Nexus now support Conda natively (since a few weeks ago if memory serves)</p>

<p>Artifactory will be quite pricey, especially if you plan on having tests and staging instances to test out your config and/or custom plugins as you will have to shell for at least a Pro instance (3K+USD).  Nexus will allow you to test most of these with the free version.</p>

<p>JFrog has exemplary support but a bit pushy with their sales.  They will have help around though to get you started should you need it.</p>

<p>I have not tried Nexus support or sales force so I cant comment (the free version was plenty enough for our needs).</p>

<p>I found the plugin framework to be more usable with Artifactory though it felt a bit limited.  Nexus seems more powerfull but it can be difficult to upgrade/remove plugins from a working instance.  On that front I much preferred Artifactory.</p>

<p>Overall we did go with Artifactory, personally I find them to be pretty much equivalent.  It will depend a bit on the actual technology you need supported (pypi, nuget, maven etc).</p>

CC BY-SA 4.0
2020-02-28T18:03:53.173Z
Thank you very much for your response, it gives me better insight!!
Ivy
CC BY-SA 4.0
2020-02-28T14:58:20.293Z
2020-02-28T14:58:20.293Z
Newtopian
<p>I was wondering what is the recommendation for a business that needs to store binaries for distribution as well as for dependencies to be used by our projects, with projects in different languages/technologies (.NET, Javascript/Java, C/C++, TAL).</p>

<p>Thank you, any info is appreciated!!</p>

<artifactory><nexus>
Nexus vs. Artifactory
Ivy
# Nexus vs. Artifactory

(Asked by: username_0 on 2020-02-28)

I was wondering what is the recommendation for a business that needs to store binaries for distribution as well as for dependencies to be used by our projects, with projects in different languages/technologies (.NET, Javascript/Java, C/C++, TAL).

Thank you, any info is appreciated!!

**Tags:** artifactory, nexus


---

## 3 answers

### Answer by username_2 on 2020-02-28. Score: 10

I have used both in enterprise settings a fair bit, but I had never really thought this through until reading the question. Artifactory seems much more complete/impressive to me, but I have used it more recently than Neuxs, so I was worried that I might be biased.

I just spent ~30 minutes reading online. Virtually every comparison or article is either totally biased (literally JFROG or Sonatype supported), or is just lacking in detail.

I eventually did find this though, which is fairly in line with my initial thoughts: <https://www.praqma.com/stories/artifactory-nexus-proget/>:

* Artifactory supports far more repository types.
* Atifactory has a far better REST API (and has often been ahead on feature development, though it seems like Nexus does catch up over time).
* Nexus is a little more extensible.
* Artifactory costs significantly more.

So... both are good. If you aren't amazingly cost conscious and want the best overall tool, probably choose artifactory. If you have specific needs and Nexus covers your required repository types, it might be worth using it to save some money as it is a solid product in the end.

> **Comments:**
> **username_0**: Thank you very much for your comment, and for taking the time to find a good article!! The link you posted was full of good information :)  

---

### Answer by username_3 on 2020-02-28. Score: 10

Am using both right now.

Nexus will support more repo types with the free version than Artifactory

but

Artifactory will have more repos support in the paid tier

Nexus now support Conda natively (since a few weeks ago if memory serves)

Artifactory will be quite pricey, especially if you plan on having tests and staging instances to test out your config and/or custom plugins as you will have to shell for at least a Pro instance (3K+USD). Nexus will allow you to test most of these with the free version.

JFrog has exemplary support but a bit pushy with their sales. They will have help around though to get you started should you need it.

I have not tried Nexus support or sales force so I cant comment (the free version was plenty enough for our needs).

I found the plugin framework to be more usable with Artifactory though it felt a bit limited. Nexus seems more powerfull but it can be difficult to upgrade/remove plugins from a working instance. On that front I much preferred Artifactory.

Overall we did go with Artifactory, personally I find them to be pretty much equivalent. It will depend a bit on the actual technology you need supported (pypi, nuget, maven etc).

> **Comments:**
> **username_0**: Thank you very much for your response, it gives me better insight!!  

---

### Answer by username_1 on 2021-02-01. Score: 3

To add more info to John's answer above: the author of that comparison article updated it at <https://www.eficode.com/blog/artifactory-nexus-proget>

From my opinion, I left jFrog and went with Nexus because Nexus free version has all my needs (repo type: Maven, yum, pypi and Docker; feature: proxy repo, private repo, group repo; authentication: LDAP/Active directory).
Since I am neither using CI/CI feature nor opening my repo to the internet, I couldn't (and shouldn't) give any comments on that point.


---

