$3.5bn raise at $26.6bn valuation



Three days after suggesting it might target up to $4bn at $40bn, the AI chipmaker has marketed 28 million shares at $115-$125 each, lining the deal up with its February private valuation rather than above it.


Cerebras Systems was preparing to seek up to $4bn at a roughly $40bn valuation in its long-awaited initial public offering. On Monday, the company filed an updated prospectus that priced the deal more cautiously: 28 million shares at a marketed range of $115 to $125 each, raising as much as $3.5bn at the high end.

At that range, the implied valuation lands closer to $26.6bn, well below the figure circulating last week and roughly in line with the $23bn private mark Cerebras carried after its February Series H.

It is, by any reading, a more grounded number. Whether it is grounded enough is the question the order book will answer.

Per the updated prospectus filed on Monday, Cerebras intends to list on the Nasdaq Global Select Market under the ticker CBRS, with Morgan Stanley, Citigroup, Barclays and UBS Investment Bank as joint book-running managers.

The 28-million-share offering carries an underwriter option of an additional 4.2 million shares, which would lift gross proceeds by roughly $525m at the top of the range. CNBC notes that chief executive Andrew Feldman, the company’s co-founder, is not selling shares in the IPO; he will hold 10.3 million shares post-deal, worth as much as $1.28bn at the high end.

The financial profile underlying the offering is, by AI-hardware standards, well-developed. Cerebras’s most recent quarter showed revenue up roughly 76 per cent year-on-year to $510m, with $87.9m in net income.

The company’s Master Relationship Agreement with OpenAI, signed in January, promises up to 750 megawatts of inference capacity through 2028 in a contract Cerebras has previously valued at more than $20bn over its term. That deal, more than any single demonstration of wafer-scale technology, has anchored the IPO narrative since.

Why the valuation came down?

The shift from a possible $4bn raise at $40bn to a marketed $3.5bn at roughly $26.6bn is not, by IPO standards, dramatic. It is also not nothing. There are three plausible readings.

The first is execution. Filing at a wider range and a more sober valuation reduces the risk of an undersubscribed book on launch day, and it gives the deal room to price up if demand is strong. After two years in which AI hardware listings have priced below initial ranges as often as above, that discipline is sensible.

The second is market context. AI software multiples have been compressing through April, with Palantir down roughly 30 per cent year-to-date and Citi cutting price targets across the AI-platform space.

While Cerebras is hardware rather than software, hardware listings have not been immune to that broader recalibration. Pricing inside the now-public reference points for memory and compute is, again, sensible.

The third is concentration risk. Public-market investors, in their diligence on the prospectus, will have noted that OpenAI is the dominant customer in the deal. The economics, if OpenAI executes as planned, are formidable.

If OpenAI’s compute demand recalibrates, even modestly, Cerebras’s near-term revenue trajectory recalibrates with it. That risk does not go away at $26.6bn; it is, however, easier to underwrite at that figure than at $40bn.

What it would mean if it prices

If Cerebras prices at the high end of the range, the offering would be one of the largest US technology IPOs of 2026, ahead of any new entrant in AI silicon since Nvidia’s reignited public market presence three years ago.

Reuters and IFR have flagged the deal as a roughly $3bn raise in Nasdaq IPO terms; the precise number will depend on whether the underwriter overallotment is exercised and on the final pricing. Either way, this is the largest first-day public capital event in dedicated AI training and inference hardware to date.

It would also be a public test of a thesis Cerebras has built carefully over a decade: that its wafer-scale chip, an architecturally radical alternative to packing many smaller GPUs onto a board, is now commercially defensible at scale. The OpenAI contract is the most visible vote of confidence in that thesis. The IPO, if it prices in line, is the second.

The road from filing to first trade is not a formality. Cerebras’s earlier IPO attempt, in 2024, collapsed after the Committee on Foreign Investment in the United States opened a review of G42’s stake in the company; the eventual restructuring of that stake into non-voting shares cleared the way for the current attempt.

Public-market investors will have read that section of the risk factors closely. They will also have noted Cerebras’s customer concentration, the extent to which margin will depend on the cost of advanced packaging, and the strategic question of whether Nvidia’s next-generation accelerators erode the use cases Cerebras’s wafer-scale design currently serves best.

None of those is fatal. They are, however, the substance behind the lower valuation. Cerebras has filed a serious prospectus into a market that is, just at the moment, taking AI hardware more seriously than AI software. The rest is up to 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