Firm Power Is an Architecture That brought the morning back to its recurring problem: What counts as available power? During the “Solving for Power” panel, moderator Lillian Kasa of Metlen Energy & Metals argued that data centers cannot operate on announcements. They need reliable electricity delivered on a schedule and backed by a commercial structure that can be financed. Margarita Patria of Charles River Associates made the distinction even sharper. Firm power is not merely generation. It is generation, transmission and fuel availability working together. Todd Detling of FortisAlberta added an important Alberta-specific qualification. Despite perceptions that the province had substantial transmission capacity available for new development, FortisAlberta is encountering constraints, particularly around the Edmonton and Calgary fringes. At the distribution level, the demand is already material. Detling said FortisAlberta has connected nearly 80 MW of data center load over the past several years, has approximately another 80 MW in the build queue, and has received roughly 300 MW in additional requests. Those smaller increments matter in a market dominated rhetorically by gigawatt announcements. They are another indication that developers are searching for power pathways they can execute now. AI Is Not Just a Bigger Load Tesla’s Sean Jones added another technical wrinkle: AI training loads can change extremely quickly. Data center power planning traditionally focuses heavily on annual consumption, peak demand and hourly load. GPU clusters can create significant changes at the second or even sub-second level. Jones described AI training demand falling from full load to around 30% in less than a second. That kind of movement can be difficult for onsite turbines and reciprocating generators to follow and potentially disruptive to the grid. Battery energy storage is therefore taking on a different role. The familiar data center battery story is backup power. The emerging AI story is

On-device translation used to mean a separate model for every language you wanted to support. English to French, English to German, and so on. However, that becomes unsustainable at a global scale when you’re talking about thousands of possible language pairs. Add to that the fact that most developers have to either send translation requests to the cloud to get fast, accurate results, or keep it local with restricted language support. Tether’s AI Research team has developed a family of multilingual translation models, TranslatePsy-EuroNano, that each support nine European languages, with deployment built around a pair of multilingual models rather than separate bilingual models for every language pair. What makes this possible Supporting a full European market on-device has previously meant bundling dozens of separate model files, but this is impractical for mobile apps and those building them. Tether AI’s multilingual open‑source edge translation models set the standard for efficiency, quality, and speed. For developers, the possibilities are endless. Using English as a pivot, the models remain comparable to Mozilla Firefox’s Bergamot-based translation system while dramatically reducing the size of on-device translation. At its smallest tier, Tether’s deployment is 17.6 times smaller while maintaining comparable translation quality. Tether’s deployment takes up 36MB to 89MB, depending on the tier you use. By comparison, the equivalent Firefox setup requires 18 separate bilingual models totaling 633MB to provide the same language coverage. The models are small enough to run efficiently on edge devices while supporting nine European languages from a single multilingual deployment, making multilingual experiences practical for a much wider range of software. Potential applications include travel and navigation apps, educational platforms that present lessons and resources on-device. The models are also designed for academics and researchers. Because the weights are openly available, researchers can fine-tune them for specialized domains, like customer

For gigawatt-scale AI developments, the developer may be involved with substations, transmission interconnections, generation plants, batteries or other behind-the-meter infrastructure long before servers arrive. Solaris now describes its overall portfolio as including generation, distribution, installation and commissioning, aftermarket support, and operations and maintenance. The arrival of companies with roots in energy and heavy industrial services suggests that the data center supplier base itself is changing as projects begin to resemble large industrial infrastructure developments. The Pattern Extends Across the Services Stack The transactions involving T5, Limbach, JK Technology Services and Solaris are hardly isolated. A wider wave of acquisitions and partnerships is pushing equipment manufacturers, contractors, engineering firms and specialist service providers toward broader roles across the data center lifecycle. Vertiv provided perhaps the clearest parallel in September, announcing an agreement to acquire UtilityInnovation Group for approximately $1.45 billion in cash, with additional consideration tied to performance. UIG brings microgrid controls, onsite-generation orchestration, specialized switchgear and behind-the-meter power architecture. The deal also extends a broader 2026 acquisition push by Vertiv that has added liquid-cooling specialist Strategic Thermal Labs, chiller manufacturer ThermoKey and prefabricated infrastructure provider Bmarko as the company builds out more of the AI data center infrastructure stack. Vertiv described the move as extending its portfolio upstream from the critical power and cooling systems inside the facility toward the grid interconnection and onsite generation itself — effectively creating a path from power source to chip. Days later, Flex announced a $4.4 billion agreement to acquire EPC Power, adding grid-forming and power-conversion technology designed for data centers, utility-scale energy storage and microgrids. EPC Power’s platform includes rectifiers and DC-DC conversion for emerging 800-volt data center architectures, with solid-state transformer development also planned. The company says it has more than 15 GW deployed across 62 countries and expects its annual U.S.

