Firefly AIBOX-K3 - An Edge AI mini PC powered by SpacemiT K3 RISC-V SoC
Back in July last year, SpacemiT unveiled the SpacemiT K3 SoC. After that, we saw some system information and early benchmarks come out around January
Condensed by AI-Portable from CNX Software — Edge AI.
Back in July last year, SpacemiT unveiled the SpacemiT K3 SoC . After that, we saw some system information and early benchmarks come out around January this year. The company has just officially launched the K3 Pico-ITX SBC , which is now available through various distributors. Firefly has launched its own K3 hardware with the AIBOX-K3, a complete industrial-grade RISC-V edge computing box.
The AIBOX-K3 Edge AI mini PC is built around the SpacemIT Key Stone K3 octa-core processor and features an integrated AI engine that delivers up to 60 TOPS of compute performance, making it suitable for local LLM inference and edge AI applications.
SoC – SpacemiT K3 CPU 8x 64-bit RISC-V X100 “big” cores clocked up to 2.4 GHz, RVA23 compliance; 130 KDMIPS performance ( similar to RK3588 ) 8x RISC-V A100 AI Cores with support for up to 1024-bit RVV1.0 parallel computing, optimized for matrix operations. GPU – Imagination Technologies BXM4-64-MC1 GPU with Vulkan 1.3, OpenCL 3.0, and OpenGL ES 1.1/2.0/3.2 support VPU Video decoder – H.265, H.264, VP9 up to 4K @ 120 FPS Video encoder – H.265, H.264 up to 4K @ 60 FPS AI – Up to 60 TOPS (INT4) of AI performance using dedicated TCM and DMA acceleration channels
CPU 8x 64-bit RISC-V X100 “big” cores clocked up to 2.4 GHz, RVA23 compliance; 130 KDMIPS performance ( similar to RK3588 ) 8x RISC-V A100 AI Cores with support for up to 1024-bit RVV1.0 parallel computing, optimized for matrix operations.
8x 64-bit RISC-V X100 “big” cores clocked up to 2.4 GHz, RVA23 compliance; 130 KDMIPS performance ( similar to RK3588 )
The portable AI angle here is not just that CNX Software — Edge AI published a new item. It is that this material changes how readers should think about edge ai boxes systems in practical terms: what shifts on-device, what still depends on platform or cloud layers, and what kind of user workflow becomes more or less realistic as a result.
From an editorial standpoint, the most useful question is whether this technical_signal produces a real behavioral or product constraint change. If the answer is yes, it belongs in AI-Portable because it tells us something about interface friction, local capability, deployment readiness, or the specific work conditions where portable AI may actually land first.
This matters because it touches edge ai boxes through a technical_signal signal, which affects real device-side constraints, deployment timing, or product readiness.
Even when the source is directionally useful, the editorial job is to separate confirmed facts from launch framing. Availability, sustained usage evidence, implementation complexity, privacy implications, and integration cost often determine whether a portable AI signal is operationally meaningful or just momentarily interesting.