Documentation menu

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

Hera KitViews · state · layout
React NativeHermes · Fabric · Yoga

↓ Versioned protocol and Unix IPC ↓

Hera server
  1. ServerConnections, input delivery, frame driver
  2. ComposerRetained state, animation, composition policy
  3. RendererScene planning, Vulkan, DRM/KMS

↓ Confirmed presentation ↓

Clients describe UI state. The server owns the composed display image and the presentation lifecycle.

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

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.rs
  • crates/composer/src/lib.rs
  • crates/renderer/src/lib.rs
  • crates/protocol/src/lib.rs