---
title: "Phison's AI SSD: What an NPU Inside the Drive Changes"
slug: "phison-ai-ssd-npu-computational-storage-sc26"
author: "Miguel Amigot"
date: "2026-11-22 12:00:00"
category: "Premium"
sector: "cross"
topics: "Phison, computational storage, AI SSD, NPU, near-data inference, on-device AI, self-hosted AI, AI infrastructure"
summary: "At SC26 on November 17, 2026 Phison previewed a computational-storage SSD with an integrated NPU and 64 GB of 130 GB/s memory. It is still in development, with no product name or sample date, and it moves filtering to the data rather than replacing GPUs."
banner: ""
thumbnail: ""
linkedin: |
  "Phison just put an AI processor and 64GB of memory inside the SSD" is going around. Phison's own SC26 release, dated November 17, 2026, says something narrower — and the narrower version is the useful one.

  What Phison actually described is a computational-storage architecture: an integrated NPU, 64 GB of memory at 130 GB/s, and support for PyTorch, vLLM, OpenVINO and llama.cpp running on the drive.

  → It is not shipping. Phison says many of the products are still in development; there is no product name and no sample date
  → It does not eliminate data movement. Phison claims a potential 10–100x reduction in data transfers for applicable workloads
  → It does not replace a GPU. 130 GB/s is roughly 4% of an H100 SXM's 3.35 TB/s, and decode speed is bounded by memory bandwidth
  → What it can do: filter, embed and pre-process data where it sits, so only the useful slice crosses the bus

  The direction is real — compute moving toward data. Where the data lives still decides who controls it.

  With ibl.ai you own all the code and the data — model-agnostic across any LLM, no per-seat pricing, deployable anywhere from your own cloud to a fully air-gapped network.

  #iblai #AgenticAI #EnterpriseAI #AIInfrastructure #ComputationalStorage #OnDeviceAI
---

## The Short Answer

**Phison did not ship an AI SSD. At SC26 on November 17, 2026 it previewed an unnamed computational-storage design: an NPU and 64 GB of 130 GB/s memory inside the drive, running PyTorch, vLLM, OpenVINO and llama.cpp, with no sample date. It is a data-movement play, not a GPU replacement. On ibl.ai you own all the code and the data, wherever inference runs.**

The viral version says "no GPU cluster, no data movement." Phison's own release claims fewer data transfers for suitable workloads, which is a smaller and more defensible statement.

## What exactly did Phison announce at SC26?

