Open-Source RISC-V AI Silicon: What It Actually Means for Local Inference

If you are building a local AI inference stack, you now have a $999 alternative to NVIDIA with an entirely open-source software stack. Here is what the evidence actually supports.

If You Only Have 30 Seconds

  • Production AI inference cards built on open-source RISC-V architecture are shipping at $999 with a fully open-source software stack.
  • The architecture uses a fundamentally different approach from NVIDIA: distributed mesh of small cores, GDDR6 instead of HBM, standard Ethernet instead of proprietary interconnects.
  • Performance claims (3x faster than GPUs) have not been independently verified. No MLPerf results exist.
  • If you are building local inference infrastructure with a 6+ month timeline, evaluate it. If you are in production on NVIDIA today, track your CUDA dependencies but do not switch yet.
  • The technology is real and shipping. The commercial proof is incomplete. The strategic implications for sovereign AI are significant.
Orbit's 60-Second Explanation
Here is the short version. For twenty years, if you wanted to run AI on hardware, you used NVIDIA chips and NVIDIA software called CUDA. That created a situation where switching to anything else was extremely expensive, not because the hardware was irreplaceable, but because all your software and all your engineers' skills were built on NVIDIA's proprietary system.

Now there is a chip that uses an open instruction set (RISC-V, meaning nobody owns it), runs an open-source software stack (meaning you can inspect and modify everything), and costs a thousand dollars instead of thirty thousand. The catch? Nobody independent has verified the performance claims yet. It might be great. It might be adequate. We genuinely do not know.

A thousand dollars is a cheap experiment. Run your actual workload on it and find out.

The Question That Matters

If you are building a local AI inference stack today, you face a single vendor for serious AI silicon: NVIDIA. You pay NVIDIA prices, you use NVIDIA software (CUDA), you accept NVIDIA's roadmap, and you hope NVIDIA continues to prioritize your market segment. For most of the past decade, this was not a choice. It was the only option.

That is starting to change. A new class of AI processors built on open-source architectures is reaching production. The most advanced of these uses RISC-V (an open instruction set architecture) for both its AI accelerator cores and its host CPU, runs an entirely open-source software stack, and sells inference cards for under $1,000. The question is whether this matters to you, or whether it is another "NVIDIA killer" that will quietly disappear in two years.

This article explains the technology, the architecture, the tradeoffs, and what you should actually do about it.

What RISC-V Is (And Why It Matters for AI Silicon)

RISC-V is an open-standard instruction set architecture (ISA) maintained by RISC-V International. Unlike x86 (owned by Intel/AMD) or ARM (licensed by Arm Holdings), RISC-V can be implemented by anyone without paying licensing fees or requesting permission [1]. This is not a minor detail. It means:

A chip designer in Tokyo, Toronto, or Taipei can build a processor without negotiating a license agreement with a company in California or Cambridge. A nation building sovereign AI infrastructure can manufacture processors without depending on a foreign licensor's continued goodwill. A startup can tape out silicon without the $5M to $15M ARM license fee that historically gated entry into processor design.

For AI specifically, RISC-V matters because it allows chip architects to extend the instruction set with custom operations optimized for neural network workloads. You are not constrained by what Intel or ARM decided their ISA should do [2].

The CUDA Problem

Understanding why open-source AI silicon matters requires understanding why NVIDIA's dominance is not primarily about hardware. NVIDIA's moat is software.

CUDA is NVIDIA's proprietary parallel computing platform. It has been in development since 2006. It has twenty years of libraries, tools, debuggers, profilers, and community knowledge. Every major AI framework (PyTorch, TensorFlow, JAX) has deep CUDA integration. Every AI researcher's muscle memory is built on CUDA [3].

This creates a lock-in that transcends hardware specifications. Even when a competitor produces silicon that matches or exceeds NVIDIA on raw performance metrics, the cost of rewriting software, retraining engineers, and re-validating production pipelines keeps organizations on CUDA. The switching cost is measured in engineering years, not dollars.

