Go back

Unknown

1h 5m 40s

Unknown

Data centers are not built solely by tech giants like Google or Amazon, but by developers who manage land acquisition, community engagement, and infrastructure permitting. Rowan Digital Infrastructure exemplifies this role by emphasizing sustainability, transparency, and community-first development. Developers like Rowan have direct control over key sustainability factors—such as embodied carbon, water usage, and construction practices—through lifecycle assessments, material innovation (e.g., low-carbon concrete, mass timber), and partnerships with local water authorities. For instance, Rowan’s Cinco project in Texas reduced water use by 250% through collaboration with the Edwards Aquifer Conservancy, while its $38 million investment in Temple, Texas, funds local water infrastructure. Power remains largely the tenant’s responsibility, though developers advocate for renewable energy policies and prevent ratepayer cost increases by lobbying for fair cost allocation. Rowan avoids off-grid gas and uses short-term bridging solutions, prioritizing long-term grid integration. Developers are increasingly seen as stewards of community trust, especially in water-stressed regions. Communities should demand verifiable data, independent third-party validation, and clear accountability for environmental and financial impacts before approving projects. This model shows that developers can play a vital role in improving data center sustainability, transparency, and community acceptance—turning a controversial industry into a responsible, locally integrated component of modern infrastructure.

Transcription

12192 Words, 68943 Characters