Phison announced three storage technologies in [a release dated Chicago, November 17, 2026](https://www.phison.com/sc26-phison-unveils-three-next-generation-storage-innovations-for-the-new-compute-era/), timed to Supercomputing 2026. Only one of them is the "AI inside the SSD" story.

The computational-storage design pairs an integrated NPU, rated by Phison at **36,800 DMIPS**, with **64 GB of memory at 130 GB/s**.

Phison says it supports PyTorch, vLLM, OpenVINO and llama.cpp, and claims a potential **10–100x reduction in data transfers** for applicable workloads, with lower host CPU use.

The other two announcements were a PCIe Gen6 enterprise controller, the X3 (PS5303), targeting up to 28 GB/s and 6.8 million IOPS, and a "Mixed Media" drive that puts pSLC and QLC flash behind one 16-channel controller.

<table style="width:100%; border-collapse:collapse; margin:1.5rem 0; font-size:0.95rem;">
  <thead>
    <tr style="background:#f5f5f0; border-bottom:2px solid #2175C5;">
      <th style="text-align:left; padding:0.75rem; color:#5f6368;">What the viral post says</th>
      <th style="text-align:left; padding:0.75rem; color:#5f6368;">What Phison's release says</th>
    </tr>
  </thead>
  <tbody>
    <tr style="border-bottom:1px solid #e5e7eb;">
      <td style="padding:0.75rem;">Phison "just put" an AI processor in the SSD</td>
      <td style="padding:0.75rem;">An architecture previewed at SC26; "many of the products and features mentioned are still in development"</td>
    </tr>
    <tr style="border-bottom:1px solid #e5e7eb;">
      <td style="padding:0.75rem;">An AI processor + 64GB memory</td>
      <td style="padding:0.75rem;">Accurate: an integrated NPU and 64 GB of memory at 130 GB/s</td>
    </tr>
    <tr style="border-bottom:1px solid #e5e7eb;">
      <td style="padding:0.75rem;">No data movement</td>
      <td style="padding:0.75rem;">A potential 10–100x reduction in data transfers, for applicable workloads</td>
    </tr>
    <tr style="border-bottom:1px solid #e5e7eb;">
      <td style="padding:0.75rem;">No GPU cluster</td>
      <td style="padding:0.75rem;">Not claimed. The release describes fewer data transfers and lower host CPU use</td>
    </tr>
  </tbody>
</table>

Two of the four claims hold up. The two that do not are the ones a hardware budget would be built on.

## Is Phison's AI SSD a shipping product, and is it the same thing as aiDAPTIV+?

No on both counts. [Tom's Hardware's November 20, 2026 write-up](https://www.tomshardware.com/pc-components/ssds/phison-details-ssd-with-a-built-in-npu-and-64gb-of-memory-that-supports-pytorch-and-llama-cpp-running-on-the-drive-second-design-merges-fast-pslc-cache-and-qlc-capacity-behind-one-controller) notes the design has no product name, no named controller and no sample date.

The same report lists what Phison left undisclosed: the memory type, form factor, power draw, a TOPS rating, how a host reaches the drive's compute, and which model sizes it supports.

It also flags that **36,800 DMIPS** is a decades-old integer CPU benchmark, not an AI throughput figure, and may describe the companion CPU cores rather than the NPU. Treat it as saying little about AI performance.

It is also distinct from [Phison's aiDAPTIV+](https://www.phisonenterprise.com/pascari-aidaptiv/), the product many readers will remember.

aiDAPTIV+, now sold as Pascari aiDAPTIV, uses flash and system memory to extend the memory a GPU can use, so larger models run than GPU memory alone would hold. The SC26 design does the opposite: it runs compute on the drive itself.

Computational storage is not new either. Tom's Hardware cites Samsung's SmartSSD and ScaleFlux as earlier designs in the same category.

## Can a 64 GB NPU inside an SSD run a large language model?

It can hold a small or quantized one, but memory bandwidth caps how fast it generates. For a dense model, producing each token means reading every weight once, so tokens per second cannot exceed bandwidth divided by the model's size in bytes.

That ceiling is simple arithmetic, and it is ours, not Phison's. Phison published no inference throughput. Real throughput lands below the ceiling once compute, the KV cache and overhead are counted.

<table style="width:100%; border-collapse:collapse; margin:1.5rem 0; font-size:0.95rem;">
  <thead>
    <tr style="background:#f5f5f0; border-bottom:2px solid #2175C5;">
      <th style="text-align:left; padding:0.75rem; color:#5f6368;">Dense model, 4-bit weights</th>
      <th style="text-align:right; padding:0.75rem; color:#5f6368;">Weights</th>
      <th style="text-align:right; padding:0.75rem; color:#5f6368;">Ceiling at 130 GB/s (Phison drive)</th>
      <th style="text-align:right; padding:0.75rem; color:#5f6368;">Ceiling at 3.35 TB/s (H100 SXM)</th>
    </tr>
  </thead>
  <tbody>
    <tr style="border-bottom:1px solid #e5e7eb;">
      <td style="padding:0.75rem;"><strong>8B parameters</strong></td>
      <td style="text-align:right; padding:0.75rem; font-variant-numeric:tabular-nums;">~4 GB</td>
      <td style="text-align:right; padding:0.75rem; font-variant-numeric:tabular-nums;">~32 tokens/s</td>
      <td style="text-align:right; padding:0.75rem; font-variant-numeric:tabular-nums;">~840 tokens/s</td>
    </tr>
    <tr style="border-bottom:1px solid #e5e7eb;">
      <td style="padding:0.75rem;"><strong>70B parameters</strong></td>
      <td style="text-align:right; padding:0.75rem; font-variant-numeric:tabular-nums;">~35 GB</td>
      <td style="text-align:right; padding:0.75rem; font-variant-numeric:tabular-nums;">~3.7 tokens/s</td>
      <td style="text-align:right; padding:0.75rem; font-variant-numeric:tabular-nums;">~96 tokens/s</td>
    </tr>
  </tbody>
</table>

The H100 figure is NVIDIA's [published 3.35 TB/s for the H100 SXM](https://www.nvidia.com/en-us/data-center/h100/). The drive's 130 GB/s is about 4% of that.

So a 70B model fits in 64 GB at 4-bit, but a ceiling of under four tokens a second is not an interactive chat service. "No GPU cluster" holds only for work that was never going to need one.

## What workloads does near-data inference actually suit?

Work where the expensive part is moving data, not generating text. Phison's own framing is a reduction in data transferred to the host, which points at filtering, classification, embedding and pre-processing over large stored datasets.

The pattern is a scan that would otherwise ship terabytes across the bus so a host can discard most of it. If a small model on the drive can tag, filter or embed records in place, only the useful slice travels, and that is where a 10–100x transfer reduction is plausible.

A retrieval pipeline is the natural fit: embedding documents where they sit, then sending vectors rather than raw files to the serving tier.

The generating model still runs where bandwidth is high. For that tier, the [self-hosted LLM serving stack](/blog/self-hosted-llm-serving-stack-ollama-vllm-tgi) — vLLM or TGI on dedicated GPUs — stays the answer.

This is the same honest boundary as [NVIDIA's PAIR, which routes requests rather than pooling GPU memory](/blog/nvidia-pair-personal-ai-router-local-inference-cluster): local and near-data inference change where work runs, not how large a model one device can serve quickly.

## Does moving AI compute to the data change enterprise AI cost?

It changes the hardware line, and it makes a pricing argument plain. Compute inside a drive you already own has no seat count in it. Its cost is the hardware and the electricity, and it does not move when you hire.

Per-seat AI licensing bills headcount regardless of use. Microsoft 365 Copilot is [listed at $30 per user per month on an annual commitment](https://www.microsoft.com/en-us/microsoft-365-copilot/pricing/enterprise), which is $720,000 a year at 2,000 employees whether those seats send one request a day or none.

Per-seat is structurally the wrong shape for AI at scale, not one pricing option among several. The more inference migrates into hardware the enterprise owns, from GPUs to NPUs to storage, the less a headcount-multiplied bill describes what is actually being consumed.

## Does in-storage AI make enterprise AI more sovereign?

Only if the drive sits on infrastructure you control. Near-data processing shortens the path data travels inside one server; it does not decide whose server that is.

A drive with an NPU in a hyperscaler's rack is still the hyperscaler's hardware. A drive in your own data centre was already inside your perimeter before it gained an NPU.

What on-drive compute adds is one more place where software runs against your data, and that software has to be governed like any other. Phison has not said how a host reaches the drive's compute, which is exactly the detail a security review will ask for.

Sovereignty is decided by who owns the stack and where it runs. Storage-level compute is a performance feature that a sovereign deployment can use, not a substitute for one.

## How does ibl.ai fit near-data and on-device inference?

On ibl.ai you own all the code and the data. The platform runs on your infrastructure with full source code, is **model-agnostic** across any LLM, has **no per-seat pricing**, and can **deploy anywhere**: your own cloud, on-premise, GovCloud, or a fully air-gapped network.

Inference placement is already an operator decision on the platform. The [September 4, 2026 platform update](/updates/platform-update-2026-09-04) shipped an on-device LLM provider picker, so an operator chooses where a given agent's inference runs, alongside hosted providers.

When computational storage reaches products with published interfaces, it becomes one more placement option under the same rule: the data stays where you put it, on hardware you control. 1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY.

*Related reading: [NVIDIA's PAIR is a router, not an inference cluster](/blog/nvidia-pair-personal-ai-router-local-inference-cluster) and [self-hosted LLM providers: Ollama vs vLLM vs TGI vs LocalAI](/blog/self-hosted-llm-serving-stack-ollama-vllm-tgi).*

*Sources: the NPU, 64 GB / 130 GB/s memory, framework list, 10–100x claim, X3 and Mixed Media details and the in-development disclaimer from [Phison's SC26 release](https://www.phison.com/sc26-phison-unveils-three-next-generation-storage-innovations-for-the-new-compute-era/); the missing product name and sample date, the undisclosed details, the DMIPS caveat and the SmartSSD and ScaleFlux precedents from [Tom's Hardware](https://www.tomshardware.com/pc-components/ssds/phison-details-ssd-with-a-built-in-npu-and-64gb-of-memory-that-supports-pytorch-and-llama-cpp-running-on-the-drive-second-design-merges-fast-pslc-cache-and-qlc-capacity-behind-one-controller); aiDAPTIV+ from [Phison](https://www.phisonenterprise.com/pascari-aidaptiv/); H100 bandwidth from [NVIDIA](https://www.nvidia.com/en-us/data-center/h100/); Copilot pricing from [Microsoft](https://www.microsoft.com/en-us/microsoft-365-copilot/pricing/enterprise). Token-rate ceilings are our arithmetic, not vendor figures.*

## Why does owning the AI stack matter?

**ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.**

- **You own all the code and the data.** Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform — the stack itself is yours.
- **Model-agnostic.** Run any LLM — Claude, GPT, Gemini, Llama, Command, or your own fine-tune — and switch providers without rewriting the platform.
- **No per-seat pricing.** Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.
- **Deploy anywhere.** Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.

1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.
