Anthropic is exploring building its own AI chips



The plans are early-stage and Anthropic may still decide to only buy chips rather than design them. The exploration comes days after the company signed a long-term deal with Google and Broadcom for 3.5 gigawatts of TPU compute starting in 2027. A company spokesperson declined to comment.


Anthropic is exploring the possibility of designing its own AI chips, Reuters reported on Thursday, citing three sources familiar with the matter. The effort is at an early stage: the company has not committed to a specific design and has not assembled a dedicated team for the project.

It may still decide to continue purchasing chips from third parties rather than building its own. A spokesperson for the San Francisco-based company declined to comment on the report.

The exploration comes as Anthropic’s revenue has accelerated sharply. The company disclosed earlier this week that its annualised revenue run rate has surpassed $30 billion, up from approximately $9 billion at the end of 2025.

That trajectory has created a scale of compute demand that makes the economics of custom silicon increasingly worth examining. Anthropic currently runs Claude across a mix of chips: tensor processing units designed by Alphabet’s Google, in partnership with Broadcom, alongside Amazon’s custom chips and Nvidia hardware.

The company said it matches workloads to whichever chips are best suited for them.

Just days before the Reuters report, Anthropic signed a long-term deal with Google and Broadcom that will give it access to approximately 3.5 gigawatts of TPU-based compute capacity from 2027, roughly three times the roughly one gigawatt it was consuming earlier in 2026, according to Broadcom’s SEC filing.

The filing flagged that the expanded deployment is contingent on Anthropic’s continued commercial success, an unusual hedge for a regulatory document. The deal builds on Anthropic’s November 2025 commitment to invest $50 billion in US computing infrastructure.

Broadcom is also already a chip design partner for OpenAI, and has a fifth undisclosed XPU customer, placing it at the centre of the custom AI silicon market that is emerging as an alternative to Nvidia’s general-purpose GPUs.

The possibility of Anthropic developing proprietary silicon mirrors moves already underway elsewhere in the industry. Meta has been building its own AI training chips, and OpenAI has been working on custom silicon as well.

Industry sources cited by Reuters put the development cost of an advanced AI chip at roughly $500 million, reflecting the need to hire specialised engineers and validate the manufacturing process.

That figure is not trivial for a company that remains, for now, unprofitable, but it is more manageable against a run-rate revenue base that has more than tripled in four months.



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