Quickstart

This guide takes you from a new account to a package available on your own private feed. You will need the .NET SDK installed and a .nupkg file to push. If you do not have one yet, run dotnet pack in any class library project.

1. Create your publisher account

Head to the publisher page and sign up. Accounts are free, and you can publish private packages for your own team without ever connecting a payment provider.

2. Create a product

A product is the container for everything you distribute. From your dashboard, choose New product and pick two short identifiers:

• Publisher slug: your namespace, for example acme.
• Product slug: the product name, for example toolkit.

Together these form the path in your feed URL. Choose them carefully: they appear in every command your users run.

3. Add a feed

Inside your product, add a NuGet feed. For an internal package you share with your own team, a private feed is the simplest choice. If you plan to sell access, create a marketplace feed instead. The difference is explained in Creating a feed.

4. Generate a push key

A push key authorizes uploads to your feed. Generate one from the feed management page and copy it somewhere safe. Treat it like a password: anyone with the key can publish to your feed.

5. Push your package

Use the standard dotnet nuget push command, pointing at your feed and passing your push key as the API key:

dotnet nuget push Toolkit.1.0.0.nupkg \
  --source https://www.pkgstore.io/api/nuget/acme/toolkit \
  --api-key YOUR_PUSH_KEY

Replace acme/toolkit with your own publisher and product slugs. Once the upload finishes, the package appears on your product page with its version and download count.

6. What is next

• Have someone install your package? Point them at Consuming a feed.
• Want to sell access? Set up Pricing and payments.
• Need to control who gets in? Read Managing access.