English
All right. Hello, everyone. Greetings. This is Volts for November 18, 2026. Can a developer turn data centers reputation around? I'm your host, David Roberts. When people think of data centers, they generally imagine the big tech companies like Google, Meta, and Amazon building them. But the fact is, most of those facilities are built by companies you've never heard of. Developers who do the work of finding the land, lining up the power, dealing with the county commission, and constructing the shell. They then rent those shells out to the tech companies. It's the developers that most often face the local fights over noise, water, power bills, and tax breaks. So it's worth asking, in terms of sustainability, what a developer can control and what it can't. Rowan Digital Infrastructure is one of the bigger players in that layer. It has roughly two gigawatts under construction in Maryland, Texas, and Oregon. It markets itself as the sustainable, community-first developer. It recently put out a community guarantee with pledges on transparency, water, and ratepayer costs. But pledges are only pledges. I'm curious which of these commitments a developer can actually keep, given that the tenant often controls things like backup generation and load behavior, and what penalties, if any, there are for failing to do so. So I'm talking today with Rowan's CEO, Charlie Deitch, who came over from running Energy and Water Strategy at AWS, and J.D. Lambert, Rowan's Director of Sustainable Practices. We're going to get into Texas, Maryland, Water, and what towns ought to be demanding before they say yes. All right, let's do this. With no further ado, Charlie Deitch, J.D. Lambert, welcome to Volts. Thank you so much for coming. Thanks for having us, David. Thanks for having us. All right. So, Charlie, let's start with you just as a little background here. As I said, I think most people imagine the tech companies that are doing the AI, they're doing the computing, they sort of imagine them building the data centers, but that's not really how it works. So maybe just explain, like, what does a developer do? What does Rowan do? Which parts of a data center campus do you build and own and run versus what the tenant owns and runs? And, like, who's responsible for what? Yeah. There's no one model, David, but let me speak to it generally, and then we can speak to where some of the nuances are as well. So the way that Rowan creates value for our customers is that we go out and we find, where is there? Is there power available on the electric grid? Where is there land and communities that are going to be receptive? And also, you know, how will this site ultimately fit into the broader compute architecture of our hyperscale customers? We buy that land, we bring it through entitlements, we work with utility providers, we work really closely with communities to make sure that our development fits within their plans as well. And then ultimately, when we're somewhere in the 18 to 20 months away from being able to energize the site, we lease the site to a customer and construct it on their behalf. And then, like you said, they rent out the capacity in that site. Now, where some of the nuances lie in that is that for some customers, we just do the shell, as you mentioned. So we're responsible for land, power interconnection, substation, and the building itself. And other sites and for other customers, we go all the way through and we build the mechanical systems, the cooling systems, which, of course, impacts the efficiency of the building. And so sort of where you draw that scope is different. And so we're responsible for land, power interconnection, substation, and the building customer by customer. And even when you look across some of our peers, some of them are more sort of absolutist about we always go to here. Rowan is sort of hallmark of how we develop is we're pretty flexible, meet customers where they're at, and we'll sort of gear our scope delineation based on what our customers really need. Is it fair to say that the customers bring the servers though? You don't build the compute equipment. That's always on their side of the line. That's correct. Yeah. Servers, racks, IT equipment always comes from our customers. And so this is a question we're going to get back to later, but also like in terms of powering, in terms of power backup, what's backing up their power? Is that the customer's responsibility? I mean, you provide the grid connection, but in terms of backup power, what's your relationship to them? It's always our responsibility when we think about we're bringing this infrastructure to communities and we're responsible for making these projects work broadly. In terms of who actually is required to determine how many generators are going to be on site, somewhere between zero and a hundred percent backup. And there's options in between that. And it's responsible for the air permit and operations of those generators that can vary site to site. But Rowan has both in our portfolio. So we have sites where we operate emergency backup and we have sites where customers do as well. Just out of curiosity, because I think listeners might be wondering, why does this developer layer exist? Is it just that the tech companies don't want to take on the complexity of doing all of this? Or is it just that they don't want to take on the complexity of doing all of this? Yeah. Maybe David would help just with a little bit of context for how Rowan plays in this space. Like what is our lane in this industry? And then we can answer that question of why does this layer exist? Can companies do this themselves? Do they do it themselves? So most of our peers come from land logistics development. So think of developers that were putting together manufacturing, logistics centers, et cetera. And they sort of said, instead of developing this into a warehouse, or manufacturing, we could develop this into a data center. So they sort of come from land development world. Right. There's another set of our peers that kind of come from co-location world. So co-locations have been around a long time, longer than the hyperscalers. Those are data centers where people rent out one to two to 10 server spaces at a time and customers roll on their racks. And those people figured out, hey, instead of renting, having a hundred contracts for a megawatt, we could just do 100 megawatt deal with a hyperscaler. Rowan is really one of the first developers where our leadership team, including myself and beyond the leadership team, people throughout the company, we came from the hyperscalers. So we grew up in AWS, in Meta, in Google. And so we bring this view of the world in terms of how we develop with communities, how do we work with utilities, but not just utilities, the whole grid ecosystem. How do we think about sustainability? We bring the lens of our hyperscale customers, as opposed to people that come from land and logistics. So we bring this view of the world in logistics and are trying to catch up with what it means to develop at this scale. So we've got a bit of a different view, but in terms of the core value proposition, what developers bring is a shorter lead time to capacity. So of the hyperscalers, there's a set that really leans on self-build and have really robust self-build programs, which means they build their own data centers. And there's a set that sort of leans away from that and really focuses on working with developers. All of them work with developers in some capacity. And that's because if you go out and create a set of developers, you're going to have a set of developers that are going to greenfield the site. It's going to take you three, four, and some markets, five years, where Rowan does a lot of that work early at risk before we have a customer. And then when we bring a site to a customer, we have a much shorter lead time from signing a lease to capacity. So that's one key value proposition is customers are managing demand uncertainty. And in order to bring compute supply to that demand uncertainty, you need solutions that have different lead times. And our lead times are always shorter than their self-build programs. I think the other model, and this goes back to the context of really understanding our customers. When you think about the AWS, Google, Microsoft metas, they are looking for activities that are globally scalable. Like snowflakes are an anathema to these companies, right? Like they want to be able to do something a thousand times over in the exact same way. Right. And so if I'm a hyperscaler, once I have a building and a design I like, I can roll in my racks and set up my network the same way anywhere in the world. But when it comes to how do you navigate community concerns around water in Temple, Texas? Communities are snowflakes. Yeah. How does the grid operator and utility different in Frederick, Maryland, which is 20 miles north of Ashburn than in Ashburn, Virginia? It's very different. And so those are sort of situations where we can bring to our customers is a delivered product that looks like any other data center they're going to roll their racks into anywhere in the world. And we can deal with the use of that data center. And we can deal with the uniqueness of community concerns. What does a really good sustainable water program look like in this specific community, et cetera. So that's sort of giving them something that's infinitely scalable while we manage the complications and intricacies of the specific county utility grid, et cetera. So for the communities where you're citing, if the community wants to know who am I dealing with, who am I holding responsible, who am I making requests of, et cetera, it's mostly you. It's mostly the developer. Correct. That'll be the water stuff, the noise stuff, the land, whatever on and on. Most of that is dealing with you and not the tenant basically. Correct. And even things that are the tenants and this happens, right? We hand over the site to a tenant and then they're delivering racks that are coming in a truck every 20 minutes. And that truck traffic is clogging up the roads when school buses are running. The county calls us and we communicate with our tenant. We get a plan in place that day. And we're like, okay, we're going to do this. And we're like, the school buses aren't clogged the next day, right? So a big part of earning and establishing Trust is just showing up and delivering. And so at Rowan, we're never going to pass the buck and say, hey, those are our tenants' trucks. Sorry, there's nothing we can do here. Or here's a number to call them. We're always forward-leaning on solving these problems. Well, I want to get into that aspect of it a little bit more. But JD, I just want to ask you, so you're marketing yourself as a sustainable developer. And so then let's just talk about what pieces are under your control, basically, versus under the tenant's control. When you talk about sustainability, what are the kind of buckets you think about? Say you're going to a brand new site, like what are the sustainability buckets? And then where does your sort of responsibility end and the tenant take over? Stuff that becomes sort of like beyond your direct control. I love this question, David, because I think there's a lot of overlap between Rowan's responsibilities and how we deliver our projects. And I think that's a really good question. I think that's a really good question. And our customers who have really high, ambitious sustainability goals as well. I thought it would be helpful if I step back a little bit and tell you a little bit about Rowan. So Rowan originated out of an Article 9 dark green, quote unquote, fund. It's a regulatory classification for sustainable investment out of the EU and UK, if you're familiar with it. And then having that responsibility to our corporate sponsors, and then our customers and tenants with their corporate sustainability requirements for us, it started to blend together. What can we do here? What do we need to be doing to show that we are a responsible developer? And I'm going to go through a couple of things that we do and just touch on really quick. Embodied carbon, that's the first thing. It's the first carbon impact you have on a project. We're going to talk about that on its own. We're going to get into that a little bit more in a second. I don't preface this. In my role as Director of Sustainable Practices, I partner very closely with our internal energy and water team. And these are engineers. They focus a lot on energy supply. Great way to frame this. In your mind, if you're a visual person like me, me and my team focus on everything within the property boundary inward. And our energy and water team focuses on everything within the property boundary outward. It's not like, we'll stop, but we're pretty close. There's a lot of overlap, but just to frame it. So embodied carbon of our buildings and our site, energy, energy efficiency of our buildings, water, water efficiency, water sourcing, construction waste, and energy efficiency of our energy used during construction. Site stewardship. So one of our projects is a brownfield. I can get into that as well. Reclamation projects. Community engagement is huge. And community engagement isn't like specific to data centers, but we're doing it really well. And we've been doing it from the beginning. Like that's like how we're going to develop. And green finance. And those are just a couple of things that we're doing, but we're doing it consistently. And that's the key thing is that we've been doing it consistently from the beginning because sustainability is part of our ethos. It's where we originated from. And so we've had a lot of these external benchmarks and things that we're coordinating with, but we've made it our own. And we've been able to do so now with delivering our first data center projects this year. Have some receipts to show like what we say and then what we do that we're, you know, maintaining that integrity. When you are choosing a tenant, have you or can you put any kind of sustainability or environmental requirements in place? I think one of the things that we've been able to do is we've been able to do a lot of the things that we're going to be able to do in the future. So, you know, we've been able to do a lot of the things that we're going to be able to do in the future. And we've been able to do a lot of the things that we're going to be able to do in the future. What we're going to be able to provide them, being able to have that two-way data sharing piece is something that we're still working on. But for the most part, we're able to be aligned on the end results, especially when it comes to embodied carbon because of where we sit in their value chain. Well, let's talk about embodied carbon. So just for listeners, we're going to talk a little bit about embodied carbon. For listeners who are not familiar with the term, this is sort of like the carbon represented by the materials, sort of the carbon emitted in the course of making the materials that go into the building and the site. So talk a little bit about, think about embodied carbon and what control you have over it. I've been thinking about this, like in some sense, like low carbon concrete and low carbon building materials are still quite expensive in some cases. I'm just curious, like how big of a lot is that? How big of a lever you have? How much access you have to those things that you need? How do you think about embodied carbon? I think about embodied carbon every day. Love this question. Okay, so globally, buildings are responsible for 40% of global carbon emissions. A third of that comes from what we call embodied carbon. And these are the emissions associated with the harvesting, manufacturing, transportation within that, you know, phase of a product's lifecycle. As opposed to energy consumed in operations, etc. Yeah, we're just talking about just that first, like I get it from wherever I'm getting it from, from the earth, and then I'm transporting it, and then I'm in a plant. And all of our projects, every single project performs lifecycle assessments in the design phase. So it helps drive decisions, you know, we're making a design as fast as that is, and then validated at the end of construction. So that means we're getting. We're getting the actual material quantities, actual product-specific EPDs, environmental product declarations, if that's a new term for you, which are the nutrition labels for those products. And then we get to walk away with, you know, pretty good understanding of what the embodied carbon impacts are for that project. And we share that with our customers, with our tenants, who are very keen to understand what that ultimate value is. And then for us, it gives us benchmarking to be able to continue to drive that down. You know, for just. For just our projects, in Maryland, our first project, Bauxite One, we were able to get a 23% reduction in embodied carbon from the Carbon Leadership Forum's 2021 baseline. I'm using a static baseline for our LCA, so that I can compare multiple projects. We might adjust as that goes on, but for now, 2021 is that industry baseline. And by having that, I can compare my projects in Frederick, Maryland, to Texas, to Oregon. But we were able to achieve that. We achieved that 23% with little to no cost premium to the project. What we did was having those LCAs early in the design phase allowed us to go in at those, you know, GMPs, at those pricing exercises, and understand, well, the DMV, the District of Maryland and Virginia, EPDs are pretty mature when it comes to the EPDs. That will change in different parts of the country, as we've learned. Right. These nutrition labels, is that a national body that does that, or is it a local? It's not a national thing. It's a state. Who issues those? It's national. If you're a manufacturer, let's say, and we do this in some cases, working with local manufacturers, mom and pop shops, you can obtain an EPD for your product, whatever that is, and ranges in cost, but it's something that you can work with a consultant to help you perform a lifecycle assessment of your product, and you can walk away with your own EPD. A lot of the major manufacturers around the world, but this has really taken off in the U.S., I have found it harder to get some EPDs. So, we've had a lot of opportunities out of certain parts outside of the country, but luckily, we just build right now in the U.S., and it's much more readily available to manufacturers in the U.S. And we're just talking about concrete, steel, these are the products in question? Yes. So, we move very fast. I should mention that if it hasn't already been mentioned in data center development, things have moved very, very quickly. But through our LCAs, we've been able to identify our top three material impact categories consistently are concrete, steel, and insulation. Concrete. Concrete has the most levers, and it's one of the most widely used materials in the world. Yes. So, for us, the embodied carbon impacts in concrete, you know, there are folks who've been working in concrete their whole lives, like generational folks working in concrete. There's a whole new documentary out about concrete. I don't know if you're following this, but there's a big concrete documentary that just came out. Oh, perfect. That's right down my alley. Okay, great. So, I'll have to look at that. But yeah, so with concrete, we have the most levers, and there's also probably the most EPDs, I want to say, out for concrete. Because for every different project and every different strength, like, you have so many EPDs for these various projects. I like to equate concrete to, like, building a cake. First, you've got to work with, like, your volumes. Like, where do you have major volumes of concrete? Can you reduce those volumes, and you do, like, instead of a thick matte slab, can you do a contour matte slab, like, reducing the actual physical volumes of concrete? Once you've done that part, go into the mix designs themselves, and that's like the cake batter, you know, like, what are you putting in the mix? And I'll get into a fun thing that we're trying out on some of our projects in a moment. And then the cherry on top is, like, CO2 injection, like, your carbon captures and those types of things. Like, we don't rely on reductions just from that. We do, like, the hard work, the, like, LCAs, working with our structural engineers, working with the concrete suppliers, like, trying to drive that. So, for example, I was mentioning with concrete, the cement accounts for 90% of the embodied carbon impacts in concrete. So, a lot of the technologies that are out there to reduce cement content. So, you're looking at replacements like slag, fly ash, glass pozzolans. On one of our projects in Frederick, Maryland, we just incorporated Prometheus Materials. They have this ProZero microalgae cement replacement. It's really cool. Like, it was really neat. My favorite part of it is when you go up and, like, look at these sidewalks because that's where we were able to pour it realistically. Can you see the algae? Yeah. Like, if you looked at the sidewalk and you were like, "Well, that sidewalk looks the same as that sidewalk," it's like, "Yeah." That's almost a 50% reduction in GWP. In terms of those reductions, are you publishing? Like, could a concerned member of the public, if you're proposing something in their community, see the baseline and the tool and what materials changed or what tonnage have changed? Like, how much of this material is available to the public to see? We have some case studies, but I don't know that we've published the actual LCAs. But I don't know why we couldn't. I think just making sure that we would have that available, like, you know, for scrutiny. Well, you know, yeah, this is sort of a theme here, but communities, I think, are quite suspicious these days about data center developers. And if you just come in saying, we're doing this and this and this, but there's no proof or documentation or whatever, there's going to be a blowback. J.D., maybe you can talk about the validation we've done with other third parties as well to validate some of the claims around carbon reductions, etc. Yeah, because as I understand it, you're pursuing. I'm pursuing LEED certification for some of these. And BREEAM, I guess, is the UK, the UK version of LEED. It now occurs to me that I should know what LEED stands for. But do you? Does anyone? Leadership in Energy and Environmental Design. Thank you. Thank you. And BREEAM, God knows what that stands for, but that's the UK version. Yeah, I forgot the acronym. But you don't actually have those certifications yet, do you? No. So we're working through that. We're on track for most of our projects. Are the projects pursuing? Yeah. BREEAM are pursuing BREEAM Excellent, which is like the third tier, third of four tiers in that rating system. And the rating systems are a great way for that validation, a third party validation, because we have to be able to uphold, like, to that level of scrutiny, any embodied carbon reduction, you know, claims that we're making. The LCAs are reviewed ultimately by those third parties. And so in that way, because of our process and performing LCAs, both in the design phase and validated through construction, we're using. that as part of the shift in data collection. That would be one of the best ways that we have from a validation standpoint. But the certifications, like third-party building rating systems, are a great resource for developers, like us especially, because we're doing so many things. How do you walk away as a consumer, as somebody who's like in the community and understand what does good look like? And a rating system like that, especially LEED, which is more recognizable, more of a household name here, is something that we're chasing LEED gold on. And we're on track right now. It takes a while to gather all the documentation and all of that. So we hope to have an update early next year on where we stand for those projects. Can I ask a quick nerdy side question, but just for my own purposes? There are some Microsoft data centers that are substituting mass timber for some of the steel and some of the concrete. And that is getting like 35 percent, 65 percent drops in inventory. And that's a lot of carbon. Have you looked into mass timber at all? It's like a slight mass timber fetish. Well, we are. And our Texas project, Synco, we're doing a mass timber structure. We swapped out metal for the mass timber on those projects. And I believe those are hitting at least a 30 percent. But it's just an office building. It's not like the data center part. The data center part with mass timber, we're getting into from an assessment and analysis standpoint, because it takes more than just like the swap. Because we also perform energy modeling and condensation risk analysis on all of our projects. It's a holistic approach. And that's really important here when we're trying to understand at a given site, in a given climate zone, with the performance, with, you know, all of these other requirements that we're measuring against, that we can ensure that at the end of the day, it's going to meet the needs of our customer. Well, just sort of a lead in to my next question. I was looking at this Schneider Electric sort of model they have of impacts. And there. Their sort of conclusion was that the building's core and the shell are a relatively small portion of the total emissions possible from one of these things. They said that if you just keep the servers one year longer than their rated lifetime, and instead of replacing them, then that alone gets you a 16 percent drop, which is like bigger than any, I think, single piece of embodied carbon. It seems like the big sustainability decisions. belong to the tenant, which is server replacement cycles and power. So maybe let's go to you, Charlie. I'm just curious about power. The sort of proposition to start with was we're going to offer land with renewable power attached. That is not, as far as I can tell, what is happening. All your sites today are running on the grid, on utility power, plus a little temporary gas at one of the sites. I'm curious what happened to that model. And is clean power something you can actually build in to your projects? Or does that just come down to the tenant and the utility making a deal between the two of them? Let's just talk about the power question. I'll get to that in a moment, David. Before we leave the body carbon discussion, though, I think the point is fair that some of the biggest levers are around how you power the data center and how you extend that. And I think that's a really good point. I think that's a really good point. Or alternatively, recycle server components, and those often lie with the tenant. Especially on power, you go look at the sustainability reports of Amazon, Microsoft, Google Meta. They have solved it in a way. Now, have they solved it sufficiently, I think is a really good topic to have. But from a GHGP reporting perspective, they have bought renewable energy against the megawatt hours they're using in their portfolios. We have not solved embodied carbon. So I do think from that angle of, there's one question of how, how big is the lever? And then there's another question of how effectively or cost-effectively has it been solved? So I think that's where scope three and embodied carbon becomes so important, because it is this piece that is sort of the hardest. And Rowan's been really forward-leaning on that. Well, maybe I'm misunderstanding you, but what I see is data centers out there herding toward gas and gas projections, the size of a small country coming online in the next five to 10 years. It doesn't look like power, certainly not clean, power. It doesn't look solved to me at all. I see Google and Amazon abandoning their sustainability commitments and opting for gas because that's what they can seem to get. And that's the fastest thing to get. So that doesn't look solved to me. The main thing the climate community is worried about is those GHG emissions of the power. And a lot of them are just building off-grid gas or stumping and lobbying for more gas pipelines and more gas developments. And so I guess I don't know what you mean by power being solved. Do you have any control over that, which just seems like the most dire thing happening? What control do you as a developer have over that? Right, David. So what we mean when we say that it's been solved is certainly not that the grid is 100% carbon-free. No one would claim that, of course. And there's a lot of work to be done, and it's being done to address that. Well, there are carbon-free options we can bring to the grid in a way that there are not carbon-free options yet. And that's the important work that's going on. So we've got solutions on the power grid to deliver carbon-free electrons. Now, are they fully deployed yet? No. But we don't have that in Scope 3, and that's why some of that innovative work we're doing around bringing algae, et cetera, is so important because we're sort of proving out these technologies in the same way we were proving out solar and wind 20, 30 years ago. In terms of what Rowan does, that's a really good question. We're fortunate to have, and sometimes challenged, but mostly fortunate to have customers with really ambitious sustainability goals. Their goals are ambitious, and then we can benchmark their progress and their actions against those goals. And I hear the criticism that you've brought to that on some of the announcements they've had around specific projects. But they do have ambitious goals, and our objective is to fit within their stated goals. So on some of our sites, that might mean making sure that if they want to bring their own energy supply portfolios, which include large amounts of renewable energy, they're going to be able to bring their own energy supply portfolios, that we've structured the market access with utilities to make sure that our customers can effectively serve those sites with their own renewable energy portfolios. And on other sites, it might mean that where we're responsible for power supply, it might mean that we're going out to the market and finding renewable supply options to bring into those sites on our customers' behalf. So there is distinction in the portfolio, some sites where we're responsible for securing the power, other sites where customers want Rowan to work with utilities, and other sites where we're responsible for ensuring that we have access to renewable energy. So I think that's one of the things that we're trying to do. And I think that's something that we're trying to do. And I think that's one of the things that we're trying to do. So if you're connected to the grid, and you say you're consuming renewables, that is basically offsets you're talking about, or some version of RECs. I know you were into this in your previous job. Are you anywhere trying to work with data center to offset hourly as opposed to just buying RECs for the years? Because, you know, I think Volt's listeners are aware of this controversy. If you just net out your emissions for the year, buy a bunch of cheap RECs, you have an accounting victory, but you don't really have much of a sustainability victory. Is anyone in your portfolio working to offset their hourly emissions. Yeah. I mean, both AWS and Google will have public goals. I should follow up and fact check if the other ones do as well around addressing that. One from Google, certainly from an hourly megawatt hour matching AWS, this is more centered around looking at timestamping carbon emissions and thinking about that timestamp carbon emissions throughout the course of the year. So those customers are certainly working on it and really focused on it. I do think your listeners will understand the difference between unbundled RECs, which are sort of, you're right, a cheap way to make the accounting work, and then doing 15, 12-year PPAs, sometimes 20-year PPAs that get new wind and solar projects built. And for our customers, the lion's share and vast majority of their clean energy that they bring are what we call bundled RECs, or effectively the long-term deals they did with those wind and solar projects. I spent a lot of my career putting those strategy together and then the execution of those projects as well. So I think it's totally fair to look at our hyperscale customers and hold them accountable to meet the goals they've set and push them to do better. I mean, we certainly do that as well. I also think we need to recognize that the investments they made have brought on tens and tens of gigawatts of wind and solar into this country that wouldn't exist if they hadn't made those commitments to those projects. There's a bit of frustration that we're not seeing the progress we would like to see, which, you know, I think is totally fair criticism. In line with that, I think there also has to be a recognition for the work that has been done in the industry. And then Rowan's job is to take that big macro trend and say, here's what it means in Temple, Texas or Frederick, Maryland, right? And here's how we can play our role on this specific project, which is a really fun angle because then we get to sort of get into some of the nuances that you can lose when you're talking about a, you know, multi-gigawatt global fleet, if you're one of our customers. A reader brought up this question, it sort of stuck in my head. It seems like one of the things you could do on power is to, there's a lot of. There's a lot of, as you know, solar and wind projects that are stuck in interconnection queues waiting to be connected to the grid. This is a long time difficult problem everybody's wrestling with. It occurs to me that like one thing a developer could do is go site near those and just offtake the power from them so they don't have to get interconnection agreements. In other words, like could help some of that wind and solar be, deployed faster just by siting next to them. Is that a strategy? Is that on your mind at all? Like trying to find ways of utilizing wind and solar that are otherwise stuck? Yeah, very much. And we have spent a lot of time working with renewable developers on that exact problem. And even if you say, look, 90% of those projects are in locations that don't work for reasons for data centers, there's still 10% of them that do. One of the things that we'll need to see to really figure out how to do that is we're going to have to do a lot of work on the grid. And we're going to have to really make that work is some of the interconnection queue reform that is willing to look at integrated gen and load together. The issue you have now is those are gen interconnection requests. And then ultimately, if you were to put a 300 megawatt data center next to a 300 megawatt solar project, now you have a load connect overnight, the grid may have plenty of capacity to serve that overnight. So from an engineering and technical perspective, it works from a how the ISO evaluates interconnection applications, there's some policy changes needed. The ISOs recognize that and are open to it, but it's slower than expected or slower than we'd like to see. A phrase that comes up a lot in my work. On the Frederick campus, Amazon holds two permits for about 99 diesel generators each. And because they've sort of split the campus up and gotten different permits for different parts, they're each coming in under the kind of air quality law. But I'm just, again, returning to the question of, do you have any control over that? Do you talk to Amazon about whether to have diesel generators on site or whether there are alternative choices? And then at the Temple site, you have some gas that you have brought on site, which you say is temporary, but how temporary? So just like, why not talk with Amazon about trying to use batteries instead of diesel generators, for instance, on a site that you own and are running like Frederick? Yeah. So let me talk a little bit about the decisions Rowan's made that'll impact effectively how those generators are operated. So we chose that site in Frederick largely based on the power infrastructure that was already there. That site was previously a aluminum smelter. It had transmission lines coming in from four different directions. It gives us, one, it made it so we didn't need to build new transmission lines in that community, which was really important to Frederick. They didn't want to see new transmission lines come in. Also gave us the opportunity to see new transmission lines coming in. So that's a value proposition to our customers. From an emissions perspective, it means these diesel generators are going to run very, very infrequently because we've put this on part of the grid where the reliability is quite high. So that's a decision and a control point we have. Ultimately, it's our customer's design decision that we're going to put in. Whether they're going to put in one-for-one diesel backup, 10% diesel backup, or whatever their case may be, that's a decision they're going to make within their own four walls. One thing we've done specifically in Frederick, and we weren't required to do this by the county, but we were happy to work on it, was to make sure that diesel generators are filled with HVO or a biodiesel project to reduce the carbon emissions that are sourced that, certainly off their initial fill. So we've worked with our customer to make sure that's the place. And that's their standard practice and policy too, wherever it is available. Temple site, what is the temporary natural gas power solution there? And how are you thinking about that? So to be clear, we haven't deployed a natural gas solution that's going to run 24-7, even as a bridge solution, but we are considering it and many are across the industry. And it is a challenge. I mean, it's a challenge from a sustainability perspective, for sure, from a community perspective. And it's one that everyone's wrestling with and our customers included. Here's how we think about it at Rowan. So we think that the long-term benefits of being on the power grid, from a cost perspective, from a liability perspective, and certainly from a sustainability perspective, are huge. And so we have not looked at any projects that are going to be running long-term on natural gas plants. We haven't signed any 10, 15, 20-year agreements with natural gas operators, just because we think ultimately. You mean off-grid natural gas. None of your projects are going to use off-grid power at all, or just off-grid natural gas? Are not going to use off-grid natural gas for over the long term. No, we're going to use it for the long run. So everything that we're looking at is a short-term bridge, which means we have an agreement with the utility to provide utility interconnection to the site. And then if we use natural gas, we're going to use it to bridge it when our customers go online until that utility connection shows up. It's a very different configuration than going to West Texas or another place and saying, "Hey, we have no plan to have a grid here. We're just going to build a natural gas power plant on site and do a 20-year agreement to have long-term natural gas." And frankly, a lot of our customers are aligned with that philosophy as well as, "Hey, the long-term reliability, sustainability, and cost benefits of being on the grid are really important. We always want to see a grid connection. And if we're going to look at natural gas, we're going to look at it in the context of short-term, say, one to three-year bridge until that utility connection is there." Okay. Let's talk a little bit about water. This is a big question, JD. There's a lot of weird information and misinformation circulating about water in this space. So there's a balance. We've talked about this on the pod before. It is possible to use closed-loop air cooling that uses very little water on site, ongoing basis. But if you do that, you need more power. It requires more electricity. And that electricity, presumably, represents water use somewhere else, at the power plant or in the power system. I'm just wondering for a community that is worried about water, how they should assess these things, and what you lean toward in your building. What is your approach to minimizing water use? Hey there, everybody. Don't worry, I'm not going to tell you about a new mattress or push a credit card on you. This isn't an ad. There are no ads on Volts. It is supported entirely by listeners like you. If you'll indulge me for a second, I'd like to ask for your support. I started Volts because we're all surrounded by depressing news about climate change and misinformation about clean energy. And it's never been more important to share the stories of the real people on the ground doing the real work of transition and all the ingenuity and courage and public spirit they are bringing to it. People are hungry to hear these stories, to learn from and find inspiration in them. I've heard from people who've changed majors or careers after hearing episodes of Volts. People using it in classrooms and community groups. Even state legislators who have passed bills inspired by specific episodes. Sharing these stories matters. It makes a difference. If you have found value in it and want to help me continue doing it, I hope you will join the community of paid subscribers at volts.wtf. It's about the cost of a cup of coffee a month. If you don't like subscriptions, you can make a one-time contribution, leave a review on Apple or Spotify, or just tell a friend about Volts. I am grateful for any and all support. If you're already subscribed to Volts, I'd love to hear from you. I'd love to hear from you. a paid subscriber. Thank you. And now, back to the show. Well, luckily, there's a lot of publicly available information about how we're approaching water responsibly, especially because unlike embodied carbon and emissions, water is visceral. And our director of water strategy, Chris Kurtz, will talk about this all day long. But you feel it, you see it, you turn it on in your kitchen, you know, so it's like in your face. So it's less nebulous than the carbon, you know, embodied carbon. But if you look at our community guarantee that you mentioned, the way we approach water is part of a holistic view with community partnerships moving beyond just simply minimizing the impact to delivering measurable advances in water stewardship and sustainability. A prime example of this is our Cinco project located in Medina County, Texas, where we partnered with the. And we partnered with the Edwards Aquifer Authority and their nonprofit on the Edwards Aquifer Conservancy to fund investments in incentivizations, essentially, for farmers to upgrade their agricultural irrigation. So it's pulling less water from the Edwards Aquifer, which is where our project pulls from. Now, again, our projects in Texas, water stress region, making sure that you're, from our standpoint, working with our tenants to design. We're able to have a cooling system that is appropriate for that area is, like, first, make sure how much water you actually need. And this partnership with the Edwards Aquifer Conservancy, we're able to offset 250% of the project's water use, and that includes construction water. So I don't know if anyone knows, like, if you're in construction, you know, like dust mitigation measures, like spraying down water. Construction uses a lot of water. And we're out there saying, well, here's our data that shows what we did at this site and what we're going to try to replicate. But we're going to try to replicate at other sites where available. Now, we just got lucky that in Medina County, this Edwards Aquifer Conservancy, you know, was available to us, and this partnership was available to us. And we'd like to be able to go into other communities where there's something similar. And in some way, we are. We're able to partner with more of those communities and learn about what's important. And we have an entire arm of our company that does that so well. But on Cinco in particular, is there a published dollar figure involved? Is there a third-party? Is there a third-party verifier involved that can reassure the community that this is real, that it's really happening? Yeah, so I forgot what the name of it is. I will have to talk with Chris about it. But it's like a volumetric water benefit analysis tool, I think. It's called 2.0 or something. But it's verifiable data that shows here's what we have as far as the inputs. Here's our assumptions for construction water use. Here's how much, you know, based off of the available data coming from the Edwards Aquifer Conservancy. We're able to validate the claim that we're offsetting 250 percent. And for us, we're able to partner with our customers in that as well. They were very excited to be able to partner on this, especially like early in that design phase, construction phase of a project instead of, you know, after the fact. Are you leaning toward these closed loop systems that don't use a lot of water for water conscious data centers? Is that becoming kind of a default or is that still a site by site question? More broadly, maybe Charlie. For Rowan? I mean, we have like our internal policy that if we're in a water scarce community, we are not going to use evaporative cooling, which would be the other alternative besides closed loop. So everywhere we're in a water scarce community, we're going to use closed loop and communities are requiring it. I think like, yes, we have that policy, but it would be required anyways. And I do think, you know, David, to your point on, hey, there's some misconceptions around this. That wasn't always true. Like there are data centers that were built, you know, in the last several years that do use a substantial amount of water for cooling. But I think communities are focusing on, especially if you're in a place like Texas, you know, water is hyperlocal. And in these communities, everything we're doing is closed loop. But just briefly to close off the water thing, JD. So in this one instance, you found kind of a ready-made partner that had a ready-made solution that you could help fund to remediate the water problem. Presumably that's not going to be true in every site where you go. Is this going to be a site-by-site thing where you're looking around for, aside from just the construction of the building itself, external ways of making the community whole on water or helping the community on water or being good stewards of water? Are there other examples beyond this, like other ideas about how to do this? Yes. So another recent headline. Rowan is investing $38 million in Temple water infrastructure. Temple is in Texas. Yes. Temple, Texas. Pulls from a totally different aquifer. That project, it's a Temple water infrastructure in a Sandman's community center. That's also publicly available. Obviously, this is like new. Wait, and what is this exactly? What is the $38 million investment in? It's in public infrastructure for Temple. So the breakdown is $25 million is going to go towards the South Temple water infrastructure capital program. $10 million towards the aquifer storage and recovery program, and $3 million towards the proposed Sandman's community center. So this is just community water infrastructure, basically, in the community where you're locating. Yeah. Is this something the community asked for? I'm just wondering how much of a part of the kind of the standard package these beyond the building solutions for water. I think there's two examples of what JD talked about, you know, Rowan going out and working with the Edwards Aquifer in Lytle, Texas, south of San Antonio, and then Temple, Texas, coming to us and saying, Hey, if you want to help us on water and water consumption in the city, we have our own infrastructure plans are sort of good bookends of what we see across communities. Like we go to communities and they say, we want to know you're doing the right thing. What is it? And they're looking for us to provide leadership and thought leadership. And there's other communities that are like, Hey, we know what we need, whether it's around sustainability, water consumption or community impacts. Can you help us with these things? And we're happy to lean in on that, too. So I think it's not a monolith. I think. I think what's consistent across all of them is they want to know, are you going to do the right thing for my community? Is this a good deal for our community from a sustainability, economic, et cetera, perspective? That's exactly the questions they should be asking. And it's incumbent upon us to have community specific answers, but all of them are going to be definitively. Yes. Like this is a good value proposition for you. Here's why we think it is. And if there's other stuff we need to be doing or could be doing to enhance that. We're going to lean in and that's a big hallmark of how we develop and how we engage around all of the issues we've been talking about today. Okay. Well, another piece of the pledge of the commitment is about grid costs. A lot of communities are worried that you come in and build a data center. You drive up power costs for us. Part of your pledge is we are not going to do that. We will take care of all the power costs. You will not see a rise in your. There's a lot of talk, I think about this going around and a lot of hand-waving going around, you know, you signed onto the white house rate payer protection pledge, which is a sort of pledge from all the hyperscalers to do this, but that is, I would say, charitably a symbolic commitment on the part of those entities. What do you mean by that? And again, like whether or not there are additional power costs and what they are. Doesn't that come down to the utility and the tenant? Like what control do you have over additional power costs and what does it mean when you say you'll pay for them? Yeah, there's one place we have really direct control, which is what are the infrastructure requirements to complete the project? And you know, the way we develop, we are always looking to go to places on the grid where that infrastructure impact is low to manage costs. That's something we fully control. Then there's a question, David, which you're raising of, okay, once those costs are known, how do we. How do they get fairly allocated? And you're right. That's something that we have influence over as a large developer, but we don't have control. Ultimately, the utility and the utility regulator have control over how rates get set and how those costs are assessed. What we've committed to, and I would say it's much more than symbolic, like we are actively lobbying on policies with utility commissions. What we've committed to is to say, hey, we're going to support policies. We're going to support utility tariffs where they look to collect. A hundred percent of the upgrade costs required to power these projects from the customers that are interconnecting. So we can't necessarily force the utility commission to do that or ask a utility to do it, but there's broad public support. And historically, and your listeners have followed rate cases. Historically, the way this works is industry, you know, used to be large manufacturing in this country would push back on those sorts of policies. And what we've said collectively as an industry is we support this. So we sort of took away the barrier for. Utility regulators, policymakers and utilities themselves to put in the tariff structures that fairly allocate costs and make sure that the infrastructure that's being added to power Rowan's projects isn't going to be show up in residential rates in that same community. And this is a little trickier in Texas because Texas already has this kind of law, the system that spreads transmission costs around to all repairs. So in terms of like what could be isolated to an individual project in Texas, a little trickier. It's just. really the building and the power equipment on your site. I don't know how deep you've gotten into trying to make those calculations in Texas. And any transmission extensions to the site as well. And then the fair pro rata share of the bulk transmission network. And I think that's where you're getting about is like there's a meaty conversation to have of what's the fair share of that bulk network. But historically in another states, that last mile infrastructure, a transmission line extension to the site would be socialized as part of the greater transmission network. And what we've said through, you know, the White House Repair Protection Pledge that we're going to support policies that allocate that cost directly to the projects themselves. Charlie, I'm curious, you wrote to Governor Abbott welcoming his pause on new data center grid connections. And just on the surface, that seems odd that a developer would cheer for a freeze on new connections for developments. I'm curious why you did that and what is going on context wise that made that necessary? And how are you thinking about them? I'd say first, like, we are really supportive of what the governor and the state is doing to make sure that there's a clear, that's being distinguished between developers that are thinking about development in the right way. And for us, that means going back to, are we doing the right thing for communities that we're coming to and developing and operating in? And that developers that haven't done that. And there are examples of both. And to your point, David, there's been such a negative perception of data centers across the country. And it's a huge understatement to say the volume has sort of gone up to, you know, it's gone up to, you know, 11 on this. It pains me in a way, because I do believe this infrastructure is extremely important. It's important for where we're going as a society. It's important for advances in healthcare. It's important for national security and for a host of reasons. I think what we're doing is extremely important and it's gotten this terrible reputation in the media and in the political world. And that is because there have been bad actors that are out there. And so when the state of Texas came through and said, hey, we need to find a way to have a clear test and way to assess projects that are doing this, the right way that are being transparent about their water use, making sure that their power costs aren't being borne by other customers that have engaged the community and are being welcomed by the community. Because we're doing those things, we sort of welcome that to say, hey, like, as opposed to slowing everything down, we're okay taking a beat to slow down for a minute to make sure that we've got a clear distinction between people doing this the right way. And we've made a ton of investments to do that and other developers that are not. JD, if you, if you were advising a county commission today that had a data center development proposed that they were on their land, what should they get in writing? What should they ask for independent verification of? What sort of penalties, like a lot of these are just county commissions in the middle of nowhere that are not necessarily set up to be sophisticated knowers of all these different levers and all these different possible impacts. To what extent should the county commissions be responsible for sort of putting a lot of this stuff in writing? And I wonder if it's just like too much to ask of them. I know a lot of county commissions are thinking about this. Like if they put a bunch of requirements on or just say no to XYZ style of development, that development might just move one county over. So on some sense, this has to be a state level thing. How should county commissions be thinking about this? What should they be asking for? Well, I'll echo what Charlie said. We welcomed it because all of the criticisms, like we were ready. We said, okay, well, we're already doing all of these things. Please judge me. Yeah, please require it. Yeah, please require it because we all want better buildings out there. So it's a hard thing to say like blanket how you should be developing, but the building and developing responsibly, not just data centers, like it's been around. There's a lot of lessons learned out there. There from all other types of like large infrastructure type projects and like large developments, community engagement I mentioned earlier is not new, but there's a lot of things you can do from how much of the site can you control? How much can you influence in terms of your setbacks and the noise requirements and how much is that developer coming in and partnering with your community? Are they having open houses? So many different levels, like how are they doing from the energy supply or energy efficiency? You know, in some cases we'll go in energy code is so varied across the US and like some jurisdictions are working on or 10 year old plus energy codes. Like are there things that we can do to like update work on energy code compliance in a given area, especially because in Maryland they're all adopting the latest and developing Maryland is very challenging, but we've done it. So I would say there's a lot of different areas and there's also so many resources that a community or a commission may not be aware of in their own backyard practitioners. And I come from the architecture world, so I know that there's practitioners across the country that can help guide even from engineering professionals. These are licensed professionals who work in energy efficiency, architectural design, reducing the impacts of the built environment. There's so much that you can do. And for us, the way that we've done it, a lot of us have come from Australia mentioned the hyperscalers teams and being able to influence. The design of your site. So using native planting species, a hundred percent native planted species, reducing your irrigation, improving the biodiversity of a given site in our projects and box site, we have like permanent easements for forested areas. And we added an additional, almost 20 acres of forest to the site. So we're going in and trying to leave the site better than we found it. And that's very true for box site three, the smelting plant. But I don't know. That I'd be willing to put like a whole blanket out there. I would want it to be as contextually relevant to that given community and like what really matters to them. But there's so many things as I've mentioned that are just low hanging fruit, embodied carbon, your water use energy efficiency, biodiversity, waste management, like so many things that have tentacles outside of the site. I would leverage those expertise of the folks already in your community, like professionals in those spaces. A non answer. Well it's a lot and Charlie you're okay with communities requiring these things and having penalties for not doing them. Like the pledge is nice and everything, but you know what I mean? Absolutely. I mean what we've seen across the country too is you can imagine there are county and city governments that have a really clear playbook for this. Certainly places where data centers have been around for a long time. That's true. But even in other places that have a big manufacturing industrial presence, you know, there is a site plan permitting process. Your site plan must have setbacks, clear height requirements. If you're going to use forested land, you need to preserve forest elsewhere. Like there's very clear guidelines and of course like your permits are subject to being in compliance and you can imagine there's other parts of the country and what we've seen is because of some of the changes around AI data centers going from these sort of core markets of Northern Virginia, Columbus, Ohio, et cetera, and expanding out to much more rural America. That when you go to some of these more rural communities, they don't have that playbook in place and we have been very forward leaning and saying here's how we think about it. We had leadership from the city of Temple, Texas up to Frederick, Maryland to say come meet with the county and Frederick have a chat with how we've worked together with them, but also how they think about this temple is really sophisticated, but data centers are relatively new to Temple and then there's even more rural communities where they just don't quite know what the requirements are and we see it as our obligation. To sit down and educate them and sort of think strategically with them the leadership and the community but I do think that there have been you know examples of developers that don't and they sort of say hey this is an opportunity just to sort of do exactly what we want without input because those clear rules of the road aren't there and that has created an understandable pushback that we've been working to sort out so we're hopeful we're optimistic the counties and the communities that already know us they think very highly of Rowan. I can say that with confidence and that's not because we're flawless but it's because we're open we know we can do better and we show up to those communities eager to do so don't you think it would be better in the long haul for these standards that you're trying to meet and that you're sort of counseling communities to ask for are codified in law like wouldn't it be better to have not only better for the communities but better for the developers and the data center developers to have a clear. Standard high quality set of rules and requirements that are in law that every developer and data center developer had to follow and thus like a communities would know they wouldn't have to learn all this stuff from scratch to figure out what to ask for and be like the developers could know that they can go places and be welcome and they don't have to have a bespoke fight or a bespoke you know sort of like. Consulting process all over again with every new community do you think would be better eventually to take the highest possible standards and codify them into law it sounds nice David I think the challenge we'd have is that what those standards would be would be so different on community to community I think it's great for communities to have those high standards developed already that I think is super powerful and have kind of clear rules of the roads and expectations but that is going to be very different in Frederick Maryland versus someplace else. place in Texas versus the northern Midwest when you think about What are the requirements of the water system? What are the sort of key considerations on the power grid? I mean, just think about developing in Arizona from the power grid where you have this, you know, very clear capacity need in the late afternoon hours and how important it is to have storage there versus another part of the country that just doesn't have that feature. So I think it is important. These are massive pieces of infrastructure that have to integrate with communities, but also with other massive pieces of infrastructure like the power grid, the water system, the fiber system. And so when we think about setting those clear rules of the road, you really have to think about what is happening in those systems around you, which are different from place to place across the country. Okay, I know you got to run, but I did want to ask you just as a final question. You are no doubt aware that there is a huge backlash. There is a huge backlash against data centers underway that has really developed and grown quickly, something like 71%, I think, on the last poll of people opposed data centers. And this is something, obviously, there's no concrete way to answer this, but do you think that that opposition has spiraled into something that is beyond these sort of concrete questions of water use or power use? Do you think that that opposition has spiraled into something bigger that is now beyond the control of you as a developer? Or do you think it will be possible in coming years for states to up their standards, for developers to up their standards, for the industry to up its general standards, for these bad actors to be reined in, for like, Amazon's out building the biggest, highest emitting facility in industrial history right now? That's not helping. Do you think that it is possible to. Reign in this backlash for people to come around on this or not? I guess you can't very well abandon hope as a developer, but like, where do you see the backlash currently? It goes back to what I said before that, like, I believe deeply in how important this infrastructure is to our society. We will look back at data centers in the same way we think about, like, the national highway system. We will just say, like, yes, this is fundamental to, like, the fabric of our life or the power grid, right? To your question on what can Rowan do? What can we influence? I think there's a set of concerns within communities which are very valid. Like, is this a good project? Are you going to have an impact on my water system? How are you thinking about sustainability? How are you thinking about economic impact in this community? Those are 100% on us. We owe it to these communities to have impactful answers and to deliver on those and be held accountable for them. 100% within our control. Then I think there's this other thing happening on a national level, which is people are scared of AI because they don't understand it. They have concerns around what it's going to mean for the larger economy, what it means for their jobs. And that is an addressable issue, but that is going to take the large language model labs, the large hyperscalers to really come out and make the case for this technology. I think what we've seen so far is, hey, this is a little bit gimmicky. I get great value out of using ChatGPT to, you know, come up with kid-friendly recipes on the weekend. But, like, I think everyone thinks so. But, like, people are also using this technology to find cancer much earlier and treat it and save lives. And, like, that part of the story of why this technology is so important to our society is not being told in a way that's impactful. And I think that's a much broader industry problem. And we sort of help bring that story to the communities we operate in. But we need people with a much louder platform and that are really developing these core technologies to step up and make the case for why this infrastructure should be here broadly. Be honest with us. When you're in a room with these people behind the scenes, are you tempted to smack them around the head at their utter incompetence in the way they've communicated their technology and their goals so far? Like, I know you can't make them into more empathetic and adept human beings, but, like… No, I mean, David, you can imagine… Do you try to influence them? The infrastructure teams, the people doing the leases and working with us on these developments within our hyperscale partners, I think they agree, right? Like, they agree that… We need to be much more vocal about telling the benefits and the impact of this. So, you know, I think that the people that are close to the infrastructure, whether you're on the developer side or on the hyperscaler side, we all agree on the need for this. It's a matter of channeling that into the national narrative in a productive way. Okay. I've kept you an hour. I appreciate you guys coming on and talking through these things. It's interesting to hear from the developer perspective. I don't think it's well represented in the public dialogue exactly what their role is. So, thanks for coming on. Thanks for coming on and walking us through all of this. Thank you. Yeah. Thank you, David. We love this space. We know it's so important to be thinking about sustainability when you're developing infrastructure at this scale. So, hopefully this was helpful, and we'd love to come back and talk more about it when the time is right. So, thank you for having us. All right. Thanks, everybody. You've been listening to Volts, founded and hosted by me, David Roberts, produced by Nate Peavy. And supported entirely through the generosity of listeners like you. If you have 10 seconds to spare, please leave a rating or review on your favorite podcast app. It really helps other people find the show. See you next time. Volts. Volts. Volts. Volts. Volts.

