Thoughts on the Indensity Release
Reactions to the Indensity announcement have ranged from exuberance to outright disappointment. As usual, I think the truth sits somewhere in the middle.
For those of us who follow EOS closely, this was not a technical surprise. Indensity is largely a system-level evolution built on the same proven Z3 platform, not a new chemistry. At the same time, it did need to be formally released to the market. Products don’t really exist until customers, EPCs, regulators, and procurement teams can point to a name, a configuration, and a clear use case.
Whether there was too much or too little hype leading into the announcement is debatable. Through the lens of long-time followers who track every EOS move, expectations were clearly elevated. That said, I thought the launch video itself was very well done. Joe and Francis were polished and clear in their delivery. The one thing I would have liked to see was a short follow-on deep dive - 15 or 20 minutes - explicitly walking through the target customer for Indensity, and clarifying whether it was intended to replace the Cube or augment EOS’s lineup. Leaving that to speculation is what created much of the reaction we’re seeing.
That aside, this post isn’t about communications style. It’s about the product lineup - and specifically the assumption many people seem to be making that Indensity replaces the Cube.
I don’t think that’s the case.
My view is that Indensity is an addition to the product lineup, not a replacement. Time will tell, of course, but I believe the Cube remains highly attractive to utility-scale customers, particularly public utilities. There are several reasons for this.
First, public utilities operate under multi-year capital investment plans that are reviewed and approved by state public utility commissions. These investments ultimately flow through to rates paid by customers and are subject to formal regulatory processes, hearings, and approvals. Unlike private companies, public utilities cannot easily “add on” or reconfigure systems over time without triggering additional review. As a result, flexibility in the form of modular, expandable “lego-style” systems is not especially valuable to them. Predictability, standardization, and pre-approved configurations matter far more.
Second, density is not free.
Packing significantly more energy into a smaller footprint - with integrated racking, power management, onboard cooling, software, and vertical scalability - almost certainly comes at a higher installed cost on a per-kWh basis compared to a more traditional Cube deployment. That’s true not just at the R&D level, but at the product and installation level as well. Higher integration, tighter tolerances, and vertical designs generally trade off lowest possible $/kWh in favor of siting flexibility and speed.
That trade-off makes perfect sense for the right customer.
Indensity appears purpose-built for private enterprises operating in dense urban or suburban environments where land is scarce, permitting is difficult, and proximity to load matters. Think data centers, mission-critical infrastructure, industrial campuses, and similar sites where footprint constraints, safety, building-code treatment, and deployment speed can justify a pricing premium. In those cases, the value proposition is not “the cheapest battery/kWh,” but the battery that can actually be sited, permitted, and built where it’s needed. By contrast, the Cube remains well suited for utility-scale and public-utility deployments where land is available, projects are planned years in advance, and regulatory certainty is prioritized over modular flexibility.
Seen through that lens, Indensity doesn’t narrow EOS’s strategy - it broadens it. It reframes part of the storage discussion away from chemistry and duration alone, and toward real-world constraints like land use, siting, permitting, and adjacency to load. Those constraints are becoming increasingly important as storage moves closer to population centers and mission-critical infrastructure.
So while Indensity may not have been the dramatic reveal some expected, it is a meaningful step in expanding EOS’s addressable market - not by replacing what already works, but by adding a system designed for customers with fundamentally different constraints and economics.