jain.com

Backblaze storage partnership

Company: CoreWeave

Subject kind
partnership
Statement date
2026-08-21
Promised amount
335.0 USD
Current status
stated

The claim, verbatim

CoreWeave signed a five-year, $335 million agreement with Backblaze for multi-exabyte storage capacity to support CoreWeave's managed storage infrastructure

Source (primary)

BLZE Stock On Track For Its Best Day Since March 2024 – ‘Game-Changing’ CoreWeave Deal Sparks Analyst Upgrades - Stocktwits (-, news_article)
View cached copy (2026-09-01)Live source ↗

Quote: “A five-year, $335 million deal with CoreWeave has put Backblaze in the spotlight, where the company aims to provide cost-efficient storage capacity that supports portions of CoreWeave's managed storage infrastructure.”

How we checked this

This claim has not yet been checked assertion-by-assertion against its source. It carries a cited source and quote, but the deeper check has not run. When it does, the result appears here whatever it says.

Additional evidence

confirms BLZE Stock On Track For Its Best Day Since March 2024 – ‘Game-Changing’ CoreWeave Deal Sparks Analyst Upgrades - Stocktwits

Quote: “A five-year, $335 million deal with CoreWeave has put Backblaze in the spotlight, where the company aims to provide cost-efficient storage capacity that supports portions of CoreWeave's managed storage infrastructure.”

View cached copy (2026-09-01)Live source ↗

Record of changes

September 1, 2026 — statedlater found incorrect
Automated extraction from the cited source. Recorded automatically from the cited source when it was published, then queued for evidence review.
September 1, 2026 — withdrawnlater found incorrect
Evidence review against the cited source. The source confirms the five-year, $335 million agreement and infrastructure support, but does not specify the storage capacity as 'multi-exabyte,' a key detail in the jain.com claim.
September 2, 2026 — stated
Correction after re-verification. Re-verification found the cited source does support this claim. The earlier withdrawal was made in error and has been reversed. The attributed quote appears verbatim in the cited source (deterministic check).