Podcast Summary

Key Points:

  1. Data centers are primarily built by developers who secure land, navigate permits, and manage community relations, not by tech companies.
  2. Rowan Digital Infrastructure, a leading developer, emphasizes sustainability, community engagement, and transparency through commitments like water stewardship and power cost control.
  3. Developers have significant control over embodied carbon, water usage, and community engagement, including material selection and partnerships with local water authorities.
  4. Power supply remains largely under tenant control, though developers can support renewable integration and advocate for grid-level clean energy policies.
  5. Rowan avoids off-grid natural gas and uses short-term bridging solutions, prioritizing long-term grid connectivity for sustainability and cost reasons.
  6. Water use is minimized through closed-loop cooling in water-stressed areas, with active community partnerships to offset water consumption and improve local infrastructure.
  7. Developers are actively lobbying for fair cost allocation policies to prevent ratepayer burdens, especially in states like Texas with complex utility structures.
  8. Communities should demand transparency, independent third-party verification, and clear accountability for environmental and financial impacts before approving projects.

Summary:

Data centers are not built solely by tech giants like Google or Amazon, but by developers who manage land acquisition, community engagement, and infrastructure permitting. Rowan Digital Infrastructure exemplifies this role by emphasizing sustainability, transparency, and community-first development. , low-carbon concrete, mass timber), and partnerships with local water authorities.

