Concepts

Organisation

An organisation is the top-level container for everything in Feedz. It holds your repositories, members, teams, and billing. You create one organisation when you sign up. An organisation has a unique slug that appears in all your repository URLs:

https://f.feedz.io/{organisation}/{repository}/...

Repository

A repository is a private package registry that can hold packages across multiple formats — NuGet, npm, Chocolatey, symbols, and generic files. You can have as many repositories as you need. Each repository has its own URL, access settings, and optional configuration such as upstream sources and retention policies.

Member

A member is a person who belongs to your organisation. Members sign in via the Feedz portal and can interact with repositories according to the permissions granted by their teams. See Members.

Service account

A service account is a non-human identity for applications, build servers, and CI/CD pipelines. Service accounts authenticate with access tokens only - they cannot log in to the portal. Use service accounts for any automated access so that pipelines are not tied to an individual's account. See Service Accounts.

Team

A team groups members and service accounts together and defines their permissions. Teams control which repositories a member can see and what actions they can perform. A member's effective permissions are the union of all their teams' permissions. See Teams.

Personal access token

A personal access token (PAT) is a credential used to authenticate against Feedz APIs, NuGet clients, and the npm CLI. Tokens are tied to a specific account and can be scoped (read-only, write, or full API), given an expiry date, and deactivated at any time. See Personal Access Tokens.

Upstream source

Upstreams connect a repository to another package source. There are two types:

• Internal upstreams — link to another repository within the same organisation. Packages from the upstream appear alongside your own, letting you split or combine repositories while keeping each feed URL simple.
• External upstreams — link to a feed outside Feedz (e.g. nuget.org). Individual packages can be pushed out to that feed directly from the package details page.

See Upstream Sources for configuration details.

Retention policy

A retention policy automatically removes old package versions from a repository based on rules you define - for example, keep only the 10 most recent versions of each package, or delete anything older than 90 days. Policies run when a new package is uploaded. See Retention Policies.

Delta compression

Delta compression transfers only the differences between two versions of a package rather than the full file. This can significantly reduce download sizes for packages that change incrementally. It is supported by the Feedz CLI and C# SDK. See Delta Compression.

Custom domain

A custom domain maps your own hostname to a Feedz repository, so clients see packages.yourcompany.com instead of a feedz.io URL. Available on the Professional plan. See Custom Domains.