SymbolSource instances a.k.a company accounts

The first thing that you need to know is that SymbolSource is based on instances with separate user databases. These are also known as company accounts, because their main purpose is to provide indepenetent symbols and source servers in cloud, software-as-a-service offering.

Unless you decide to subscribe to one of our commercial plans, most of the time you'll be using be Public instance, where you can register a private account for youself, or the MyGet instance, which shares users with

Inputs and outputs, plugs and sockets

SymbolSource consumes NuGet and OpenWrap packages and stores their content while indexing symbols and sources for later on-demand access. These are all stored in repositories, which have separate package (project) namespaces. The diagram below illustrates fictional repositories 1 and 2.

SymbolSource Public accepts packages at URLs constructed the following way:

  • using NuGet to push:
  • using OpenWrap to push:

Learn more about the methods, tools and best practises of publishing to SymbolSource

When you want Visual Studio to get symbols and sources included in those packages, you need to point it to:

  • the anonymous debugging URL, which skips projects with restricted access:,
  • an authenticated URL, which you can learn more about by clicking the link below.

Learn more about configuring Visual Studio and using SymbolSource during debugging

Because SymbolSource can also serve NuGet and OpenWrap packages, you can also use the following URLs:

  • with NuGet to get packages:
  • with OpenWrap to get wraps:

Note that packages downloaded from SymboSource will not contain any symbols or sources. These are stripped away and stored separately for serving with the SRCSRV protocol on-demand. This means that you can push an all-in-one package once to SymbolSource and have everything set up for the best experience: with binary-only packages for referencing and symbols/sources available on-demand during debugging.

Learn more about using SymbolSource as a package store with NuGet and OpenWrap

Repositories available in the Public instance

There are a couple of main repositories available at These repositories are all open for read access, but pushing packages requires additional permissions - and more on that later.

  • Default - This is now mostly a historic repository. In the beginning symbol and source uploads where done through a web form taking a regular ZIP file. Third-party uploads were rare so most of the time we just created those ZIP files ourselves and uploaded them to the Default repository. If there are any of you still refusing to jump on the package manager bandwagon, you can have us store symbols in that repository even today, e.g. for binaries published by some old-school method like a POZFWS (Plain Old Zip File on a Web Site). Maybe we'll even enable our old upload form again?

  • NuGet - This is where nuget.exe pushes to automatically, when it detects that a symbol package is present. Pushing is only possible if you are listed an owner of a given project on

  • OpenWrap - OpenWrap users claim wrap names colliding with NuGet packages, so there is a separate repository for this tool. You can push here directly, as there is no other central OpenWrap host available at the moment, no equivalent of

  • Chocolatey - as mentioned on one of our blogs, SymbolSource can be used not only for debugging libraries, but also actual applications. This repository syncs its permissions with Learn more about publishing debuggable open-source applications with Chocolatey and SymbolSource in this post: A world of debuggable open-source software – Part 3: Applications.

Private repositories and the permission model in detail

From the previous point you now know that SymbolSource can provide separate repositories and that some they can be associated with NuGet galleries like and to share permissions.

If you have an account on you can also create your own private repositories, which will be prefixed with your user name to make them unique. In that case you have total control over read and write access - you can grant those rights using our website to any other user of SymbolSource (or to the public user, which makes them available without authentication, exactly like all the repositories listed in the previous point.). You can create a private account at any time by filling out the registration form. Once logged in to SymbolSource, you can create a new private repository by going to the Metadata page.

With SymbolSource, permissions are tracked up to the level of a project (package) version, which means that you can let someone else only access stable releases, or even use SymbolSource as a secure means of distribution of libraries sold commercially.

Learn more about controlling permissions with the SymbolSource API

Integration with package galleries

When you publish symbol packages to our NuGet endpoint, which is, you are pushing to the Public instance and NuGet repository. You could also push to your own repository with an URL like this:, but be sure to create it on the website first.

Whereas a private repository is under your control, the NuGet repository is configured to verify permissions with on each upload - using the API key supplied by the user on the nuget.exe push command-line. You are only allowed to push if confirms that the API key belongs to an account listed as one of the package owners.

An interesting feature is that you don't even need to create an account on to push NuGet symbol packages - we'll create one for you automatically, but since we can't figure out your user name from the upload alone, and we won't ask to provide one for privacy reasons, this new account will have a generated name. At any time you are welcome to create a real account and associate your API key - we'll move all your previous uploads under the new account automatically. Registering gives you the additional benefits of reviewing upload reports for possible symbol issues and managing package versions.

After uploading a symbol package with NuGet and logging into SymbolSource you might notice that your package ownership is mirrored on the Authorization page. This allows you to browse upload reports for those projects, and also manage individual versions, by going to the NuGet repository and hiding or deleting them. Hiding is similar to's unlisting - it removes a version from public display, but still allows symbols to be downloaded with Visual Studio.

All of this also applies to and any other site based on the NuGet Gallery codebase - which can be associated with a private repository that you own, or any repository under a company account.

Integration with MyGet

Because is quite a different beast than, we also have a different integration model for it. To support multiple MyGet repositories, and a separate user base, SymbolSource hosts a MyGet company that is managed by using our API. Each MyGet user and repository automatically gets its counterpart on SymbolSource, so you don't need to do anything, apart from checking out MyGet Feed Details to discover what your push URL for symbol packages is and how to configure Visual Studio to download PDBs from your repositories. Your account's API key will enable you to push to both MyGet and SymbolSource, just as with NuGet.

You can also share MyGet symbol repositories with others - just add other people under MyGet Feed Security and our sync process will take care of the rest.

If you'd like to benefit from our website's features at the same time, just edit your MyGet Profile to set up and password and after a moment you'll be able to log into SymbolSource MyGet instance

There are already some prominent examples of public MyGet feeds making use of SymbolSource:

Company accounts in detail

A mentioned before, SymbolSource offers separate instances in a software-as-a-service model. These are also called company accounts and they can be created automatically by simply filling out a form.

Depending on the plan you choose, a company account will let you create even an unlimited number of arbitrarily named users and repositories. Soon we will also let you implement SSO with your own Active Directory infrastructure.

With a company account, all URLs contain its name instead of Public:

  • the website is at<company-name>
  • NuGet push URLs are at<company-name>/<repository-name>
  • NuGet package feeds are at<company-name>/<repository-name>/FeedService.mvc
  • OpenWrap repositories are at<company-name>/<repository-name>

Other integration possibilities

As you can see our data model is quite flexible, and the fact that all the endpoints (website, NuGet, OpenWrap) are build around our APIs gives us a lot of possibilities. For example, we've always liked the idea of commercial third-party library and component vendors enabling source access using our platform instead of downloadable ZIP files. Our APIs allow adjusting symbol and source access in real-time from any e-commerce platform controlling sales and licencing. Feel free to contact us if you find this idea interesting. We'll be happy to explain it further and help in deploying a solution.