Hosting your own NuGet feeds

Instead of making packages publicly available, you might want to release packages to only a limited audience, such as your organization or workgroup. In addition, some companies may want to restrict which third-party libraries their developers may use, and thus direct those developers to draw from a limited package source rather than

For all such purposes, NuGet supports setting up private package sources in the following ways:

  • Local feed: Packages are simply placed on a suitable network file share, ideally using nuget init and nuget add to create a hierarchical folder structure (NuGet 3.3+). For details, see Local Feeds.
  • NuGet.Server: Packages are made available through a local HTTP server. For details, see NuGet.Server.
  • NuGet Gallery: Packages are hosted on an Internet server using the NuGet Gallery Project ( NuGet Gallery provides user management and features such as an extensive web UI that allows searching and exploring packages from within the browser, similar to

There are also several other NuGet hosting products that support remote private feeds, including the following:

  • Azure Artifacts, which is also available on Team Foundation Server 2017 and later.
  • MyGet
  • ProGet from Inedo
  • NuGet Server, a community project from Inedo
  • NuGet Server (Open Source), an open-source implementation similar to Inedo's NuGet Server
  • LiGet, an open-source implementation of NuGet V2 server that runs on kestrel in docker
  • BaGet, an open-source implementation of NuGet V3 server built on ASP.NET Core
  • Sleet, an open-source NuGet V3 static feed generator
  • Artifactory from JFrog.
  • Nexus from Sonatype.
  • TeamCity from JetBrains.

Regardless of how packages are hosted, you access them by adding them to the list of available sources in NuGet.Config. This can be done in Visual Studio as described in Package Sources, or from the command line using nuget sources. The path to a source can be a local folder pathname, a network name, or a URL.