Number of Seats/Users: Comet 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 Comet 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 Comet. Comet reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Comet 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 Comet. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Comet 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 Comet is generally well liked by our clients, but it also triggers serious cost and usability discussions in ML teams.

Overall sentiment:
– Average satisfaction sits around “good to very good” (mostly 4–5 stars).
– The platform clearly delivers value in experiment tracking and collaboration, but price and scaling issues often become decision points.

Key strengths Spendbase clients highlight:
– Easy integration & setup
– Works smoothly with major ML frameworks (PyTorch, TensorFlow, Keras, scikit-learn).
– Simple logging calls (log_metric, log_asset) give rich visualizations with little boilerplate.
– Strong experiment tracking
– Centralized tracking for metrics, assets, and model versions.
– Great for replacing local tracking and making runs reproducible.
– Powerful visualization & panels
– Panels and reports help compare hyperparameters, performance, and embed multiple views.
– Community panels and plotting tools are noted as especially useful.
– Collaboration benefits
– Handy for teams and academic groups who need to share experiments and grading.
– Remote access from any device is seen as a plus.

Main pain points our clients report:
– Cost & licensing
– Multiple teams are reconsidering Comet purely due to rising license costs.
– Academic plans feel restrictive because of limited team size.
– Lack of a free trial is seen as a barrier for new adopters.
– Scale & performance issues
– UI slows down with large numbers of experiments.
– Hard to manage and organize many old trials and views.
– File and model limits
– Errors with large file uploads and hassles when saving big models.
– Usability & learning curve
– Steep initial learning curve for some.
– Confusing custom views and panels; accessibility could be improved.
– Docs & feature parity
– Documentation called “okay but improvable.”
– Gaps between Python SDK capabilities and what’s exposed in the UI (e.g., model registry automation).

From a Spendbase discount perspective, Comet delivers strong technical value, but cost optimization, license right-sizing, and negotiating better terms are critical to keeping it in the stack for many ML teams.