Greg’s PlaceProjects / Project Lattice

Project Lattice

A homelab looks different depending on which console is open. Lattice puts the relationships in one place: a graph you can stand inside on Vision Pro.

Physical host

The Proxmox machine supplies CPU, memory and storage to its guests.

Virtual machine

A guest runs its own operating system. Its link identifies the host that provides the resources.

Linux container

A lighter guest shares the host kernel. Its activity belongs to this host too.

Example topology · expand a node to inspect it

Start with the host

In a flat list, a virtual machine and its host can look like peers. In Lattice the connection between them is part of the picture. A pinch on a node brings its contents closer. Activity changes which nodes draw your eye.

Behind the view

A Go service polls infrastructure APIs and translates their different inventories into nodes and edges. The headset consumes that graph. A new integration can describe the equipment it knows about without teaching the renderer another vendor’s API.

How a change reaches the headset

A Proxmox poller reads hosts and guests. The backend updates the graph and streams changes over a WebSocket. Swift and RealityKit turn those changes into objects in the room.

Lattice development overview · See the homelab architecture