For instance, Rowan’s Cinco project in Texas reduced water use by 250% through collaboration with the Edwards Aquifer Conservancy, while its $38 million investment in Temple, Texas, funds local water infrastructure. Power remains largely the tenant’s responsibility, though developers advocate for renewable energy policies and prevent ratepayer cost increases by lobbying for fair cost allocation. Rowan avoids off-grid gas and uses short-term bridging solutions, prioritizing long-term grid integration.

Developers are increasingly seen as stewards of community trust, especially in water-stressed regions. Communities should demand verifiable data, independent third-party validation, and clear accountability for environmental and financial impacts before approving projects. This model shows that developers can play a vital role in improving data center sustainability, transparency, and community acceptance—turning a controversial industry into a responsible, locally integrated component of modern infrastructure.

FAQs

Developers like Rowan identify suitable land and communities, secure power connections, handle permitting, and build the physical infrastructure. They own and manage land, power interconnection, substations, and the building shell. Customers (like AWS or Google) provide servers, IT equipment, and manage operations such as backup power and cooling systems.

Yes, developers have significant control over embodied carbon through lifecycle assessments, material selection (like low-carbon concrete or mass timber), and design optimization. They also manage water use by adopting closed-loop cooling in water-scarce areas and partnering with local agencies to offset water consumption.

Rowan conducts lifecycle assessments during design and validates them through third-party reviews. Projects pursue third-party certifications like LEED or BREEAM, and they publish detailed data on material use and carbon reductions to ensure transparency and accountability.

Rowan works with utilities to secure renewable energy for customer sites, either by enabling customers to use their own renewable portfolios or by sourcing renewable power directly. They avoid long-term off-grid natural gas and use it only as a short-term bridge until grid connections are established.

Developers partner with local water authorities and communities to implement water-saving measures, such as closed-loop cooling in arid regions. They also fund community water infrastructure projects, like irrigation upgrades, to reduce strain on local aquifers and demonstrate real, measurable benefits.

Developers have direct control over infrastructure costs and are actively lobbying for policies that ensure these costs are fairly allocated to project users, not general ratepayers. They support tariffs that collect full infrastructure costs from interconnecting customers, reducing community rate increases.

Chat with AI

Loading...

Pro features

Go deeper with this episode

Unlock creator-grade tools that turn any transcript into show notes and subtitle files.