The whole system,not just the agent.
A Wayland-native system designed from the ground up around an agent that can act on your machine. The other two editions borrow their foundations from an OS someone else maintains. This one is the foundation.
v0.1.10 · 3.0 GB · amd64 · UEFI and legacy BIOS
Six layers, and the agent sits on top of all of them.
Each layer only depends on the one beneath it. That ordering is what lets the agent sit below the applications it drives rather than above them.
Hardware
Commodity amd64 machines. No special silicon, no security co-processor requirement, no vendor lock. If it boots Linux and drives Wayland, it runs MeghaOS.
System image
The system is installed and updated as a whole image rather than assembled package by package. Every machine on a given version is running the same system, so "which version are you on" has an exact answer.
Session & compositor
A Wayland session built for this workspace rather than a general-purpose desktop with our software bolted on. The compositor, the lock screen and the greeter are all part of the same session.
Service separation
The agent runs as its own supervised service, separate from the interface that talks to it. They communicate over a local socket, so the workspace can restart without losing the agent and the agent can be stopped without taking the session down.
Agent runtime
The language model, the agent scheduler, the local vector store, and the MCP connector layer. Choose a local model and the whole loop (reasoning, memory and composition) completes without leaving the machine.
A2UI
The generative interface layer. Composes a workspace from 160+ widget types per request and renders it through a Wayland-native compositor. No application is launched.
The architecture page takes the same six layers apart in three dimensions.
What the foundation actually does for you.
The whole desktop, not an app on someone else’s.
The compositor, the greeter, the lock screen and the agent are one system designed together. Nothing here is our software bolted onto a desktop environment that was built for a different purpose.
- Compositor, greeter and lock screen all part of the session
- The agent starts and stops with the session that owns it
- No second desktop environment underneath fighting for control
- Consistent behaviour, because there is one path through it
- Compositor, greeter and lock screen all part of the session
- The agent starts and stops with the session that owns it
- No second desktop environment underneath fighting for control
- Consistent behaviour, because there is one path through it
A system that is versioned, not accumulated.
The installer writes a complete system image rather than assembling the machine package by package. Every install of a given version is the same install, which is what makes a problem reproducible and a fleet predictable.
- The image is the system, written whole
- Every machine on a version is identical
- No drift from years of incremental changes
- “Which version are you on” has an exact answer
- The image is the system, written whole
- Every machine on a version is identical
- No drift from years of incremental changes
- “Which version are you on” has an exact answer
A modern display stack, with no legacy tax.
The session is Wayland end to end. There is no X11 compatibility layer to work around, which is what lets the interface be composed and recomposed continuously without tearing or stale frames.
- Pure Wayland, wlroots-based compositor
- Tear-free by construction
- No X11 compatibility path to maintain
- Composition can change shape without a redraw penalty
- Pure Wayland, wlroots-based compositor
- Tear-free by construction
- No X11 compatibility path to maintain
- Composition can change shape without a redraw penalty
Supervised, restartable, and separate.
The agent runs as its own managed service rather than inside the window you are looking at. The interface can restart without losing the agent, and the agent can be restarted without taking your session down with it.
- One agent per session, supervised and restarted on failure
- Interface and agent talk over a local socket
- Model runtimes are their own services too
- Nothing is lost when a window goes away
- One agent per session, supervised and restarted on failure
- Interface and agent talk over a local socket
- Model runtimes are their own services too
- Nothing is lost when a window goes away
A model runtime that is already there.
The inference runtime and a compact model ship with the system, so the machine can reason offline from first boot. Point it at a larger model when the hardware allows, or at a hosted provider when a task earns it.
- Inference runtime installed and managed as a service
- A compact model bundled so first launch works offline
- Swap in Megha or any model you serve yourself
- Commodity amd64 hardware, no special silicon required
- Inference runtime installed and managed as a service
- A compact model bundled so first launch works offline
- Swap in Megha or any model you serve yourself
- Commodity amd64 hardware, no special silicon required
Build anything, on the machine you already trust.
Containers and virtualised development environments work the way they do on any Linux workstation, so a toolchain you need for one project does not have to become a permanent fixture of the system.
- Container tooling works as you would expect
- Toolchains stay inside their containers
- The agent can drive them like any other tool
- Your workspace is yours, not a managed appliance
- Container tooling works as you would expect
- Toolchains stay inside their containers
- The agent can drive them like any other tool
- Your workspace is yours, not a managed appliance
From download to desktop in three steps.
This one does replace your operating system. Back up anything you need first, and if you are not ready for that, the desktop environment gives you the same agent on the Linux you already have.
Verify and write
Check the image against its published SHA-256, then write it to a USB drive with whichever imaging tool you prefer.
Boot the installer
Start the machine from the drive. The installer walks through language, keyboard, timezone, disks and your user account.
Sign in
Reboot into MeghaOS. First launch sets up the workspace locally and asks which model you want it to use.
Before you install
1. Verify the downloaded image against its published SHA-256.
2. Write it to a USB drive with the imaging tool of your choice.
Double-check the target device before you confirm.
3. Boot from the drive and follow the installer.Verify the SHA-256 before you write it. The checksum is on the download page. We would rather you did not take our word for it.
Requirements
- amd64 (x86_64)
- UEFI or legacy BIOS
- 8 GB RAM recommended
- 25 GB disk space
- Wayland-capable GPU driver
- An 8 GB or larger USB stick
Every guarantee, end to end.
Air-gapped installation and fleet imaging are supported here. If you are deploying to a regulated environment, talk to us first.