<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><id>https://sled.lighthouseadvisory.consulting/feeds/vast-data.xml</id><title>SLED AI Adoption Intelligence · VAST Data</title><link rel="self" type="application/atom+xml" href="https://sled.lighthouseadvisory.consulting/feeds/vast-data.xml"/><link rel="alternate" type="text/html" href="https://sled.lighthouseadvisory.consulting/streams/vast-data"/><updated>2026-11-11T05:16:08.918Z</updated><author><name>Lighthouse Advisory</name></author><entry><id>https://sled.lighthouseadvisory.consulting/streams/vast-data/editions/2026-11-10</id><title>VAST Data · Issue 06 · 2026-11-10</title><link rel="alternate" type="text/html" href="https://sled.lighthouseadvisory.consulting/streams/vast-data/editions/2026-11-10"/><updated>2026-11-11T05:16:08.918Z</updated><published>2026-11-10T00:00:00.000Z</published><summary>TACC&#39;s Horizon User Guide, updated November 10, documents that early users of the NSF Leadership-Class Computing Facility system at UT Austin work on a shared VAST file system for $HOME and $SCRATCH, without Lustre striping, with a 10-day unbacked scratch purge and a $WORK tier deferred to late 2026. TACC&#39;s October 28 report says Horizon has entered only its first phase of early operations as Frontera retires. For public research universities this is an operator design reference, not yet measured performance or reliability evidence.</summary><content type="text">TACC&#39;s Horizon User Guide, updated November 10, documents that early users of the NSF Leadership-Class Computing Facility system at UT Austin work on a shared VAST file system for $HOME and $SCRATCH, without Lustre striping, with a 10-day unbacked scratch purge and a $WORK tier deferred to late 2026. TACC&#39;s October 28 report says Horizon has entered only its first phase of early operations as Frontera retires. For public research universities this is an operator design reference, not yet measured performance or reliability evidence.

2 sources · 1 cross-source patterns

Horizon&#39;s VAST user file systems are in early operations, not yet production evidence
Before citing Horizon in a university or state research-computing storage decision, which measured early-user throughput, availability and migration results will TACC publish, and when will $WORK and production status arrive?</content></entry><entry><id>https://sled.lighthouseadvisory.consulting/streams/vast-data/editions/2026-11-05</id><title>VAST Data · Issue 05 · 2026-11-05</title><link rel="alternate" type="text/html" href="https://sled.lighthouseadvisory.consulting/streams/vast-data/editions/2026-11-05"/><updated>2026-11-06T11:55:44.271Z</updated><published>2026-11-05T00:00:00.000Z</published><summary>VAST Data&#39;s November 5 release claims more than $10 billion in FY2026 year-to-date commitments from 14 large customers and more than 200 exabytes of flash aligned through 2029, mentioning government organizations among planners. Same-day Blocks &amp; Files reporting qualifies the headline as aggregate commitments (software plus supporting hardware) rather than necessarily orders placed, notes there is no official top-10 frontier-lab ranking, and records VAST&#39;s statement that aligned capacity is allocated by advance commitments because demand exceeds supply. For SLED, the signal is supply-chain and procurement timing—not a measured agency or campus outcome.</summary><content type="text">VAST Data&#39;s November 5 release claims more than $10 billion in FY2026 year-to-date commitments from 14 large customers and more than 200 exabytes of flash aligned through 2029, mentioning government organizations among planners. Same-day Blocks &amp; Files reporting qualifies the headline as aggregate commitments (software plus supporting hardware) rather than necessarily orders placed, notes there is no official top-10 frontier-lab ranking, and records VAST&#39;s statement that aligned capacity is allocated by advance commitments because demand exceeds supply. For SLED, the signal is supply-chain and procurement timing—not a measured agency or campus outcome.

2 sources · 1 cross-source patterns

VAST&#39;s $10B demand signal is commitment-scale news that SLED buyers must qualify as delivery and allocation risk
For a state or university VAST expansion competing with hyperscaler demand, which written delivery dates, advance-commitment terms and shortage-allocation rules will gate award and acceptance?</content></entry><entry><id>https://sled.lighthouseadvisory.consulting/streams/vast-data/editions/2026-11-01</id><title>VAST Data · Issue 04 · 2026-11-01</title><link rel="alternate" type="text/html" href="https://sled.lighthouseadvisory.consulting/streams/vast-data/editions/2026-11-01"/><updated>2026-11-03T03:21:36.884Z</updated><published>2026-11-01T00:00:00.000Z</published><summary>Data infrastructure (limited SLED relevance): a VAST blog dated October 30 models its Kafka-compatible Event Broker on VAST on Cloud at $238,387 a month against $1.1 million for Confluent Cloud Enterprise at 4 GB/s with five-day retention. It is a vendor model with no customers named, and VAST concedes long retention can cost more. An earlier independent StorageMath analysis says VAST&#39;s Event Broker and uptime claims lack the methods needed to check them. No new U.S. state, local or education VAST deployment surfaced, and the CSCS evaluation remains inaccessible.</summary><content type="text">Data infrastructure (limited SLED relevance): a VAST blog dated October 30 models its Kafka-compatible Event Broker on VAST on Cloud at $238,387 a month against $1.1 million for Confluent Cloud Enterprise at 4 GB/s with five-day retention. It is a vendor model with no customers named, and VAST concedes long retention can cost more. An earlier independent StorageMath analysis says VAST&#39;s Event Broker and uptime claims lack the methods needed to check them. No new U.S. state, local or education VAST deployment surfaced, and the CSCS evaluation remains inaccessible.

