Digital Growth Now Has a Physical Balance Sheet
We often describe digital transformation through software metrics: workloads migrated, users served, features released. Less visible is the physical infrastructure underneath-and an increasingly important question: who bears the cost of the electricity, water and grid upgrades required to sustain that growth?
Maryland’s new review framework covers data centres at or above 25 megawatts, including major expansions, and links state support to scrutiny of grid costs, water use, environmental impacts and community concerns. The signal extends beyond stricter permitting: infrastructure economics and legitimacy are becoming central to the case for growth.
From TCO to lifecycle accountability
A conventional technology business case covers compute, storage, migration and operations. Yet a large data centre is also a long-lived participant in regional infrastructure systems.
I would broaden total cost of ownership to include dedicated grid investment, water constraints, environmental obligations and uncertainty around demand forecasts. Who funds upgrades? What happens if utilisation falls short? Will the project genuinely add infrastructure capacity, or shift costs onto existing utility customers?
This does not mean every facility must pass an identical test. It means projects need credible, transparent assumptions. A profitable proposal can still impose unacceptable social costs; an environmentally responsible proposal can still be financially unsustainable. Strategic decisions must confront both realities.
Accountability has to become a platform capability
A task force and public dashboard are useful governance mechanisms, but neither substitutes for disciplined operations. I expect energy-, water- and infrastructure-awareness to influence architecture more directly: site selection, power redundancy, cooling, workload placement and expansion planning.
This matters as AI increases demand. Training jobs, batch inference and latency-sensitive services have different operational profiles. For flexible workloads, time-aware scheduling around grid conditions may help. For latency-critical processing, locality and power resilience matter more. Neither strategy is universal-and digital orchestration cannot substitute for physical capacity.
The practical requirements are decisive: auditable telemetry, credible demand forecasts, maintained reporting and explicit responsibility for infrastructure funding. A dashboard cannot replace enforceable commitments. Reporting should be treated as a continuing operational feedback loop, not a document completed before launch.
A new architectural literacy
For architects and CTOs, resource constraints must become design inputs from the beginning, rather than late-stage compliance gates. For founders, especially those building AI-enabled businesses, “scalable compute” is no longer a sufficient promise. Investors, customers and regulators will increasingly ask where capacity comes from, how expansion is financed, and what happens when resource assumptions change.
The same principle applies to digital public infrastructure worldwide. Locating data within a jurisdiction does not guarantee resilience if its power, cooling or financing model is fragile. Genuine digital sovereignty requires operational continuity, transparency and accountability-not merely geographic control.
This is also an important lesson for emerging engineers: look through the abstraction. What does “the cloud” depend on, who maintains it, and who absorbs the risk when assumptions fail?
Three questions should now appear in every major infrastructure business case:
- Who funds the incremental power, water and supporting infrastructure?
- Which workload compromises remain acceptable under realistic demand?
- Can the public independently verify the commitments behind the performance data?
The real test of digital leadership is not how much capacity we can promise, but whether we can deliver it sustainably and remain worthy of public trust. That is becoming an engineering and governance challenge-not merely a communications exercise.
About the Author: Sanjeev Sarma is the Founder Director and Chief Software Architect at Webx Technologies. With a core focus on Generative AI integration, Cloud-Native Scalability, and Enterprise Software Architecture, he has spent over two decades driving digital transformation across Northeast India and beyond. Beyond his corporate leadership, Sanjeev is deeply invested in shaping the future of the IT industry. He serves as an Industry Expert on the Board of Studies for Assam Don Bosco University’s School of Technology, advises state technology committees, and actively mentors emerging tech startups at STPI. He brings a unique, dual perspective of high-level enterprise execution and future-ready academic curriculum development.
