Skip to content
AevornixAEVORNIX
RISC-VIn Development

Build for RISC-V before the hardware wave arrives.

RVStack gives developers the software tools to test applications, package workloads, run AI models, build images, certify compatibility and publish RISC-V-ready software.

Explore RVStack View the RISC-V roadmap
Join Developer Preview RISC-V in the Store

What RVStack is

The software layer above the instruction set.

RVStack is Aevornix's software-first RISC-V platform. It helps developers build, test, optimise, certify and publish software for RISC-V environments before mass-market hardware is ready.

Aevornix does not design processors. The instruction set is open and already exists; what is thin is everything a developer needs on top of it.

RVStack pipeline
RVStack pipeline, 9 stages first to last: 01 Developer input, 02 Build system, 03 Emulation, 04 Compatibility scanner, 05 Security scanner, 06 AI runtime, 07 Certification, 08 Store publishing, 09 Deployment.

  1. Developer input

    A repository, a package or a model, plus the profile it is meant to run on.

  2. Build system

    Cross-compilation and linking for the selected 64-bit RISC-V target.

  3. Emulation

    Execution inside an emulated RISC-V machine matching the profile.

  4. Compatibility scanner

    Native libraries, architecture-specific binaries and missing system services.

  5. Security scanner

    Supply chain, signing state and a software bill of materials.

  6. AI runtime

    Format, operator coverage, precision and memory for any model in the package.

  7. Certification

    One report naming the profile, the date and exactly what was checked.

  8. Store publishing

    A listing carrying the architecture, licence, badges and tested date.

  9. Deployment

    Delivery to an emulated profile, a Linux RISC-V machine or a managed fleet.

Why RISC-V needs software

RISC-V gives the industry an open processor architecture. Developers still need operating systems, build tools, app stores, AI runtimes, testing, certification and deployment systems. RVStack focuses on those missing software layers.

Software first. Hardware later.

Aevornix is not waiting for consumer RISC-V devices to mature. RVStack begins with emulation, cloud builds, app scanning, AI model checks and software distribution. This creates value before hardware scale arrives.

The stack

Eight capability areas.

Each one is a distinct piece of software with its own stage. Where a card links, that page covers it in full.

Developer cloud

Build and test for RISC-V without owning the hardware.

In Development

App compatibility

Find what blocks a package before the port begins.

In Development

AI runtime

Check, size and package models for RISC-V environments.

Research

Mobile platform

A RISC-V-first mobile software platform on an open foundation.

Research

Store distribution

Publish with architecture, licence and scan results attached.

Planned

Certification

A checkable statement of what a build was tested against.

Planned

Security

Supply-chain scanning, signing and bills of materials.

Research

Fleet deployment

Managed delivery of certified builds to many devices.

Planned

Research status

Six lanes, at two different depths.

Four lanes are still answering questions. Two have moved past that into something that runs.

Read the research map

Building on an answer

Still open questions

  • RISC-V AI runtime

    Research

    Which models are practical on RISC-V systems, and at what size and precision?

  • RISC-V mobile software

    Research

    What does a mobile software platform need once vendor-specific services are not available?

  • RISC-V app store

    Research

    What does a buyer need to know before installing software built for an architecture they may not have?

  • RISC-V security

    Research

    What has to be true about a package before a platform is willing to sign and distribute it?

Prototype status

What is being proved, and how far it has got.

Seven targets, each at its own stage.

  • RISC-V app scanner

    Take a package, report what prevents it running on a RISC-V profile.

    In Development

  • RISC-V AI model scanner

    Take a model, report unsupported operators, precision and estimated memory.

    Research

  • RISC-V emulator runner

    Run a build against an emulated profile and capture its output.

    Prototype

  • RISC-V store category

    A category in the Aevornix Store carrying architecture and target metadata.

    Planned

  • RISC-V compatibility badge

    A published, checkable statement of what a package was tested against.

    Planned

  • Aevornix Mobile shell

    An emulated mobile system shell with Aevornix services in place of vendor ones.

    Research

  • RVStack CLI

    One command line across build, emulate, scan, certify and publish.

    Planned

Programme indicators

Emulation workflowPrototype
App scannerIn Development
AI model scannerResearch
Linux image builderPlanned
Store categoryPlanned
Certification badgesPlanned

Development roadmap

Research, prototype, development, platform.

Four stages. Two are under way at once, because the research lanes have not all closed.

View the RISC-V roadmap

  1. Stage 01: Research

    Under way

    Define the software problem.

  2. Stage 02: Prototype

    Under way

    Build working proof.

  3. Stage 03: Development

    Next

    Turn prototypes into usable products.

  4. Stage 04: Platform

    Later

    Create a commercial ecosystem.

Product family

Where the RISC-V work sits.

RISC-V is not a separate company inside Aevornix. It is a target that seven existing product lines are being extended to reach.

RVStack
The RISC-V software platform: build, scan, certify, publish.
Aevornix Mobile
A RISC-V-first mobile software platform derived from open foundations.
Aevornix AI
Model checking, optimisation and packaging for RISC-V environments.
Aevornix Cloud
Hosted build, emulation and test capacity for developers without target hardware.
Aevornix Runtime
The portable execution layer compiled software runs on.
Aevornix Store
Distribution, licensing and trust signals for RISC-V software.
Aevornix Developer Platform
Accounts, preview access, documentation and publishing.

Certification model

Trust is the last layer, not the first.

A build becomes publishable when there is a published, checkable statement of what it was tested against: the profile, the date and the findings.

RISC-V in the Store The compatibility scanner

RISC-V category in the Aevornix Store

Planned

The Aevornix Store is live and carries a real catalogue today, but it has no RISC-V category. The listing schema, the badge set and what each badge would have to be earned by are described in full on the Store page.

Developer preview

Join the RVStack developer preview to test software portability, scan packages, prepare AI models and publish RISC-V-ready products through the Aevornix ecosystem.

Join Developer Preview

Build for RISC-V.

Join Developer Preview Read the research map RISC-V in the Store