AWS reportedly to tuck Grok into Bedrock, despite zero enterprise demand

AWS reportedly to tuck Elon Musk's Grok into Bedrock, despite zero enterprise demand

The energy drink of frontier models

Corey Quinn

Corey Quinn

Special to El Reg

Published fri 29 May 2026 // 23:23 UTC

A security lead at a large enterprise* told me last week, when I asked whether they had any interest in Grok: "The revenge porn edgelord LLM? Yeah, imagine that; our bank wants nothing to do with it."

A couple of other people I put the question to seemed genuinely surprised I'd brought it up at all, the way you'd react if someone wandered into a board meeting and asked whether anyone wanted to expense a timeshare.

So that's the current state of enterprise demand for Grok, as measured by the unscientific but reliable method of asking the people who actually sign the cloud contracts. It lands somewhere between "no" and "why would you ask me that?"

REG AD

Which is awkward, because Business Insider reported this week that AWS is "in talks" to add SpaceX's Grok models to Bedrock, joining Anthropic, Meta, Cohere, and the OpenAI models AWS is in the process of bolting on. SpaceX has reportedly already shipped the models to AWS. There's no launch date, which in AWS announcement terms puts us squarely at the "intention to perhaps one day announce an announcement" stage.

REG AD

But is it any good? (No)

Let me dispatch the obvious objection: maybe nobody wants Grok because they haven't tried it, and it's secretly excellent. I've run blind tests of the frontier models on some of my own deeply stupid side projects—the shitposting.ai family, where the entire design goal is to be edgier and weirder than the current discourse will tolerate. If there's a use case purpose-built to let Grok flex its whole "we say the things others won't" positioning, it's mine.

MORE CONTEXT

AIs don't like religion – particularly Jehovah's Witnesses, study claims

SpaceX pitches itself as integrated interplanetary proto-monopolist in IPO filing

Amazon put a filesystem on S3; I showed up with a test suite and bad intentions

AWS plants more tombstones in the application graveyard

Grok loses. It's fast — legitimately, impressively fast — but it's just not as good. It's the energy drink of frontier models: it'll keep you up, but you won't enjoy the experience and you'll regret it in the morning.

So we've got a model that enterprise buyers actively don't want, that underperforms even on the single axis it's purportedly optimized for, attached to a company whose image generator reportedly was used to produce roughly three million sexualized images of real people over an eleven-day stretch, including an estimated 23,000 depicting apparent minors, according to the Center for Countering Digital Hate, triggering regulatory action in more than a dozen jurisdictions and a Dutch court injunction carrying a €100,000-per-day penalty. That part isn't a joke, and I'm not going to make one.

Then layer on the fact that nobody sensible wants to take a hard dependency on Elon Musk's org chart. In roughly a year, the thing has been reorganized into oblivion — X (the rebranded Twitter) sold to Grok-producing xAI, xAI swallowed by SpaceX, with the whole AI unit then being dissolved into a division called SpaceXAI. All eleven original cofounders have left. More than fifty researchers walked after the SpaceX absorption. The API endpoint you'd integrate against, api.x.ai, is migrating to a SpaceX-branded URL on a timeline nobody's published. Building production infrastructure on top of that is like renting an apartment in a building that keeps changing its name, its address, its compliance with the fire code, and its landlord while you're still unpacking.

And here's the part that should bother whoever greenlit this. Bedrock's entire pitch— the reason anyone pays the wrapper tax instead of hitting a model's API directly— is governance: IAM, PrivateLink, CloudTrail, encryption, guardrails, and an audit trail you can wave at a regulator. The model is almost secondary to those things for those customers. And the enterprises that actively value that stack are precisely the ones telling me they wouldn't touch Grok with a borrowed keyboard.

The startups that hypothetically *do* want Grok — for the edge, for the speed, for whatever a founder talks themselves into at 2 a.m. — could not care less about CloudTrail. They want it cheap, fast, and now, and they can already have it: Grok is one curl to a public endpoint away, same as every other model on the shelf. Bedrock has no monopoly on third-party models; it never did. So sketch the Venn diagram. One circle is "wants Grok," the other is "wants Bedrock's governance." Grok-on-Bedrock is built to serve only the gap where they don't overlap.

So who asked for this?

REG AD

Nobody. Which is the interesting part.

When customer demand can't explain a decision, follow the corpdev. And AWS has run this exact play twice already this year, in public, with the numbers attached.

With Anthropic: a commitment to spend more than $100 billion on AWS over ten years and secure up to five gigawatts of Trainium capacity, with Amazon putting in another $5 billion immediately and up to $20 billion more on milestones — on top of the $8 billion it had already sunk in, for a cumulative stake somewhere around $33 billion.

With OpenAI: an existing $38 billion agreement expanded by another $100 billion, OpenAI committing to roughly two gigawatts of Trainium, and Amazon writing a $50 billion check on top.

The pattern is identical both times. Amazon invests, the lab commits to gigawatts of Trainium, and the model shows up on Bedrock as the consumer-facing bow on top. The Bedrock listing is the gift wrap. The Trainium commitment is the gift.

So here's the way I'm thinking about it: AWS isn't trying to sell Grok to your bank, but rather trying to sell Trainium to SpaceXAI — a company currently training Grok on something like 550,000 Nvidia GPUs in a Memphis facility the size of the chip on my shoulder. Peel even a fraction of that onto Amazon silicon ahead of the SpaceX IPO and the deal pencils out, regardless of whether a single human ever calls the Grok endpoint in anger. Bedrock becomes little more than a sales funnel with infuriatingly bad documentation.

The part where I say something nice

Because the strategy is clever, and I try to say so when it's earned. Amazon is now bankrolling both leading independent AI labs at once, on its own chips, through its own model marketplace, while positioning itself as neutral infrastructure for whoever ends up winning. Against the roughly $200 billion in capex Amazon is torching in 2026, getting frontier labs to pre-commit to the silicon is about the only thing that makes that spreadsheet survivable. It worked twice. Why not go for three?

REG AD

The third just happens to be a satellite-internet competitor. Amazon Leo - Amazon's own years-later answer to Starlink - is out there signing Delta, JetBlue, AT&T, Vodafone, and NASA. So AWS would be cutting a relationship check to the one company it's simultaneously trying to chase out of low Earth orbit. This seems fine. This is normal! Everybody in this industry is everybody else's landlord, tenant, competitor, and shelf-mate, frequently within the same quarter and occasionally within the same press release. There will never be a problem that this arrangement causes.

The caveat that keeps me honest

I have no inside information here past "casual conversations with enterprise execs." I haven't seen a term sheet. There's no public Trainium commitment from SpaceXAI, and Colossus runs on Nvidia today. So I can't prove this is silicon corpdev rather than, say, AWS executives wanting a seat at the IPO table, or a marketing org that needs to put "every frontier model" on a slide. What I can tell you is that customer demand doesn't explain it, because there isn't any - and AWS has shown you, twice and with receipts, what its other explanation tends to look like.

So when Grok eventually lands on Bedrock with no fanfare and no launch date, and then is never mentioned again, don't read it as AWS believing you want Grok. Read the S-1. If there's a Trainium number in it, you'll know what the model was really for.

• Specifics have been fuzzed to protect confidentiality. ®