The direct answer
What does AMD describe? A Kria AI SOM family using Ryzen AI Embedded X100 Series processors on COM-HPC, plus a developer platform combining a SOM with an FPGA-equipped carrier and sensor or communication interfaces.
What do the four headline numbers establish? They establish nothing directly about an orderable Kria AI SOM. The 234-agent and 2.3× claims point to a modeled sweep; 8,000 decisions/s points to a Bosch Rexroth controller result on X100 Series; the 3.4× and 1.6× comparisons point to a GMKtec EVO-X2 system configured to reflect X199 specifications.
What did RCI validate? RCI traced fourteen claim and provenance observations and twelve disclosure fields. It ran zero modules, controllers, software stacks, benchmarks or robots.
The audited AMD surfaces define a new compute-family direction and several claimed platform features. They do not yet provide an exact-model record whose headline benchmark values were measured on that named module.
The launch page describes a family, not one exact model
The page says Kria AI SOMs will use Ryzen AI Embedded X100 Series processors and be available through an AMD partner ecosystem. It highlights up to 128 GB LPDDR5x unified memory, sixteen Zen 5 CPU cores, eight FAKRA camera inputs, CAN-FD, RS485 and 10GbE QSFP.
Those highlights are useful discovery fields, but the audited page does not attach them to a SOM part number, processor OPN, partner SKU, memory option, carrier revision or simultaneous-interface test. RCI therefore records them as family-level manufacturer claims.
Four headline metrics, three different evidence mechanisms
| Headline | Footnote evidence | What it is not |
|---|---|---|
| 234 concurrent agents | mimik modeled sweep of 455 feasible workflows across X100 and NVIDIA T5000 device classes | Observed Kria AI SOM throughput |
| 8,000 decisions/s | Bosch Rexroth controller result summarized as 125 μs on AMD X100 Series | Robot reasoning rate or identified Kria platform test |
| 3.4× real-time result | OpenNav benchmark on GMKtec EVO-X2 Ryzen AI Max+ 395 configured to reflect X199 versus Jetson AGX Thor | Kria AI SOM versus Thor measurement |
| 2.3× agents / 1.6× CPU | mimik model and OpenNav GMKtec proxy result respectively | One common physical-module benchmark |
Sponsorship or commissioning does not automatically invalidate a result. It does require the sponsor relationship, test article and modeled-versus-measured status to stay attached when the number is reused.
The developer platform adds a carrier and software stack
AMD describes a carrier card with an FPGA and multiple sensor and communication interfaces, supported by an AMD Robotics Software Suite built on ROCm and ROS 2. That is a platform architecture statement, not a frozen compatibility record.
The audited page does not provide an exact carrier-board revision, input-power range, cooling solution, supported ROS distribution, immutable software image, interface concurrency condition or public result bundle. RCI therefore does not place the platform into the exact-model comparison table.
Five missing objects block an exact-model record
- Orderable identity: no confirmed SOM part number, processor OPN, carrier SKU or partner configuration.
- Mechanical and electrical envelope: no fixed dimensions, mass, input-power range, cooling or derating record.
- Software bill: no immutable image, compatibility matrix or supported ROS/ROCm version set.
- Matched benchmark: no disclosed run of the four headline metrics on the named Kria AI SOM.
- Commercial state: no public list price, inventory state or shipment lead time on the audited page.
Twelve disclosure checks
| Field | Status | Evidence | Boundary |
|---|---|---|---|
| exact som part number | not-disclosed | The audited page uses the Kria AI SOM family name. | No orderable SOM identity or processor OPN is fixed. |
| exact carrier identity | not-disclosed | A carrier card with FPGA and interfaces is described. | No carrier SKU, schematic, connector map or revision is attached. |
| power and thermal | not-disclosed | The launch page describes performance and integration. | No exact input power, module power, cooling solution, derating or thermal test condition is fixed. |
| dimensions and mass | not-disclosed | COM-HPC is named. | No exact module or complete developer-platform dimensions and mass are published on the audited page. |
| price and availability | incomplete | Partner and contact routes are provided. | No public list price, exact shipping SKU, inventory state or lead time is established. |
| benchmark hardware match | not-matched | The OpenNav footnotes identify a GMKtec proxy system configured to reflect X199 specifications. | The compared system is not identified as the named Kria AI SOM or developer platform. |
| modeled vs measured agents | modeled | The mimik footnote describes a modeled sweep of feasible workflows. | Modeled concurrency is not observed production throughput or reliability. |
| controller result scope | incomplete | The 8,000 decisions/s footnote names a Bosch Rexroth controller on X100 Series. | Exact controller, X100 SKU, workload, software, repetitions and raw results are not fixed on the AMD page. |
| software release identity | not-disclosed | ROCm, ROS 2 and an AMD Robotics Software Suite are named. | No immutable software bill, supported-version matrix or result bundle is linked from the audited page. |
| raw results | not-on-audited-page | Headline values and footnote destinations are published. | RCI did not find raw metric files on the named product page. |
| independent replication | not-established | Two cited studies were commissioned or sponsored by AMD and one controller result is summarized by AMD. | Sponsorship does not invalidate a result, but it must be disclosed and does not prove independent replication. |
| rci validation | not-performed | RCI inspected public launch, product and footnote relationships. | Zero module, carrier, controller, software or robot tests were run by RCI. |
Method, work level and rights
RCI read the current AMD Kria AI product page, official newsroom route and X100 product surface, traced each prominent metric to the source named in its footnote, and classified the relationship between the named product and the cited evidence. RCI did not copy figures or tables, purchase hardware, execute software or reproduce any benchmark.
Highest completed work level: EV1 source verification. There is no EV3 recomputation, EV4 RCI bench test, EV5 external replication or EV6 accredited result.
- The audited web pages are mutable launch surfaces rather than immutable product datasheets.
- RCI did not obtain an exact partner SOM or carrier-board engineering package.
- The four headline metrics remain third-party or manufacturer-reported and were not recomputed by RCI.
- Absence from the audited page does not prove that private partner documentation or later orderable products do not exist.
- A proxy system configured to reflect X199 specifications is not a Kria AI SOM measurement.
Primary surfaces: AMD Kria AI product page, AMD newsroom announcement, OpenNav benchmark page and mimik benchmark page. Linked works retain their own rights.
Download the provenance map
Download the immutable JSON release and record-level CSV. Stable aliases are current JSON and current CSV.
Suggested citation: Robot Component Index. “AMD Kria AI Claims Audit: Four Benchmark Footnotes, Zero RCI Hardware Runs.” RCI 044, version 0.1.0, 2026-08-11. https://robotcomponentindex.com/research/amd-kria-ai-claims-audit/
For version-aware BibTeX and machine citation records, use Cite RCI.