- Open foundations
- Prefer open standards and portable formats. RISC-V for the instruction set, open formats for projects and assets, so work is not trapped by the tool that made it.
- Connected products
- Products share identity, distribution, runtime and development systems. A capability built once is available across the platform rather than rebuilt per product.
- Portable infrastructure
- Services must be able to move between cloud providers and Aevornix-owned servers. Nothing is architected in a way that makes leaving a provider impractical.
- Truthful progress
- Product status reflects implemented work and verified development stage. A status label is a description of where something is, and it changes when the work does.