Editions & features
NuGetKeep is open-core. The server runs in one of three editions depending on which license key (if any) is present at startup. Team and Enterprise are ordered by scope of use rather than by feature count alone: Team secures one team’s feed; Enterprise runs an organisation’s package platform. Scoped API keys and multiple isolated feeds are what an organisation needs once several teams coexist — everything else in Enterprise is already in Team.
| Feature | Community (free) | Team (licensed) | Enterprise (licensed) |
|---|---|---|---|
| v3 protocol — restore, push, unlist | ✓ | ✓ | ✓ |
| OIDC/SSO login + RBAC | ✓ | ✓ | ✓ |
| Basic (unscoped) API keys | ✓ | ✓ | ✓ |
| Single feed | ✓ | ✓ | ✓ |
| Vulnerability quarantine (OSV scan gate) | — | ✓ | ✓ |
| Trusted publishing (keyless OIDC push) | — | ✓ | ✓ |
MCP tools endpoint (/mcp) | — | ✓ | ✓ |
| Scoped API keys (package-pattern / operation restrictions) | — | — | ✓ |
| Multiple feeds | — | — | ✓ |
No seat or developer cap on either paid edition — licenses are ECDSA-signed and validated offline, flat rate, one server.
When no valid license is present (absent, expired, or tampered) the server boots as Community
edition: all five premium features refuse to operate, and a WARNING log line at startup
enumerates each of them. A Team license unlocks three of the five (vulnerability quarantine,
trusted publishing, MCP); the remaining two (scoped API keys, multiple feeds) stay locked, and
the same startup WARNING enumerates just those.
Ready to upgrade? See Buying & applying a license.