Skip to content
Z Zendikt
Vendor trust scorecard

Weights and Biases vendor trust score

Trust scoring is the “is this vendor a fair counterparty” question, deliberately separated from product quality. Six dimensions, dated, sourced where events warrant it.

7.3
/10
mixed
Verdict

Weights and Biases's vendor trust profile is mixed. The dimension scores below show where to negotiate hard and what to monitor across a multi-year contract.

Vendor Trust Score

Is Weights and Biases a trustworthy vendor?

7.3/10
Mixed
Pricing transparency
Published rates; no hidden fees
7.5
Contract fairness
Reasonable terms; no auto-renew traps
7.5
Incident response
How they handle outages and breaches
8.0
Post-acquisition behavior
Customer treatment after M&A or PE
6.5
Executive stability
Leadership churn over 24 months
7.5
Roadmap honesty
Public commitments held
7.0
Trust signal log
  • 2024-05-14
    CoreWeave acquired Weights and Biases for a reported $1.7B
    Largest neutrality question in the MLOps category since the acquisition. CoreWeave is a GPU-cloud company; ML teams on AWS, GCP, Azure now weigh whether W and B remains genuinely neutral or quietly tilts toward CoreWeave compute over time.
  • 2024-11-12
    Roadmap continuity post-acquisition
    Customer-facing roadmap continues; some buyer reports of slower release cadence on non-acquisition-aligned features through late 2024 and into 2025.
  • 2025-04-22
    Renewal pricing crept up at large enterprises
    Several buyer reports of double-digit renewal increases through 2024 to 2025; consistent with broader post-acquisition pricing pattern.
Vendor Trust is scored independently of product quality. A great product from an unfair vendor still earns a low trust score.

How to read this score

  • Trust is separate from product quality. A vendor can ship great software and treat customers badly — or vice versa. We score the two independently.
  • 8.0+/10: strong. Few concerns at renewal or procurement.
  • 6.5–7.9: mixed. Negotiate hard on the lowest dimensions; monitor across the contract term.
  • 5.0–6.4: cautious. Add explicit mitigation language to the master agreement.
  • Below 5.0: concerning. Treat this as a contracted-risk evaluation, not a product-fit evaluation.
  • Updates: we re-verify scoring quarterly. Material trust events (acquisitions, breaches, leadership change, hostile contract terms) get logged on the timeline above.

Related editorial

Last updated 2026-05-10. Scoring methodology: editorial standards. Disagree? Tell us.