Skip to content
AevornixAEVORNIX
CloudIn Development

Aevornix Cloud

Hosted build, test and distribution infrastructure.

View the architecture View the roadmap

Overview

What Aevornix Cloud is

Hosted build and test infrastructure for Aevornix projects: the layer that makes building for a target you do not own practical.

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 →

Planned scope

Cloud build
Hosted build pipelines for projects, applications and images.
Cloud testing
Test suites and device-matrix checks run as part of the pipeline.
Developer Cloud
Hosted workspaces so RISC-V development needs no local target hardware.

Portability commitment

Every Aevornix service is built so it can move between cloud providers and Aevornix-owned servers. The Store, its API and this site already run as containers on managed infrastructure for exactly this reason, nothing is architected in a way that makes leaving a provider impractical.

Development

Where the work stands.

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

Active(1)

  • Portable infrastructure

    In Development

    Keep every service movable between cloud providers and Aevornix-owned servers.

    Last update
    : Store, Store API and this site all run as containers on managed infrastructure

Next(1)

  • Cloud build and test

    In Development

    Run project builds and device-matrix test runs as hosted pipelines.

    Depends on
    Developer Cloud

Explore Aevornix Cloud.

View the architecture View the roadmap
Aevornix Cloud | Cloud | Aevornix