CUDA just got real on RISC-V. Here's how to capitalise on that limelight
In July 2025, Nvidia told the RISC-V Summit in China it would bring CUDA to RISC-V, so a RISC-V chip could act as the main processor in a CUDA-based AI system. It was a promise with no timeline. This month at Hot Chips 2026, the promise turned into a product: Nvidia published the technical bar a RISC-V platform has to clear (RVA23 compliance, vector extensions with predication, ACPI support via the newly ratified BRS spec, PCIe cache coherency), and SiFive demoed the BigSky SF-2U870, a rack server running RHEL 10 and CUDA on real workloads, available today. SiFive's CEO put it well: "RISC-V in the datacenter isn't a distant aspiration any more, it is happening right now." A year ago this was a slide. Now it's a spec sheet and a server you can order.
That's the news. What matters more for anyone working in or around RISC-V is what happens next, because a moment like this only comes along once or twice a year, and most of the ecosystem will let it pass by with a LinkedIn share and nothing else.
A rising tide raises all ships
This announcement doesn't just benefit Nvidia or SiFive. It's a credibility event for RISC-V as a category. Every company selling RISC-V IP, tooling, silicon, or services just got a stronger answer to the question every RISC-V vendor has been fielding for years: is this actually ready for serious compute, or is it still an embedded and edge story? Datacenter-class CUDA support, backed by a shipping server and a mainstream enterprise Linux distribution, is a genuinely different answer than the ecosystem had a year ago.
Search and AI answer engine interest in RISC-V as a category will tick up over the next few weeks, because interest in RISC-V-in-the-datacenter as a whole ticks up whenever a proof point like this lands, not just interest in Nvidia or SiFive specifically. Buyers who'd parked RISC-V as "watch this space" will go looking for more, and the companies who show up with something substantive when they look are the ones who benefit. The rising tide is real. Whether it lifts your ship in particular depends entirely on whether you're in the water when it comes through.
How to actually capitalise on it
Move in the window, not after it. The broad tech press covers a story like this for a few days, then moves on. There's then a two to four week window where people are still actively searching and asking AI tools about it, but almost nothing published so far actually explains the substance rather than repeating the announcement. That window is the opportunity. A same-week or same-fortnight piece that goes past the press release will outrank a more polished piece that shows up a month later, because both search and answer engines weight recency heavily on a live story.
Write for the next question, not the headline. The generic query "Nvidia CUDA RISC-V" is already crowded with rewrites of the same three facts. The gap is in what a technical buyer or engineer actually types next: does CUDA work on RISC-V yet, which RISC-V chips support CUDA, is RISC-V ready for AI datacenters, how does this compare to Arm for AI infrastructure, can I buy a RISC-V server that runs CUDA today. Build content that answers those directly, in plain sentences, and you're building for the question volume that's still coming rather than the one that's already spent.
Get named alongside the primary sources. RISC-V International, SiFive, and Red Hat are the accounts most likely to be treated as authoritative on this story by search and by AI answer engines. A piece that cites them accurately, links out properly, and adds something they didn't cover (a translation for a specific buyer audience, a caveat the coverage missed, a comparison the announcement didn't make) has a real shot at being picked up or referenced by the people already covering this space. That's worth more than any amount of keyword stuffing.
Make the honest caveat part of the pitch. BigSky ships in limited quantities. ACPI support has historically been patchy even on Arm after years of standardization, so the realistic read is narrower than "RISC-V datacenters have arrived": the technical blocker is gone and there's now a real product, not that this is mass-market yet. Naming that yourself, credibly, is what makes a piece trustworthy to an engineer and it's good practice for answer engines too, which tend to favor sources that show both sides rather than pure hype.
Turn one good piece into several formats while it's still current. A single well-researched explainer is the anchor. From it: a LinkedIn post making the sharpest single point (promise to production in a year is the strongest hook), a short technical breakdown of just the platform requirements for an engineering audience, and a follow-up comparison piece once competitors respond, because they will. One piece done properly beats three thin ones chasing the same keyword.
Connect it back to what you actually do. The highest-value version of this content isn't neutral commentary, it's commentary that lands on "here's what this means for you, and here's where we fit," whether that's IP, tooling, infrastructure, or services. That's the difference between a piece that gets read once and a piece that starts a conversation.
Structure it so both a person and a machine can use it. Clear headers that state a claim rather than a vague label, a direct answer near the top before the color and caveats, and the technical detail laid out plainly rather than buried in a paragraph. That's what a busy engineer scanning on their phone wants, and it's exactly what an AI answer engine is looking for when it picks a passage to cite.
The tide is rising for the whole ecosystem right now. The companies that publish something real on this in the next couple of weeks, rather than a share and a hot take, are the ones whose ships actually go up with it.
The legacy vendor AI repositioning problem
There is a particular kind of pressure that doesn't get talked about in deep tech marketing conversations, because the companies feeling it most acutely are the ones least likely to admit it publicly.
They've been in market for twenty, thirty years. They have real customers, real revenue, and a reputation earned the hard way across generations of product cycles. And somewhere in the last two years, the conversation shifted. The buyers they've been selling to are now asking a different set of questions. The competitors they've spent years outmaneuvering have repositioned as AI companies. The analysts who used to write about them in predictable ways are starting to frame the category differently.
The problem isn't that these companies don't have an AI story. Most of them do. But like everyone else who stamped AI on their product, it sounds like everyone else's.
There's a version of AI repositioning that almost every legacy vendor defaults to. They take the existing product description, add the words 'AI-powered' or 'AI-enabled', update the website headline, and brief the PR team to find an AI angle for the next product launch. It ticks the box. It does not move the market. I’ll admit I’ve been asked ‘Can you make this more AI-washed?’ and the best answer in my experience tends to be ‘no’.
The reason it doesn't work is that technically sophisticated buyers; the CTOs and architects and procurement leads at the OEMs and hyperscalers and enterprise customers that these companies are trying to reach have seen this exact skulduggery from fifteen different vendors in the past eighteen months. They know what it looks like, they have a filter for it and when your repositioning looks like wallpaper, you don't just fail to gain credibility — you actively lose it, because the attempt signals that you don't have a story worth telling.
What Arm went through is a useful reference point. The business had built its position over three decades on a clear, defensible model: IP licensing to chip designers who built the hardware that everyone else then built on top of. That model was well understood. The relationships built around it were real and deep. And then the AI infrastructure buildout created a moment where the architecture question — what compute is the world's most demanding AI workloads going to run on — was genuinely up for grabs.
The challenge wasn't technical. Arm's position in AI infrastructure was already strong. NVIDIA runs on Arm. AWS, Google, Microsoft, and Meta were all building custom silicon on Arm Neoverse. The trajectory was there, but the challenge was commercial: how do you reposition as a company at the center of the AI infrastructure story without disrupting the licensing relationships that built the business, and without making claims that your ecosystem of partners will immediately fact-check and find wanting?
The answer wasn't a campaign. The proof points that were specific, verifiable and credible to a technical audience. The broader narrative came second, built around those proof points rather than built in advance of them. And the message was calibrated differently for each audience: for the investor, the story was about where AI compute was concentrating and why Arm's architecture was structurally advantaged; for the OEM and the chip designer, the story was about what specifically had changed in the tools, the ecosystem, and the programme support available to them.
That sequencing, with proof before narrative, and different narrative for each seat is what most legacy vendor AI repositioning gets wrong. The instinct is to announce the position before the proof is assembled, because the competitive pressure feels urgent and the board wants to see something in market. The result is a claim without substance reaching the exact audience most skilled at identifying claims without substance.
The other failure mode is narrowing too early. Legacy vendors often try to claim AI relevance in the specific product category they already occupy, because that's the safest ground. What they miss is that the more interesting and defensible AI story is often structural — about where they sit in the supply chain, what they enable that nothing else can, and why the AI transition makes that position more valuable rather than less. That's a harder argument to make, but it's the one that lands with the buyers and investors who are trying to understand what the next five years look like.
The companies getting this right are the ones who've accepted that AI repositioning is not a marketing exercise. It's a commercial strategy question that marketing then has to express. The sequence is: understand where you actually sit in the AI value chain, build the proof that substantiates that position, then build the narrative. In that order. Reversed, it produces exactly the kind of repositioning the market has learned to ignore.
Dale Kaszycki is a Co-Founder of Latent