Iris
A shorter path from image data to the screen.
Iris is built with raw Vulkan, DMA-BUF zero-copy pipelines, and direct GPU memory handling. It is for Linux users who care what the software is actually doing between decode and presentation.
iris render path
dma-buf zero-copy
preferred when the stack permits it
raw vulkan
direct ownership of presentation
extra copies
treated as waste, not normal overhead
01
gpu-owned presentation
02
lower transfer churn
03
linux-first rendering
Why this matters
Most viewers still inherit the wrong center of gravity.
They remain CPU-shaped, layered for convenience, and relaxed about transfers the user never asked for.
That choice leaks into latency, heat, and feel.
People who care about systems can usually detect it before they can describe it.
Iris is built to remove that drag, not disguise it.
The product stays narrow because the engineering opinion is specific.
Principles
Technical signal
renderer
Vulkan is the renderer. Not the branding layer.
pipeline
Zero-copy is pursued because extra movement through memory is visible work.
audience
Linux users who care about systems are the intended center of gravity.
Roadmap
A first release centered on renderer correctness and stable interaction under real image workloads.
Format support expanded only where the path remains technically honest.
A small early group made up of Linux users who notice architecture before feature count.
Waitlist
Join before the first release opens up.
Leave an address if you want in early. The first group should be small, opinionated, and paying attention.
Private Waitlist
Join before public access.