Feeds
A feed is a separate package source inside one PaGetto server. Each feed has its own packages, its own settings (overwrites, deletion, retention, size limit, read-only mode), its own read-through mirror and its own permissions. Use feeds to keep, for example, internal packages apart from experimental ones, or to give each team a mirror of nuget.org with different rules.
Every feed has a type, the kind of packages it serves: NuGet, Dart, npm, Maven, Python, Rust, Go, Ruby, Hex, PHP, CocoaPods, Swift or R. This page describes NuGet feeds and what all feeds share; Dart and Flutter packages covers Dart feeds, npm packages npm feeds, Maven packages Maven feeds, Python packages Python feeds, Rust crates Rust feeds, Go modules Go feeds, Ruby gems Ruby feeds, Hex packages Hex feeds, PHP packages PHP feeds, CocoaPods pods CocoaPods feeds, Swift packages Swift feeds and R packages R feeds.
Feed URLs​
Every feed has a slug, and its NuGet v3 endpoints live under /feeds/{slug}/:
| Feed | Service index |
|---|---|
Default feed (slug default) | https://your-server/v3/index.json |
Any other feed, e.g. internal | https://your-server/feeds/internal/v3/index.json |
All endpoints (search, registrations, package content, push, delete, symbols) work under the feed prefix, so a client only needs the service index URL. The web UI works the same way: https://your-server/feeds/internal/ lists that feed's packages.
The default feed is created on first start and can't be deleted. Its URLs are the ones PaGetto has always used, so clients configured before multi-feed support keep working.
Managing feeds​
Feeds are managed by administrators on Admin > Feeds. This needs Authentication:Mode set to Local, Entra or Hybrid (see Authentication). The Legacy mode has no administrators, so only the default feed exists.
- Create a feed with New feed: a slug, a type, a display name (at most 256 characters) and an optional description (at most 4000 characters). A slug is lowercase letters, digits and hyphens, can't start or end with a hyphen, and is at most 128 characters. It becomes part of the URL, so choose it with care. The type (NuGet, Dart, npm, Maven, Python, Rust, Go, Ruby, Hex, PHP, CocoaPods, Swift or R) can't be changed afterwards either.
- Reorder feeds by dragging them. The order is used wherever feeds are listed in the UI.
- Open a feed's Settings to change its display name, description and settings.
- Delete a feed with its trash button. This deletes all of its packages from the database and storage. It can't be undone.
There is also a small JSON API at /api/v1/feeds. It only accepts the web UI's sign-in cookie, so it is meant for administrators signed in to the web UI; personal access tokens and Basic auth don't work there.
| Request | Effect |
|---|---|
GET /api/v1/feeds, GET /api/v1/feeds/{slug} | List all feeds, or get one |
POST /api/v1/feeds | Create a feed from slug, name, description and type ("NuGet", the default, "Pub" for a Dart feed, "Npm" for an npm feed, "Maven" for a Maven feed, "PyPI" for a Python feed, "Cargo" for a Rust feed, "Go" for a Go feed, "RubyGems" for a Ruby feed, "Hex" for a Hex feed, "Composer" for a PHP feed, "CocoaPods" for a CocoaPods feed, "Swift" for a Swift feed or "Cran" for an R feed) |
PUT /api/v1/feeds/{slug} | Change only the name and description |
DELETE /api/v1/feeds/{slug} | Delete the feed and its packages. The default feed returns 409 Conflict |
Settings, mirrors and the feed order can only be changed in the web UI. Changes made through the API are not written to the audit log.
Feed settings​
Open Admin > Feeds > Settings for a feed (/Admin/Feeds/{slug}/Settings). Each setting has a Use global default checkbox: while it is checked, the feed follows the value from configuration; uncheck it to override the value for this feed only.

| Setting | Global setting | Description |
|---|---|---|
| Read-only mode | IsReadOnlyMode | Reject pushes, unlists, deletes and relists on this feed, from NuGet clients and from the web UI |
| Package overwrite policy | AllowPackageOverwrites | Disallow (recommended), prerelease only, or allow all. See package overwrites. |
| Deletion behavior (NuGet feeds) | PackageDeletionBehavior | Unlist (recommended) or hard delete. See hard deletions. |
| Max package size (MiB) | MaxPackageSizeMiB | Largest package or symbol package this feed accepts, at least 1 MiB. It can only lower the global value, which caps every request; larger pushes get 413 Payload Too Large |
| Retention (NuGet feeds) | Retention | How many major versions, minor versions per major, patch versions per minor and prerelease versions per patch to keep, each 0 or more. 0 keeps none of them except the version being pushed. An override left empty falls back to the global value. Prereleases of older majors deletes prereleases below the latest stable major (DeletePrereleasesOfOlderMajors). See auto-deletion. |
| Upstream listing cache (seconds) | UpstreamListingCacheSeconds | How long mirrored version lists are reused before asking the upstreams again. See upstream listing cache. |
Set the values you want for most feeds in configuration, and override only where a feed differs. Changing a global value then updates every feed that still uses the default.
Mirror (read-through cache)​
A NuGet feed can mirror an upstream NuGet feed, for example nuget.org (a Dart feed mirrors pub servers such as pub.dev, see Mirror pub.dev, an npm feed npm registries, see Mirror registry.npmjs.org, a Maven feed Maven repositories, see Mirror Maven Central, a Python feed package indexes, see Mirror PyPI, a Rust feed sparse registries, see Mirror crates.io, a Go feed module proxies, see Mirror proxy.golang.org, a Ruby feed gem servers, see Mirror rubygems.org, a Hex feed Hex repositories, see Mirror hex.pm, a PHP feed Composer repositories, see Mirror Packagist, a CocoaPods feed spec repositories, see Mirror cdn.cocoapods.org, a Swift feed Swift package registries, see Mirror another registry, and an R feed CRAN-like repositories, see Mirror CRAN). When a client asks the feed for a package it doesn't have, PaGetto fetches it from the upstream source, stores it in the feed and serves it. Later restores are served locally, which speeds up builds and keeps them working when the upstream is unreachable.
Mirrors are listed on each feed's settings page, under Mirrors. Use Add mirror to add one; each mirror has these settings:
| Setting | Description |
|---|---|
| Enabled | Use this mirror. Clear it to pause a mirror without losing its settings |
| Package source URL | The upstream service index, e.g. https://api.nuget.org/v3/index.json. Must be an absolute http or https URL |
| Use NuGet V2 (legacy) protocol | For upstream servers that only speak the V2 protocol |
| Download timeout (seconds) | How long to wait for an upstream download, at least 1. Leave it empty for the default of 600 seconds |
| Authentication | None, Basic (username and password), Bearer token or Custom headers (JSON, e.g. {"X-Api-Key":"value"}) |
Password and token fields are write-only: leave them blank to keep the stored value.
Custom headers must be a JSON object. The headers Authorization, Cookie, Host, Content-Length, Transfer-Encoding, Connection, Upgrade, Proxy-Authorization and Set-Cookie are refused; use Basic or Bearer authentication instead of an Authorization header. If any value on the settings page is invalid, nothing is saved. Changes to a mirror's password or token are written to the audit log as feed_mirror_credentials_changed.

Upstream credentials are stored in the PaGetto database. Restrict access to the database and its backups, and use a read-only token for the upstream feed where possible.