Number of Seats/Users: MyGet offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows MyGet that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from MyGet. MyGet reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: MyGet offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from MyGet. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: MyGet often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that MyGet is generally seen as a strong, developer-friendly choice, but with some cost-structure and reliability concerns that are very relevant from a savings perspective.

What Spendbase clients like most
– Easy onboarding:
– Fast to set up private feeds, especially for NuGet.
– Straightforward integration with CI/CD pipelines.
– Broad tech coverage:
– Supports multiple ecosystems (NuGet, npm, Maven, Python, etc.), which helps consolidate tools and reduce tooling sprawl.
– Real productivity gains:
– Centralized, consistent package versions across dev, QA, and clients.
– Good fit for distributed teams and reusable libraries.
– Helpful for caching dependencies and mitigating security/supply-chain risks.
– Perceived value:
– Many clients call it “cost effective” vs other options when they actually use the multi-ecosystem capabilities.

Key friction points (and where overspend often hides)
– Pricing and plans:
– Some clients only need a private NuGet feed but pay for a “universal” feature set they rarely use.
– Newer plans reportedly offer less storage for similar money.
– Multiple comments ask for more flexible or per‑user pricing.
– Reliability and risk:
– While several clients say “never had issues”, others report major outages that stalled development.
– This creates hidden costs: downtime, delays, and the need for backup solutions (e.g., on‑prem mirrors).
– Usability gaps:
– UI called “dated” or visually unappealing by some.
– Navigation and permissions/auth setup can be confusing initially.
– Documentation and plugins are not always up to date (e.g., issues with newer Visual Studio versions).
– Feature gaps / wishlist:
– Docker registry support.
– Better package retention rules and dependency management (especially deep dependency chains).
– Upstream sources, events, improved search/overview, optional on‑prem active backup.

How Spendbase typically acts on this
– Identify if teams are:
– Paying for multi-language support but only using NuGet.
– Buying more storage than needed or sitting on legacy plans.
– Maintaining parallel backup solutions because of outage concerns.
– Then we:
– Renegotiate to a more appropriate tier or feature set.
– Benchmark MyGet vs alternative tooling already present (e.g., Azure DevOps feeds) to avoid double spend.

Net: MyGet can be high value when matched correctly to usage; the main savings opportunity is right‑sizing plans and eliminating paid, unused capability.