CUDA lock-in cycle: skills lead to libraries lead to hardware lead to investment, with open-source stack as exit ramp
Figure 2: The CUDA lock-in cycle. Each investment reinforces the next. An open-source stack provides an exit ramp.

An open-source software stack attacks this problem differently than a proprietary alternative (like AMD's ROCm). Instead of asking organizations to trust a different single vendor, it creates a commons that any organization can inspect, modify, contribute to, and fork if necessary.

How the Architecture Actually Works

The most production-ready open-source AI silicon today is Tenstorrent's Blackhole processor. Rather than simply describing specifications, it is worth understanding the architectural philosophy, because it represents a genuinely different approach to AI compute.

The Tensix Core

Where NVIDIA builds large, monolithic streaming multiprocessors (SMs) that share memory hierarchies, Blackhole uses a mesh of smaller, independent processing units called Tensix cores. Each Tensix core contains a matrix engine (for the multiply-accumulate operations that dominate neural networks), a vector unit (for activation functions and normalization), and five small RISC-V cores that handle scheduling and data movement [4].

These cores communicate over a 2D network-on-chip (NoC) mesh. There is no shared global memory in the traditional sense. Each core has its own local SRAM, and data moves between cores via explicit message passing over the mesh.

ComponentBlackhole Specification
Tensix Cores120 (reduced from 140 via firmware, Jan 2026) [5]
On-chip SRAM180 MB total (distributed across cores)
External Memory28-32 GB GDDR6 at 448-512 GB/s
Compute664 TFLOPS (BLOCKFP8)
Host CPU16 x 64-bit RISC-V cores (can run host-less)
Chip-to-chip10 x 400 Gbps Ethernet (1 TB/s aggregate)
Process NodeTSMC 6nm
Power300W
Price$999 (p100a) / $1,399 (p150a/b)

Source: Tenstorrent official specifications [6]

Architecture comparison: NVIDIA GPU with shared L2 cache and HBM versus Tenstorrent Blackhole with distributed Tensix cores, 2D mesh, and GDDR6
Figure 1: Architectural comparison. GPU uses shared memory hierarchy; Blackhole uses distributed mesh of independent cores.

The Anti-HBM Bet

Most high-end AI accelerators use High Bandwidth Memory (HBM), which provides enormous bandwidth but costs significantly more per gigabyte. Blackhole deliberately uses GDDR6 instead, trading peak bandwidth for lower cost and simpler board design [7]. This is a bet that large on-chip SRAM (180 MB) combined with intelligent data scheduling can compensate for lower external memory bandwidth.

The Anti-NVLink Bet

NVIDIA connects GPUs within a server using NVLink, a proprietary high-bandwidth interconnect. Blackhole uses standard Ethernet. Each chip has 4 Tbps of Ethernet connectivity built directly into the silicon [8]. This means systems scale using commodity networking infrastructure. No proprietary switches, cables, or topologies.

The Anti-Disaggregation Bet

The current industry trend is to disaggregate AI inference: use one type of hardware for prefill and another for decode. Tenstorrent's CEO Jim Keller has explicitly bet against this:

"The big fad is disaggregation, special purpose hardware, SRAM. Do you know how many people are going to be talking about that in 2 years? None." [9]

Blackhole runs both prefill and decode on the same silicon. This simplifies deployment but means it may not match specialized hardware on either phase individually.

What Has Been Proven and What Has Not

Evidence scorecard: shipping, open-source, and model support are proven; performance and cost claims are unproven; reliability is too early
Figure 3: Evidence scorecard. Green items are independently verifiable. Yellow items are vendor claims without independent confirmation.
ClaimStatusEvidence
Cards are shipping and purchasableProvenMultiple retailers, customer deployments confirmed
Software stack is open sourceProvenGitHub repositories are public, MIT licensed
Runs major open-weight modelsProvenDemonstrated at events; ~90% HuggingFace compatibility claimed
Performance exceeds NVIDIA on inferenceUnprovenNo MLPerf submission; all benchmarks vendor-reported [10]
Cost per token is lower than NVIDIAUnprovenNo independent TCO analysis published
Architecture scales to frontier modelsPartially proven120+ Galaxy systems deployed in Japan; DeepSeek 671B running
Long-term reliability in productionToo earlyGA since April 2026; insufficient time for reliability data

What You Should Do

If You Are...Then You Should...
Building a new local inference stack with 6+ months before productionEvaluate Blackhole cards ($999) alongside NVIDIA. Run your specific models on both. Measure on your workload, not vendor benchmarks.
Already running NVIDIA in production with no issuesDo nothing today. Monitor quarterly. Begin tracking your CUDA dependencies so you understand your lock-in surface area.
A startup choosing first inference hardwareStart with NVIDIA for time-to-market. Write your pipeline to be hardware-agnostic where possible (ONNX, framework abstractions).
Building sovereign or air-gapped AI infrastructureEvaluate open-source silicon seriously. The ability to inspect, modify, and independently manufacture your compute stack may outweigh raw performance.
An investor or analystWatch for independent benchmarks (MLPerf), a hyperscaler deployment, and the Quasar next-gen chip. The technology is real; commercial validation is incomplete.

RynX Perspective

Open-source AI silicon matters to RynX because local inference independence is a core engineering principle. The ability to run AI workloads without depending on a single vendor's software ecosystem, pricing decisions, or export-control status is not an abstract concern for organizations building sovereign or safety-critical AI systems. It is an operational requirement.

We do not yet use Tenstorrent hardware in production. The evidence base is insufficient to justify migration from proven infrastructure. But we are tracking the ecosystem closely because the architectural properties (open ISA, open software, commodity networking, host-less operation) align with what local and physical AI deployments actually need.

This section represents RynX interpretation and opinion, not independently verified fact.

What We Are Watching

Five specific developments would change this analysis:

DevelopmentWhy It Matters
MLPerf submission or equivalent independent benchmarkResolves the performance question definitively
Hyperscaler or frontier lab deploymentValidates reliability and scale beyond neoclouds
Quasar (next-gen chip) tape-out on advanced nodeDetermines whether architectural bets hold at higher performance
Qualcomm acquisition outcomeChanges the competitive landscape and support structure
12-month production reliability data from ai& deploymentAnswers the durability question that no benchmark can

Sources

  1. RISC-V International. "About RISC-V." riscv.org/about. Accessed August 6, 2026.
  2. Patterson, D. and Waterman, A. "The RISC-V Reader: An Open Architecture Atlas." 2017.
  3. NVIDIA. "CUDA Toolkit Documentation." docs.nvidia.com/cuda. Accessed August 6, 2026.
  4. The Register. "Tenstorrent Blackhole AI Chip Architecture." August 27, 2024.
  5. Tom's Hardware. "Jim Keller's Tenstorrent Is Downgrading Blackhole P150 Cards." January 2026.
  6. Tenstorrent. "Blackhole Hardware Specifications." tenstorrent.com/hardware/blackhole. Accessed August 6, 2026.
  7. Tenstorrent. TT-Deploy Keynote. "Architecture Overview." May 2026.
  8. Tenstorrent. "Networked AI Architecture." tenstorrent.com. Accessed August 6, 2026.
  9. Keller, Jim. TT-Deploy SF Keynote. May 2026.
  10. MLPerf v6.0 Results. mlcommons.org/benchmarks. Accessed August 6, 2026. (Tenstorrent absent.)
  11. Tenstorrent and ai&. "TT-Deploy JP Announcement." tenstorrent.com/newsroom. June 30, 2026.
  12. Stanford HAI. "The Commercial Landscape of AI Sovereignty Offerings." July 15, 2026.

Related Reading

More articles coming soon. The RynX Journal publishes one strong article per week when quality permits.

Reviewed and approved by RynX. Final editorial responsibility rests with RynX.