Fervo Energy launches $1.33bn IPO, the largest climate-tech listing of 2026


TL;DR

Geothermal developer Fervo Energy is offering ~55m Class A shares at $21–24 each in a Nasdaq IPO positioned as climate-tech’s most direct play on the AI infrastructure trade.

On Monday, Fervo Energy formally launched its IPO roadshow, offering 55,555,555 shares of Class A common stock at an indicated range of $21 to $24 each. At the high end of the range, the geothermal-energy developer would raise as much as $1.33bn and become the largest climate-tech IPO of 2026 to date. The company has applied to list on Nasdaq under the ticker FRVO, with pricing expected the week of 11 May.

Fervo’s commercial proposition is the deployment of enhanced geothermal systems at scale. The company combines horizontal-drilling techniques borrowed from oil and gas with fibre-optic sensing and advanced reservoir engineering to extract geothermal heat from hot dry rock formations that, until recently, were not economically viable as energy sources. Canary Media’s coverage of Fervo’s S-1 emphasised the company’s progress on its first commercial-scale Cape Station project in Utah, which is being developed in phases and has signed power-purchase agreements with hyperscaler customers including Google.

That hyperscaler-customer dimension is the part of the Fervo story that made the IPO viable. Geothermal has been a marginal energy category for decades, with deployment limited to geographies where naturally hot rock met permeable reservoirs near the surface. Fervo’s enhanced geothermal approach extends the addressable geography substantially, and the AI build-out has produced a customer base, hyperscalers, willing to sign long-term power-purchase agreements at premiums for 24/7 carbon-free baseload.

Why this IPO matters

The structural argument behind Fervo’s pitch is that AI infrastructure has, in 2026, become one of the largest new sources of demand for clean baseload power. TNW has tracked the energy dimension of the AI build-out, and the relevant context is straightforward: hyperscaler capex is on track to exceed $725bn this year, and a meaningful share of the constraint on data-centre deployment is no longer money or chips but power, specifically reliable, low-carbon power available 24/7. Fervo is, on its own framing, a direct answer to that constraint. TNW’s earlier coverage of Oracle’s $16.3bn Stargate-related financing and the broader pattern of AI infrastructure being financed against contracted lease and power agreements is the funding context Fervo is now plugging into.

The 💜 of EU tech

The latest rumblings from the EU tech scene, a story from our wise ol’ founder Boris, and some questionable AI art. It’s free, every week, in your inbox. Sign up now!

TechCrunch noted in its IPO preview that Fervo has been one of the most-watched climate-tech companies for several years, with backers including Breakthrough Energy Ventures, Sumitomo Corporation, and a long roster of climate-orientated funds. The IPO is the company’s transition from private climate-tech bet to public infrastructure operator. Renaissance Capital’s IPO desk set the deal terms at $1.2bn before the upsizing to $1.33bn at the offered range, signalling reasonable book demand at the higher figure.

The risks behind the listing

Geothermal at commercial scale remains a hard engineering problem. Fervo’s Cape Station has demonstrated commercial viability in pilot phases, but the trajectory from a single producing site to a fleet of multi-gigawatt geothermal facilities is not yet proven. Bloomberg’s IPO coverage flagged execution risk specifically around drilling-cost inflation and the regulatory environment for the long-duration land and water permits that geothermal at scale requires.

The financing context is also volatile. Climate-tech IPOs have, in recent years, performed unevenly in public markets, and Fervo’s listing comes into a market that has been more enthusiastic about AI infrastructure plays than about climate-tech assets even when the latter directly serve the former. The company’s pitch, that geothermal is the cheapest 24/7 carbon-free baseload available to hyperscalers, will be tested by both how the order book closes and how the share price holds in the weeks after listing.

There is also a softer comparison worth noting. TNW recently reported that SpaceX’s pre-IPO disclosures warn orbital AI data centres rely on unproven technologies and may never be commercially viable. Fervo’s commercial proposition, by contrast, is grounded: terrestrial drilling, conventional fibre-optic sensing, established power-grid interconnection, and signed power-purchase agreements with named hyperscaler customers. The IPO will, if it prices at range, give public investors a way to participate in the AI-infrastructure trade through a climate-tech vehicle that is, by current standards, unusually mature.

