Architecture
Follow the ownership boundaries that turn application descriptions into a composed display image.
Hera places rendering and presentation under server control so that every application participates in one composition. Clients contribute descriptions of UI state, and the server retains those descriptions until they change. This ownership model lets the server coordinate application surfaces, animation, input, and display timing without handing the scanout loop to individual clients.
System Overview
↓ Versioned protocol and Unix IPC ↓
- ServerConnections, input delivery, frame driver
- ComposerRetained state, animation, composition policy
- RendererScene planning, Vulkan, DRM/KMS
↓ Confirmed presentation ↓
The diagram follows a UI description from its application toolkit across IPC and into the server. Within the server, service orchestration, composition policy, and device execution have separate owners. This allows asynchronous client work and the dedicated render worker to progress independently while keeping device resources under explicit ownership.
Architecture Guides
- Server and lifecycle explains service orchestration, connection ownership, and shutdown.
- Scene graph and surfaces explains retained state and cross-surface composition.
- Composer explains commit admission, animation sampling, and prepared frames.
- Renderer explains how scene descriptions become GPU work.
- Building a frame walks through a complete frame from commit to display activation.
- Presentation and synchronization explains why GPU completion and display activation are separate events.
- Input and focus connects hit testing to confirmed scene history.
Crate Responsibilities
The server-side crates divide responsibility according to that flow. hera-server manages service policy and delivery, then asks hera-composer to prepare retained composition state for a frame. hera-renderer consumes the prepared scene and owns the GPU and display resources needed to present it. The herad executable constructs these services from deployment configuration and supplies their shutdown signal.
The client boundary has a similar separation. hera-protocol defines the wire types, codec settings, and pure validation that both sides must understand, while hera-ipc carries those values through Unix framing and descriptor passing. Keeping filesystem and runtime operations in the transport layer allows the contract to be tested and reused independently.
Within an application, Hera Kit maintains its own tree for state, layout, and callbacks. That tree is evaluated into scene diffs; it is not the server's retained scene graph. The Internals guides explain how the toolkit moves from this local representation to an accepted server update.
Source Reference
The following files in the Hera checkout define the behavior described on this page.
crates/server/src/lib.rscrates/composer/src/lib.rscrates/renderer/src/lib.rscrates/protocol/src/lib.rs