From the VAST Data edition of November 5, 2026
Blocks & Files qualifies VAST's $10B figure as commitments not necessarily orders, and records allocation-by-commitment under flash shortage
Blocks & Files (Chris Mellor) · Independent storage industry reporting · Global coverage (UK-based publication; U.S. vendor subject)
- Publisher
- Blocks & Files
- Original publication
- 2026-11-05
- Source retrieved
- 2026-11-06
- Event date
- 2026-11-05
What happened
Same-day Blocks & Files coverage restates VAST's 14-customer / $10B / 200 EB claims, then qualifies them: the fiscal window is February 1–October 31, 2026; the $10B is aggregate commitments for software and supporting hardware rather than necessarily orders already placed; there is no official top-10 frontier-lab ranking; 'significant percentage' of enterprise NAND is undefined (editor suggests 2–5% as a possible floor); and a VAST spokesperson said demand exceeds supply so aligned capacity is allocated by customers' advance commitments and delivery schedules, not an unlimited guarantee. The piece also sketches forward supply planning with SSD partners without per-order triggers.
Why it matters
Directly useful for SLED procurement and research-computing planning: independent reporting confirms that even VAST's aligned flash is commitment-gated under shortage, so state and university projects should negotiate delivery schedules explicitly and not assume retail SSD availability. Still not a SLED deployment evaluation.
Evidence and measured results
Opened full article HTML (published thu 5 Nov 2026 // 14:00 UTC). Qualifications appear in bootnote and spokesperson quote; editor commentary on NAND percentage and historical-precedent credibility is clearly labeled as the publication's reckoning. Not a lab benchmark or audit.
Limitations and uncertainty
Trade press, not a formal audit; some hypothetical supplier dialogue is illustrative. Author has previously been criticized by StorageMath for amplifying VAST claims, so read qualifications carefully but do not treat the article as adversarial research.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-05; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Buyers hear a $10B demand signal but need to know what is committed versus shipped and how shortage allocation works.
- Stakeholders
- Procurement officers
- Research computing directors
- Reseller storage specialists
- Finance / budget owners
- Discovery questions
- Is the quoted capacity a commitment, a purchase order or installed?
- What delivery schedule and allocation priority attach to our advance commitment?
- What happens if SSD partners miss the planned EB mix?
- Value hypothesis
- Clear commitment-versus-order language reduces procurement risk when competing with hyperscaler demand; hypothesis drawn from the article's qualifications, not a measured outcome.
- Potential engagement
- Help a SLED buyer draft delivery and allocation clauses informed by the spokesperson's shortage qualification.
- Unsupported claims
- That Blocks & Files independently verified the $10B total
- Guaranteed supply for public-sector orders
- Any performance comparison versus Everpure/NetApp/Dell
Pre-sales engineering
Role takeaway
- Fit
- Applies when engineering must forecast VAST capacity under industry flash constraints.
- Architecture and integration
- Forward planning is with SSD and JBOF partners on product-family EB views; integrate supplier lead-time assumptions into BOM and staging plans.
- Prerequisites
- Advance commitment and required delivery schedule
- SSD product-family forecast from VAST/partners
- Fallback capacity plan
- Constraints
- Demand exceeds available supply (VAST spokesperson)
- No unlimited availability guarantee
- Undefined NAND market-share claim
- Security
- Not covered; keep separate from supply-chain discussion.
- Proof of value
- Contractual delivery dates with remedies
- Visibility into allocation queue position
- Do not accept 'significant percentage of NAND' without a defined metric
Delivery
Role takeaway
- Work
- Build a schedule that separates commitment, order placement, SSD delivery and cluster acceptance.
- Dependencies
- NAND/SSD partner build plans
- Customer advance commitment
- Site readiness
- Ownership
- Program manager jointly with vendor supply-chain contact.
- Skills and adoption
- Teams need commercial literacy on commitments vs orders plus classic storage ops skills.
- Governance checkpoints
- Commitment paperwork complete
- Mid-lead-time supplier confirmation
- Pre-acceptance delivery audit
- Acceptance criteria
- Proposed: shipped usable capacity matches contract by date
- Proposed: written allocation rule under continued shortage
- Proposed: no go-live until hardware on floor and burned in
- Risks
- Treating commitments as installed capacity
- Public projects deprioritized versus larger committers
- Illustrative supplier examples misread as contractual mechanics
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Reinforces that architecture timelines for VAST expansions must include NAND/SSD partner lead times and commitment-based allocation; no change to DASE/CNode design from this article.
Governance
Who approves, reviews and stays accountable for outcomes?
Buyers should document whether a purchase is a commitment, an order or installed capacity—terms VAST's marketing conflates. Require disclosure of allocation priority rules in contracts.
Security and privacy
What data, permissions and controls need testing?
None discussed.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
None stated.
Procurement
What should contracts, pricing and exit terms secure?
Independent reporting warns that aligned capacity is allocated by advance commitments under shortage—SLED solicitations should require delivery schedules, allocation priority and remedies, and should distinguish commitments from purchase orders in evaluation language.
Operating model
Which teams own the service once it runs?
Operating model for VAST-powered sites increasingly includes multi-quarter supply planning with the vendor, not only day-2 storage administration.
Publication history
- 2026-11-05VAST Data · Issue 052 resources
Stable resource ID: blocksandfiles-vast-10b-commitments-vs-orders-20261105