Pricing the week of 11 May. Bookrunners include J.P. Morgan, BofA Securities, RBC Capital Markets, and Barclays as joint leads, with Baird, BBVA, Guggenheim, MUFG, Société Générale, William Blair, Piper Sandler, and Wolfe-Nomura on the wider syndicate. The deal is, on paper, well-supported. The final indicator of climate-tech IPO appetite in the AI infrastructure cycle is now the order book.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Vibe coding has taken the development world by storm—and it truly is a modern marvel to behold. The problem is, the vibe coding rush is going to leave a lot of apps broken in its wake once people move on to the next craze. At the end of the day, many of us are going to be left with apps that are broken with no fixes in sight.

A lot of vibe “coders” are really just prompt typers

And they’ve never touched a line of code

An AI robot using a computer with a prompt field on the screen. Credit: Lucas Gouveia / How-To Geek

Vibe coding made development available to the masses like never before. You can simply take an AI tool, type a prompt into a text box, and out pops an app. It probably needs some refinement, but, typically, version one is still functional whenever you’re vibe coding.

The problem comes from “developers” who have never written a line of code. They’re just using vibe coding because it’s cool or they think they can make a quick buck, but they really have no knowledge of development—or any desire to learn proper development.

Think of those types of vibe coders as people who realize they can use a calculator and online tools to solve math problems for them, so they try to build a rocket. They might be able to make something work in some way, but they’ll never reach the moon, even though they think they can.

Anyone can vibe code a prototype

But you really need to know what you’re doing to build for the long haul

For those who don’t know what they’re doing, vibe coding is a fantastic way to build a prototype. I’ve vibe coded several projects so far, and out of everything I’ve done, I’ve realized one thing—vibe coding is only as good as the person behind the keyboard. I have spent more time debugging the fruits of my vibe coding than I have actually vibe coding.

Each project that I’ve built with vibe coding could have easily been “viable” within an hour or two, sometimes even less time than that. But, to make something of actual quality, it has always taken many, many hours.

Vibe coding is definitely faster than traditional coding if you’re a one-man team, but it’s not something that is fast by any means if you’re after a quality product. The same goes for continued updates.

I’ve spent the better part of three months building a weather app for iPhone. It’s a simple app, but it also has quite a lot of complex things going on in the background.

It recently got released in the App Store—no small feat at all. But, I still get a few crash reports a week, and I’m constantly squashing bugs and working on new features for the app. This is because I’m planning on supporting the app for a long time, not just the weekend I released it, and that takes a lot more work.

Vibe coders often jump from app to app without thinking of longevity

The app was a weekend project, after all

A relaxed man lounging on an orange beanbag watches as a friendly yellow robot works on a laptop for him, while multiple red exclamation-mark warning icons float around them. Credit: Lucas Gouveia/How-To Geek | ViDI Studio/Shutterstock

I’ve seen it far too often, a vibe coder touting that they built this “complex app” in 48 hours, as if that is something to be celebrated. Sure, it’s cool that a working version of an app was up and running in two days, but how well does it work? How many bugs are still in it? Are there race conditions that cause a random crash?

My weather app has a weird race condition right now I’m tracking down. It crashes, on occasion, when opened from Spotlight on an iPhone. Not every time does that cause a crash, just sometimes.

If a vibe coder’s only goal is to build apps in short amounts of time so they can brag about how fast they built the app, they likely aren’t going to take the time to fix little things like that.

I don’t vibe code my apps that way, and I know many other vibe coders that aren’t that way—but we all started with actual coding, not typing a prompt.


Anyone can be a vibe coder, but not all vibe coders are developers

“And when everyone’s super… no one will be.” – Syndrome, The Incredibles. It might be from a kids’ movie, but it rings true in the era of vibe coding. When everyone thinks they can build an app in a weekend, everyone thinks they’re a developer.

By contrast, not every vibe coder is actually a developer, and that’s the problem. It’s hard to know if the app you’re using was built by someone who has plans to support the app long-term or not—and that’s why there’s going to be a lot of broken apps in the future.

I can see it now, the apps that people built in a weekend as a challenge will simply go without updates. While the app might work for the first few weeks or months just fine, an API update comes along and breaks the app’s compatibility. It’s at that point we’ll see who was vibe coding to build an app versus who was vibe coding just for online clout—and the sad part is, consumers will lose out more often than not with broken apps.



Source link