Long Drive
My Files
← Back to blog

AI's Power Problem Is Also a Data Persistence Problem

9/18/2026Long Drive Editorial

NVIDIA, Google, and startup Emerald AI have formed the Alliance for Energy Management in AI (AEMA), with Anthropic joining. The goal: make data centers dynamically adjust power consumption based on grid conditions. This isn't just an energy story—it's a reminder that digital infrastructure is constrained by physics, and that data persistence has a cost.

The grid is the new bottleneck

AI's appetite for compute has collided with the physical limits of electricity grids. In many regions, interconnection queues stretch for years, and local opposition to new data centers is growing over concerns about rate hikes. AEMA's premise is simple: instead of building for peak demand, make workloads flexible. Shift training jobs to when renewable energy is abundant, or throttle inference during grid stress. Emerald AI's software orchestrates this, and NVIDIA and Google bring hardware and cloud-scale data.

The alliance matters because it acknowledges a hard truth: you can't just add more GPUs. Power delivery, not chip supply, is becoming the binding constraint. That has implications beyond AI. Every always-on service—including cloud storage—depends on continuous power and cooling. The more we treat data as something that must be instantly available forever, the more we strain the grid.

Flexibility vs. permanence

AEMA's approach optimizes for flexibility: compute that can move, pause, or scale down. But not all data workloads are flexible. A training job can wait; a medical record or a legal contract cannot. The alliance's model works for batch processing, but it doesn't solve the problem of data that must persist indefinitely.

This is where the economics of storage get interesting. Traditional cloud storage is a subscription: you pay monthly, forever, and if you stop paying, your data disappears. That model aligns with flexible compute—it's easy to scale down. But it also means your data's existence is contingent on an ongoing billing relationship. For archives, that's a fragile foundation.

A different model is prepaid, permanent storage. Arweave, for example, uses a one-time fee to store data across a decentralized network, with the endowment covering future costs. Long Drive, built on Arweave and operated by Supercomputing International (Hong Kong), applies this to a cloud drive: upload once, and the data is stored permanently. No recurring subscription, no risk of deletion if you forget to pay. For corporate archives or family photos, that's a meaningful shift.

The hidden cost of "always on"

Data centers are not just power hogs; they are also cooling challenges. The International Energy Agency estimates that data centers consumed about 1.5% of global electricity in 2022, and that figure is expected to rise with AI. AEMA's flexibility helps, but it doesn't change the fundamental demand for storage that never sleeps.

Consider the lifecycle of a typical cloud file. It sits on replicated disks, backed up, indexed, and served through always-on infrastructure. Even cold storage requires power for spinning disks or periodic checks. The cost is continuous, and so is the environmental footprint. Permanent storage on a decentralized network doesn't eliminate that footprint, but it changes the incentive: you pay once, and the network's endowment manages long-term costs. It's a different way to think about durability—not as a service you rent, but as an asset you own.

What this means for long-term data

The AEMA alliance is a signal that the AI boom is forcing a reckoning with infrastructure limits. Flexibility will help, but it won't make data disappear. The real question is how we store the data that must outlive us—contracts, research, family histories—without tying it to an endless subscription or a single company's balance sheet.

That's the problem Long Drive is built around. It's not about faster access or more features; it's about a simple promise: upload once, and the data stays. On a grid-constrained planet, that kind of permanence is not just convenient—it's a different design philosophy. One where storage is an endpoint, not a recurring line item.