RVA23 profile compliance was the OS portability gate for RISC-V application processors, and SpacemiT K3 is now on the right side of it. The K3 Pico-ITX SBC launched today with 8x X100 RISC-V cores at 2.4GHz plus 8x dedicated AI cores at 60 TOPS INT4, and Ubuntu 26.04 support that is mainline, not a board-vendor fork. Ubuntu mandated RVA23 for 25.10+; the distro simply does not port to boards that fail the profile.
Before RVA23, every RISC-V SBC ran a custom OS image maintained by the board vendor. Broken package repos, non-mainline kernels, toolchain assumptions that didn't hold outside the vendor's own build system. That forking tax was not a silicon problem; it was an ecosystem coordination failure that made RISC-V dev boards frustrating even when their raw compute was competitive. Ubuntu mandating RVA23 compliance starting with 25.10 set a hard line. K3 clears it, which means OpenHarmony, Fedora, Deepin, and Ubuntu 26.04 all run without modification. The development artifact you build on K3 is the same one you ship to production.
Vendors whose support contracts are priced around RISC-V ecosystem fragmentation have 18 to 24 months before that moat dries up. Teams building RISC-V AI inference pipelines or edge systems should budget a K3 evaluation now; the downside is a few weeks of porting work, the upside is escaping a vendor-lock stack on both the OS and the tools layer.