Skip to content
MeghaOS

Select language

MeghaOS speaks over 100 languages on your own machine. This site is available in full in every language listed here; our legal pages and blog posts stay in English.

FIG 6.0 · Architecture

Six layers,hardware tocomposed interface.

MeghaOS is a Wayland-native system built from the ground up around an agent that acts on your machine. The agent sits below the applications rather than above them, and that inversion is what the rest of this page follows from.

FIG 6.1 · The stack

Hardware at the bottom. Composed interface at the top.

The agent runs below the applications, not above them. That inversion is the whole architecture.

LAYER 00HardwareLAYER 01System imageLAYER 02Session & compositorLAYER 03Service separationLAYER 04Agent runtimeLAYER 05A2UI
FIG 6.2 · Layer by layer

What each layer actually does.

Read top to bottom or bottom to top; each layer only depends on the one beneath it.

LAYER 05

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.

  • 160+ widget types
  • Composed per intent
  • Wayland · labwc compositor
  • Tear-free, no X11 legacy
LAYER 04

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.

  • Local or hosted models
  • Parallel agents with budgets
  • Local vector memory
  • MCP connectors
LAYER 03

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.

  • Separate agent service
  • Local socket transport
  • Supervised and restartable
  • One agent per session
LAYER 02

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.

  • Wayland-native
  • wlroots compositor
  • Tear-free, no X11 legacy
  • Session-managed lifecycle
LAYER 01

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.

  • Image-based install
  • Versioned as a unit
  • No per-machine drift
  • Reproducible across a fleet
LAYER 00

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.

  • amd64 (x86_64)
  • UEFI or legacy BIOS
  • 8 GB RAM recommended
  • 25 GB disk
FIG 6.3 · The loop

Intent in, composed interface out.

Every request runs the same path. The agent works out what would help, describes an interface for it, and the shell draws that description, then discards it when you move on. No application is launched because none needs to be.

  • The agent reasons about intent, not about which app to open
  • It emits a description of an interface, not a screenshot of one
  • The shell draws it from its own widget set, 160+ types
  • The composition is thrown away, so nothing accumulates
One request
  1. 01
    Intent
    What you asked for, in your own words.
  2. 02
    Plan
    Which tools and which data the answer needs.
  3. 03
    Compose
    A description of the interface that would help.
  4. 04
    Render
    Drawn natively by the session, not screenshotted.
  5. ↺
    Discard
    Gone when you move on. Nothing to uninstall.
FIG 6.3b · The output

Step 04, running in this page.

The description the agent emits, handed to the shell's renderer: the same code, vendored into this site, drawing from the same widget set. If you want to know what layer five produces, this is it.

Where the money is

Read from the ledger export on this machine. Nothing left the device.

Runway
14.2months
↑ +1.4 vs last close
Q3 burn
412K
↑ 8.1% under forecast
Variance
36K under
↑ +2 months
Q3 budget consumed78%
Headcount plan filled61%
Monthly burn against forecast
USD thousands
AprMayJunJulAugSep
78of plan

Three months under. Compute is the only line above forecast, up 19% since the eval cluster came online.

Payroll lands where it was modelled, so the variance is real rather than timing.

FIG 6.4 · Storage

Mistakes are cheap

The coding workspace is checkpointed before the agent acts, and undo rewinds the files and the conversation together. Letting an agent try things is only reasonable when trying things is cheap to reverse. Elsewhere the guard is different: destructive commands are refused outright, and the risky middle tier stops to ask.

  • A checkpoint before every coding-agent turn, automatically
  • Undo restores files and conversation together
  • Kept separate from your own version control
  • Per-message, so you rewind exactly as far as you meant to
FIG 6.5 · Display

Pure Wayland, no X11 legacy

The display stack is pure Wayland on the lightweight labwc compositor, buttery smooth and tear-free. Dropping X11 is also a security decision: X11's input model lets any client watch every other client's keystrokes, which is untenable when agents are driving the screen.

  • labwc compositor, small, fast, well understood
  • Tear-free by construction, not by workaround
  • No global input snooping between clients
  • A2UI layouts are drawn by the shell, not fetched as a page
FIG 6.6 · Requirements

What it needs from your machine.

Deliberately modest. Lightweight and low-latency on modern multi-core systems, bare metal or virtualised.

Architecture
amd64 (x86_64)
Firmware
UEFI or legacy BIOS
Memory
8 GB recommended
Disk
25 GB

Verify it yourself.

The ISO is public and checksummed. Nothing on this page requires you to take our word for it.