Skip to content
AevornixAEVORNIX
RoadmapIn Development

Research to platform, in four stages.

Each stage has a purpose and a set of deliverables, and each deliverable states where it actually is. Two stages are running at once, because the research questions have not all been answered.

Stages

What each stage is for.

A stage marked as under way does not mean every deliverable inside it is. Each carries its own status.

  1. Stage 01: Research

    Under way

    Define the software problem.

    • RISC-V ecosystem mapIn Development
    • Use-case modelIn Development
    • Compatibility criteriaIn Development
    • Licensing rulesResearch
    • Open mobile foundation policyResearch
    • AI runtime assessmentResearch
    • Store taxonomyResearch
  2. Stage 02: Prototype

    Under way

    Build working proof.

    • Emulator test flowPrototype
    • 64-bit RISC-V build runnerPrototype
    • Linux application scannerIn Development
    • Mobile package scannerResearch
    • AI model readiness reportResearch
    • RISC-V store categoryPlanned
    • Developer preview applicationsAvailable
  3. Stage 03: Development

    Next

    Turn prototypes into usable products.

    • RVStack Developer CloudIn Development
    • RVStack SDKIn Development
    • RVStack CLIPlanned
    • RVStack CertifyPlanned
    • Aevornix Mobile shellResearch
    • AI runtime packagingPlanned
    • Store publishing workflowPlanned
  4. Stage 04: Platform

    Later

    Create a commercial ecosystem.

    • Paid certificationPlanned
    • Developer accountsAvailable
    • Build minutesPlanned
    • Store revenue sharePlanned
    • Enterprise fleet deploymentPlanned
    • AI model marketplacePlanned
    • Mobile system previewPlanned
    • Partner programmePlanned

Current work

The RISC-V items on the company roadmap.

The same items, grouped by what is happening to each one, with their dependencies and current objective.

View development roadmap

Active(2)

  • Compiler toolchain

    In Development

    Compile and link Aevornix projects for 64-bit RISC-V targets.

    Depends on
    Device profile definitions
  • Execute builds against a defined device profile so target behaviour is observable before hardware exists.

    Depends on
    Device profile definitions

Next(7)

  • RISC-V SDK

    In Development

    Provide the headers, libraries and build integration developers target open architectures through.

    Depends on
    Compiler toolchain
  • App scanner

    In Development

    Report exactly which profile requirements a build meets, category by category.

    Depends on
    Device emulator · Device profile definitions
  • Developer Cloud

    In Development

    Host build and test environments so RISC-V development needs no local target hardware.

    Depends on
    Compiler toolchain · Device emulator
  • Assemble deployable Linux images for supported RISC-V targets.

    Depends on
    RISC-V SDK · Operating layer
  • Define the compatibility and security report that gates a store listing and a deployment.

    Depends on
    App scanner · Security report
  • Drive build, emulate, scan, certify and publish from a terminal or a continuous-integration pipeline.

    Depends on
    RISC-V SDK · Developer Cloud
  • Add a Store category that carries architecture support, operating-system target, scan results and the date a product was last tested.

    Depends on
    RVStack Certify · Aevornix Store

Research(2)

  • Deliver certified builds to emulator, cloud and physical targets.

    Depends on
    RVStack Certify · Image builder
  • Establish which model formats, operators and precisions are practical on RISC-V, and what a runtime would have to provide.

    Depends on
    Compiler toolchain · Device emulator