MyGet
Repository management software
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if MyGet and its alternatives fit your requirements.
$15 per month
Free TrialFree version
Small
Medium
Large
- Information technology and software
- Banking and insurance
- Media and communications
What is MyGet
MyGet is a hosted package repository service used to store, proxy, and distribute software packages and build artifacts. It is commonly used by development teams to manage private feeds for package formats such as NuGet and npm and to support CI/CD workflows. The product focuses on feed-based repository management with access controls and upstream sources to centralize dependency consumption and internal package publishing.
Multi-format package feed support
MyGet supports multiple package ecosystems (commonly including NuGet and npm) under a feed-based model. This helps teams standardize how they publish and consume internal packages across projects. It also reduces the need to run separate repository tools for each package type in smaller environments.
Upstream proxy and caching
MyGet can proxy upstream public registries and cache dependencies in a controlled feed. This supports repeatable builds and can reduce external dependency on public endpoints during CI runs. It also provides a single place to apply access policies for dependency consumption.
Access controls for private feeds
MyGet provides private feeds with authentication and permissions to control who can publish and download packages. This fits common enterprise needs for internal libraries and pre-release distribution. Teams can separate feeds by environment or project to limit blast radius and simplify governance.
Hosted-service dependency
MyGet is primarily delivered as a hosted service, which can be a constraint for organizations that require fully on-premises or air-gapped deployments. Network connectivity and service availability become part of the build and release dependency chain. Some regulated environments may require additional vendor due diligence and contractual controls.
Feature depth varies by format
Repository capabilities can differ by package type (for example, metadata handling, retention policies, or advanced promotion workflows). Teams with complex artifact lifecycle requirements may need to validate parity across all formats they use. Advanced enterprise features found in broader artifact platforms may require workarounds or complementary tooling.
Ecosystem and roadmap uncertainty
MyGet has had periods of reduced visibility compared with larger, more broadly adopted artifact repository platforms. For long-term standardization, buyers may need to confirm current product status, support model, and roadmap commitments. This can increase procurement effort for organizations seeking a strategic, multi-year platform decision.
Plan & Pricing
| Plan | Price | Key features & notes |
|---|---|---|
| Open Source (OSS) | Free | Public & community feeds only; 1 GB storage; max package size 100 MB; includes Build Services and Symbols Services; subscription valid 1 year (renewable) — available to qualifying non-commercial open-source projects. |
| Developer | $15/month ($165/year) | 1 private feed; 1 private contributor; 500 MB storage; 500 MB max package; 0 build minutes; shared infrastructure. |
| Team | $40/month ($440/year) | 5 private feeds; 5 private contributors; 2 GB storage; 1 GB max package; 600 build minutes; Build Services, License Governance, Vulnerability Management, Custom Package Retention. |
| Enterprise | Starts at $1,395/year | Unlimited private feeds; starts at 10 users (client access licenses); starts at 4 GB storage; starts at 1000 build minutes; dedicated Azure infrastructure; custom branding and subdomain; data localization (EU or US); billed via invoice or credit card; contact sales for tailored pricing. |
Seller details
MyGet
Leuven, Belgium
2011
Private
https://www.myget.org/
https://x.com/MyGetTeam
https://www.linkedin.com/company/myget
