Skip to content
AevornixAEVORNIX
DevicesFuture Platform

One library. Multiple ways to play.

Aevornix is designing a connected gaming hardware platform built around a shared runtime, Store, account system and game library.

Explore the platform architecture Follow hardware development
SHARED PLATFORMHomeHandheldCloud
One libraryOne runtimeOne StoreOne account

Platform principle

Built as one system.

Four parts, designed together. A device profile is a set of capabilities within this system rather than a separate product with its own library and account.

The platform is one system with four parts: One library, One runtime, Multiple profiles, Connected services.

One library

Games and applications remain attached to one Aevornix account.

One runtime

Supported projects target shared execution and compatibility standards.

Multiple profiles

Developers build against defined home, portable and cloud profiles.

Connected services

Cloud saves, remote play, updates and account services move between supported devices.

One system · four parts · shared across every profile

Hardware profiles

Three profiles, one platform.

Each profile is being designed toward a set of principles. These are design directions rather than specifications. Nothing below is a committed capability.

Home platform

Research

High-performance gaming for the living room.

Read the profile research →
Design principles
  • Sustained performance rather than short bursts
  • Quiet thermal design
  • Fast local storage
  • Serviceable construction
  • Shared Aevornix runtime
  • Developer profile targeting

Handheld platform

Research

Portable access to the same account and compatible library.

Read the profile research →
Design principles
  • Efficiency-oriented, RISC-V-directed research
  • Portable power profile
  • Docked and handheld modes
  • Local and streamed play
  • Shared save data
  • Adaptive interface scaling

Cloud gaming

Future Platform

Remote execution for supported games and applications.

Read the profile research →
Design principles
  • Account-linked sessions
  • Regional game streaming
  • Controller handover
  • Save synchronisation
  • Device-independent access
  • Adaptive streaming

Platform architecture

The stack every profile shares.

Six layers. The top three run in production or developer preview today; the lower three are where the hardware work actually sits. Open a layer for its purpose, stage, product and what it means for a developer.

Shared software stack, 6 layers from top to bottom: 01 Games and applications, 02 Aevornix Store and library, 03 Aevornix account and identity, 04 Aevornix Runtime, 05 Operating and device services, 06 Home, handheld and cloud profiles.

  1. Games and applicationsWhat a player actually runs, authored against a declared capability profile.Developer PreviewOpen
    Purpose
    What a player actually runs, authored against a declared capability profile.
    Development stage
    Developer Preview
    Related product
    Aevornix Engine
    Developer relevance
    This is your project. The profile you target is a build setting, not a separate port.
  2. Aevornix Store and libraryDistribution, ownership and the library a player carries between devices.AvailableOpen
    Purpose
    Distribution, ownership and the library a player carries between devices.
    Development stage
    Available
    Related product
    Aevornix Store
    Developer relevance
    The distribution layer already runs in production, so it is the one part of this stack you can build against today.
  3. Aevornix account and identityOne identity across the Store, the site, the tools and every device profile.AvailableOpen
    Purpose
    One identity across the Store, the site, the tools and every device profile.
    Development stage
    Available
    Related product
    Your account
    Developer relevance
    Entitlement and save ownership hang off this, so a player’s library is not per-device.
  4. Aevornix RuntimePortable execution of compiled projects across supported targets.In DevelopmentOpen
    Purpose
    Portable execution of compiled projects across supported targets.
    Development stage
    In Development
    Related product
    Aevornix Runtime
    Developer relevance
    The compatibility contract. If your project runs on the runtime, moving between profiles is a capability question rather than a rewrite.
  5. Operating and device servicesSystem services, permissions, storage, networking and application lifecycle.ResearchOpen
    Purpose
    System services, permissions, storage, networking and application lifecycle.
    Development stage
    Research
    Related product
    Aevornix OS
    Developer relevance
    Determines what a project may ask of a device, and how it starts, suspends and resumes.
  6. Home, handheld and cloud profilesThe declared capability levels a build is certified against.Future PlatformOpen
    Purpose
    The declared capability levels a build is certified against.
    Development stage
    Future Platform
    Related product
    RVStack
    Developer relevance
    You target a profile, not a device. The profile is what the compatibility report is written against.

Continuity

Your session moves with you.

What the shared stack is for: a session that follows the account rather than restarting on each device.

  1. Start on the home system
    A session begins on the profile with the most headroom.
  2. Continue on the handheld
    The same title resumes on the portable profile.
  3. Resume through the cloud
    Where no local device is available, the session runs remotely.
  4. Synchronise saves
    Save state follows the account rather than the hardware.
  5. Retain account identity
    One identity across every profile.
  6. Retain library access
    The library is attached to the account, not the device it was bought on.

This flow describes a platform intention. No part of it is an operating service today.

Developer model

Build against profiles, not unknown hardware.

A profile can be built against before the machine exists. It states its capabilities; a build is checked against them and produces a report.

RVStack architecture →Aevornix Runtime →Developer documentation →Hardware roadmap →
Target profiles
Build against a named capability profile rather than a specific machine.
Defined capability levels
Each profile states what it provides: ISA baseline, memory, graphics, storage, input.
Performance budgets
Frame, load and throughput envelopes belong to the profile, so optimisation has a target.
Input profiles
Controller, touch and docked input declared per profile rather than detected at runtime.
Screen profiles
Resolution and scaling behaviour declared, so interface work is deliberate across form factors.
Certification checks
A build is checked against the profile before it is considered deployable.
Compatibility reports
The check produces a report naming exactly what is met and what is not.
Shared packaging
One packaging path across profiles rather than a separate pipeline per device.

Development

Where the hardware work stands.

Filtered to the hardware and gaming-platform items. Every entry is at research stage, with its objective and dependencies.

Research(6)

  • Shared device software stack

    Future Platform

    Define one stack (library, Store, account, runtime and device services) that every hardware profile shares.

    Depends on
    Portable runtime · Store account system

  • Hardware capability profiles

    Future Platform

    Define the home, handheld and cloud capability profiles developers build against instead of unknown hardware.

    Depends on
    Shared device software stack · Device profile definitions

  • Home platform research

    Future Platform

    Research a living-room system built for sustained performance, quiet operation and serviceability.

    Depends on
    Hardware capability profiles

  • Handheld platform research

    Future Platform

    Research a portable system sharing one account, library and save data with the home profile.

    Depends on
    Hardware capability profiles

  • Cloud gaming

    Future Platform

    Research remote execution and streaming for supported games, with account-linked sessions and save synchronisation.

    Depends on
    Shared device software stack · Cloud build and test

  • Input and controllers

    Future Platform

    Research input profiles and controller handover across the hardware family.

    Depends on
    Hardware capability profiles
Follow hardware development

Follow the Aevornix hardware platform.

Follow hardware development Explore Aevornix Runtime

Read the RVStack architecture →