The AI infrastructure market has become very good at announcing gigawatts. Delivering them is another matter. That distinction framed one of the closing sessions of Day 1 at the Data Center Frontier Trends Summit 2026 (Aug. 4-6), where Sean Farney, vice president of data center strategy at JLL and a member of the Data Center Frontier Editorial Advisory Board, moderated a discussion on why some AI data center projects advance from concept to construction while others remain little more than ambitious site plans. Farney was joined by Lawrence Vo, vice president of M&A and capex at Csquare; John Day, chief commercial officer at CleanArc Data Centers; Justin Loth, executive director of power development at Provident Data Centers; and Roshan Shah, co-founder and CEO of Decimal Digital. The question Farney put before the group was straightforward: amid a market moving at what he called “the speed of light,” what separates the developers that actually get projects done from those that do not? The answers repeatedly came back to the same point. In the current market, land, capital and an announcement are no longer enough. Developers have to prove that power is deliverable, infrastructure is ready, regulatory processes are moving, communities are receptive, talent is available and the commercial model can withstand changing conditions. A Gigawatt on Paper Is Not a Gigawatt of Capacity For Loth, who spent roughly 15 years on the utility side before joining Provident, the scale of current data center proposals alone should force the industry to think differently about what constitutes a credible project. Before the hyperscale and AI expansion, he noted, gigawatts were a measure more commonly associated with cities than individual loads. “A 3.5 gigawatt campus,” Loth said, is roughly equivalent to the native load of Austin or San Antonio. That scale makes the distinction

As a result, Microsoft has said six additional data centers planned in the region are being designed around biomimicry principles rather than treating landscaping as something added after the engineering work is finished. The change, from landscaping as decoration to ecology as a design input, is now being applied elsewhere. There is already a significant US example, set in Mecklenburg County, Virginia, where Microsoft originally announced the Chase City Conservancy in 2022, as part of a data center development south of Chase City. The completed project, which opened in April 2025, protects more than 230 acres from development. It includes more than eight acres of wetlands, over 16,300 linear feet of restored streams, 185 acres of native pollinator habitat, more than 25,000 planted trees and over three miles of publicly accessible walking trails. Local environmental organizations helped shift the design away from what the company describes as a more conventional recreational area toward biodiversity and habitat conservation illustrating the community-engagement side of Microsoft’s model, which, given the current temperature of such relationships, can’t be understated. For data center developers, that may be as important as the ecological results. Community impact is no longer being evaluated on just tax revenue and jobs. Turning portions of a site into protected wetlands, forests, trails or habitat potentially creates a visible local benefit in ways that renewable-energy contracts hundreds of miles away cannot. Microsoft’s commitment to the local community has been led by their Community First AI Infrastructure Plan announced in January 2026. Wetlands in Wisconsin, Screening in Georgia At Microsoft’s massive Mount Pleasant, Wisconsin, AI data center development, the company is working with the Root-Pike Watershed Initiative Network on restoration projects involving wetlands, native prairie and forested riparian buffers. One element involves returning previously straightened streams to more natural, winding channels, improving aquatic

Software is still the gatekeeper Axelera In terms of software enablement, Axelera’s Voyager SDK spans its existing Metis products and the new Europa architecture, providing a common environment across embedded, edge and server deployments, with support for a multitude of computer vision models, LLMs, VLMs, diffusion models, speech and other AI workloads. To automate setup, Axelera’s Voyager Wingman uses natural-language prompts to help developers create or port inference pipelines, while AxeleraScript, or AxScript, provides a Python-enabled domain-specific language with lower-level AIPU control for custom operators and transformer models. This could prove every bit as important as Europa’s performance and efficiency. Enterprises already have models, development environments and application stacks. Extensive rewriting or specialized expertise adds development and operational costs that can quickly undermine savings on hardware and power.