Base
Immutable trusted core
The system image is read-only by default, reducing drift and preserving integrity.
Warning: Avyos is experimental alpha software and is not ready for production use. Use only in testing or non-critical environments.
A modern OS foundation for secure, predictable computing.
Avyos is built in Go on top of Linux primitives. It rethinks the system layer for clarity, stronger isolation, and long-term maintainability without carrying legacy Unix assumptions forward.
Immutable core
Capability identity
Isolated compatibility
Built for teams that value clarity, reliability, and operational confidence.
Desktop Preview
How It Looks
Early Avyos desktop preview.
Designed from first principles.
Avyos starts with a clean model where trust, identity, and lifecycle behavior are intentional from day one.
Where traditional systems struggle
- Critical platform logic and day-to-day change often blur into one surface.
- Coarse identity models make least-privilege access difficult to maintain.
- Incremental layering creates drift and reduces long-term operational clarity.
How Avyos approaches it
- An immutable foundation keeps system behavior stable and easier to audit.
- Runtime change is controlled rather than implicit and ad hoc.
- Capability-first identity supports practical least-privilege boundaries across services and apps.
Predictability is the baseline. If behavior is unclear, redesign it.
Features
A clear system model focused on reliability, security, and maintainability.
Layout
Clear system model
The platform separates foundational system behavior from operational change.
Identity
Capability-first identity
Authorization is explicit, composable, and designed around least privilege.
Updates
Transactional upgrades
Apply updates atomically and roll back quickly when verification fails.
Privacy
Privacy-first defaults
Telemetry is disabled by default, and diagnostics remain transparent and opt-in.
Surface
Smaller trusted surface
Fewer base services improve auditability and reduce operational surprises.
Compatibility
Linux compatibility mode
Run existing Linux applications in isolated environments while keeping the core platform independent.
"Security and reliability should emerge from design, not from patchwork."
Architecture principleSecurity as a built-in property
Security is designed in from day one, not added later.
Stable trusted foundation
Core system components stay read-only, and changes remain intentional and reversible.
Capability-native identity
Capabilities define what software can do, replacing broad roles with focused permissions.
Boundary-first execution
Service and app boundaries are explicit, keeping behavior understandable and enforceable.
Design guarantees
- Immutable system foundation separated from runtime change
- Capability-driven least-privilege access model
- Isolated execution boundaries for services and applications
- Transactional upgrades with rollback support
- Minimal default services in the trusted base
FAQ
Clear answers to common questions.
Avyos runs on the Linux kernel but redesigns the operating system layer: layout, identity boundaries,
state routing, and trust assumptions.
Avyos replaces legacy OS assumptions with a modern model: immutable foundation, capability-first identity,
and clear boundaries between trusted platform behavior and runtime change.
Yes. Linux applications run in isolated compatibility environments so existing software can work without
redefining the core platform architecture.
Not by default. Any diagnostics are opt-in, transparent, and governed by explicit policy.
v0, code-named "Virtual Monster" (Alpha), focuses on the core lifecycle, trusted base, and practical
developer workflows.
Architecture overview
Avyos is built in Go above Linux primitives with modern identity, predictable lifecycle behavior, and clear compatibility boundaries.
Implementation policy:
Keep the full system in pure Go with CGO_ENABLED=0. Prioritize a design that is simple to
develop, maintain, and use. Compatibility-layer distro resources are allowed, but must stay optional and
never become a hard dependency for core platform behavior.
Reference architecture
Layered system model
Trusted boundaries and runtime contracts from kernel to user-facing workloads.
Compatibility layer
Distro compatibility runtime in strict isolation, with no access to the outside host environment. Privilege: Isolated
Application layer
User-facing apps and sessions with constrained access to platform services. Privilege: User
Runtime layer
Shared runtime services for graphics, display, and session orchestration. Privilege: Service
Core layer
Platform control services for boot, policy, identity, and lifecycle management. Privilege: Platform
Kernel base
Kernel primitives and hardware control for process, memory, and network boundaries. Privilege: Kernel
Compatibility: Wayland bridge and distro layer with outside-environment access blocked by default
Target hosts: QEMU arm64 and amd64, hardware enablement in progress
Project status
v0 release scope
Execution snapshot for Alpha
Build the redesigned OS with us.
Start with docs, review the architecture, or contribute implementation work.
Try Avyos
Spin up the latest Avyos image locally in minutes.
Notice: Below command take around 200 MB bandwidth and has been tested on macOS and Linux host machines.
