Skip to content
AevornixAEVORNIX
ComputeIn Development

Aevornix Runtime

Run Aevornix projects across targets.

Overview

What Aevornix Runtime is

The Runtime is the portable execution layer: the contract that lets a compiled project run consistently across desktop, web and future device profiles. It is the layer the whole device platform depends on, which is why it sits in development rather than research.

Architecture position

Where this sits in the stack.

Portable and vendor-independent by construction: standard interfaces and open targets, so software moves across the ecosystem rather than binding to one platform.

RVStack architecture

RVStack architecture, 7 layers from top to bottom: 01 Application, 02 Development toolchain, 03 Portable runtime, 04 Operating layer, 05 RISC-V architecture, 06 Device profile, 07 Deployment target.

  1. Application
    Games, tools and software targeting the Aevornix platform.
    .aev project format
  2. Development toolchain
    Compiler, linker, debugger, SDK and build systems.
    ELFDWARF
  3. Portable runtime
    Execution services shared across supported RISC-V targets.
  4. Operating layer
    System services, permissions, storage, networking and application lifecycle.
    POSIX-style system interfaces
  5. RISC-V architecturefoundation
    The open instruction-set foundation beneath the software stack.
    RV64GCRVA23
  6. Device profile
    Defined hardware capabilities used for emulation and compatibility testing.
  7. Deployment target
    Physical devices, virtual environments, cloud targets and certified platforms.
    linux-riscv64

Open the full architecture →

The problem it solves

Without a portable runtime, every target is a port. With one, a target is a capability question: the profile states what it provides, the runtime provides consistent execution semantics on top, and the difference between targets becomes something a compatibility report can describe.

Where it sits

Above
Games and applications, and the project format they are authored in.
Below
The operating layer and, beneath that, the instruction set.
Across
Desktop, web, and the home, handheld and cloud device profiles.

Development

Where the work stands.

Objectives and dependencies. Dates appear only where a specific verifiable event backs them.

Active(1)

  • Portable runtime

    In Development

    Execute compiled Aevornix projects consistently across desktop, web and future device profiles.

    Depends on
    Export targets
Aevornix Runtime | Compute | Aevornix