AWS reportedly to tuck Elon Musk's Grok into Bedrock, despite zero enterprise demand
Jump to main content
Search
REG AD
AI + ML
AWS reportedly to tuck Elon Musk's Grok into Bedrock, despite zero enterprise demand
The energy drink of frontier models
Corey Quinn
Corey<br>Quinn
Special to El Reg
Published<br>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."<br>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.<br>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)<br>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.<br>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.<br>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.<br>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.<br>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.<br>So who asked for this?
REG AD
Nobody. Which is the interesting part.<br>When customer demand can't explain a decision, follow the corpdev. And AWS...