2 sources · 1 cross-source patterns

VAST Event Broker cost and performance claims rest on vendor-only models; public buyers need their own workload baselines
Before an agency or university considers VAST Event Broker for telemetry or log streams, what measured workload profile, matched durability settings and contract pricing will it use to test VAST&#39;s cost and performance claims?</content></entry><entry><id>https://sled.lighthouseadvisory.consulting/streams/vast-data/editions/2026-10-31</id><title>VAST Data · Issue 03 · 2026-10-31</title><link rel="alternate" type="text/html" href="https://sled.lighthouseadvisory.consulting/streams/vast-data/editions/2026-10-31"/><updated>2026-11-02T01:20:58.168Z</updated><published>2026-10-31T00:00:00.000Z</published><summary>State and higher education: New York&#39;s Empire AI issued a vendor-neutral Gamma RFI on October 29 (up to 5 MW, about $160 million across two tranches) that records Beta&#39;s 20 PB of VAST storage and asks how new storage would interoperate with it, including across two sites, while its user guide says no data is backed up. Research computing: an LLNL study accepted at PDSW&#39;26 found VAST spared GPU communication from contention but still stalled 12% of training iterations. The CSCS evaluation remains inaccessible.</summary><content type="text">State and higher education: New York&#39;s Empire AI issued a vendor-neutral Gamma RFI on October 29 (up to 5 MW, about $160 million across two tranches) that records Beta&#39;s 20 PB of VAST storage and asks how new storage would interoperate with it, including across two sites, while its user guide says no data is backed up. Research computing: an LLNL study accepted at PDSW&#39;26 found VAST spared GPU communication from contention but still stalled 12% of training iterations. The CSCS evaluation remains inaccessible.

2 sources · 1 cross-source patterns

Public AI compute buyers need measured storage-path evidence, not rated VAST capacity or throughput
For a public AI cluster extending or adding VAST storage, which representative-workload tests of tail latency, fabric placement, cross-site access and restore will gate acceptance?</content></entry><entry><id>https://sled.lighthouseadvisory.consulting/streams/vast-data/editions/2026-10-30</id><title>VAST Data · Issue 02 · 2026-10-30</title><link rel="alternate" type="text/html" href="https://sled.lighthouseadvisory.consulting/streams/vast-data/editions/2026-10-30"/><updated>2026-10-31T04:40:20.360Z</updated><published>2026-10-30T00:00:00.000Z</published><summary>State and higher education: the Massachusetts AI Hub&#39;s state-funded AICR cluster runs on about 14.3 PiB of VAST all-flash storage with encryption at rest, but its operator documents snapshot-only protection, no off-site backups and Beta status, with no published performance outcomes. Health and human services: a VAST blog maps encryption, retention locks, WORM and immutable snapshots to HIPAA; it is a vendor feature claim, and HHS&#39;s Security Rule overhaul is now projected for July 2027. The CSCS independent evaluation remains inaccessible.</summary><content type="text">State and higher education: the Massachusetts AI Hub&#39;s state-funded AICR cluster runs on about 14.3 PiB of VAST all-flash storage with encryption at rest, but its operator documents snapshot-only protection, no off-site backups and Beta status, with no published performance outcomes. Health and human services: a VAST blog maps encryption, retention locks, WORM and immutable snapshots to HIPAA; it is a vendor feature claim, and HHS&#39;s Security Rule overhaul is now projected for July 2027. The CSCS independent evaluation remains inaccessible.

2 sources · 1 cross-source patterns

VAST data-protection outcomes depend on operator configuration and policy, not the platform alone
For a VAST-based public AI or ePHI data store, which protections are actually enabled, who owns keys and backups, and has recovery been tested?</content></entry><entry><id>https://sled.lighthouseadvisory.consulting/streams/vast-data/editions/2026-10-29</id><title>VAST Data · Issue 01 · 2026-10-29</title><link rel="alternate" type="text/html" href="https://sled.lighthouseadvisory.consulting/streams/vast-data/editions/2026-10-29"/><updated>2026-10-30T03:21:45.629Z</updated><published>2026-10-29T00:00:00.000Z</published><summary>First VAST Data edition. Higher-ed research computing: Georgia Tech&#39;s NSF-funded Nexus opened on an eight-appliance VAST all-flash layer, though it was pre-production and public specs conflict. Agentic AI: VAST and NVIDIA announced an Agent Sandbox Foundation Stack claiming durable agent records, while independent research on the underlying OpenShell runtime shows exfiltration through permitted egress. Sovereign inference: VAST and Hyperfusion plan containerized, air-gapped units, with validation incomplete. No U.S. state/local government VAST evidence surfaced; the CSCS independent evaluation could not be accessed.</summary><content type="text">First VAST Data edition. Higher-ed research computing: Georgia Tech&#39;s NSF-funded Nexus opened on an eight-appliance VAST all-flash layer, though it was pre-production and public specs conflict. Agentic AI: VAST and NVIDIA announced an Agent Sandbox Foundation Stack claiming durable agent records, while independent research on the underlying OpenShell runtime shows exfiltration through permitted egress. Sovereign inference: VAST and Hyperfusion plan containerized, air-gapped units, with validation incomplete. No U.S. state/local government VAST evidence surfaced; the CSCS independent evaluation could not be accessed.

4 sources · 1 cross-source patterns

Agent-sandbox persistence and audit claims need independent security verification
Before an agency or university pilots sandboxed agents on VAST, how will it prove that every agent action is recorded and that allowed tools cannot exfiltrate data?</content></entry></feed>