Berth is the VRAM leasing service for every GPU you run. Engines ask the berthd node for a lease on the card; the node queues the request, asks the current holder to drain, waits until the driver shows the memory free, and only then grants the berth. Nothing is ever granted on process exit alone, and nothing is claimed as reserved unless the driver measured it. Every stat on this page is collected by the node itself, from the driver, the host, and the engines' own endpoints.
- -A section rail under the header jumps to any panel on the tab and marks the one in view. Every panel folds from the chevron in its head and stays folded between visits. The card tab counts voyages and the engines tab counts engines, so the header says which tab wants attention. On a phone the nav sits along the bottom edge with the tab you are on marked, and the menu button opens the node's versions, the last successful read, the detail level, the retry and this list. Times read relative, with the exact clock in the title. When a read goes stale a retry appears on the conn pill that reads the node now instead of waiting out the poll.
-The log's filter box matches the kind word, the engine and the detail; the chips carry live counts and the count line names what is shown. LATEST jumps back to the newest row. The board's headers sort by vessel, hold, status and age, and the foot names the order. Alert cards dismiss until they clear or change level. The ticket copies its JSON or a deep link to this exact voyage.
- -berth. the VRAM leasing service for every GPU you run
+Engines ask the berthd node for a lease on a card. The node queues the request, asks the current holder to drain, waits until the driver shows the memory free, and only then grants the berth. Nothing is granted on a process exit alone, and nothing is called reserved unless the driver measured it. Every number on this page comes from the node: the driver, the host and the engines' own endpoints.
+Every state shows as a shape and its word together, the same on every panel: a dot is working now, a ring is waiting or passive, a half-filled circle is in transition, a triangle needs attention, a square is not running or not live. A magenta CONTESTED flag on a docked row means the driver saw other VRAM holders on the card at grant time, so the measured hold and the free space disagree. A green WARM flag marks a parked engine, and its hover text carries the estimated RAM it holds and how long it has been parked; a boarding row carries a Q flag with its place in the queue, and the node's completion estimate when it sent one. The row title, the berth panel and the ticket stamp carry how much each holds, and the ticket names the tier the weights live in, HOT on the card or WARM in RAM, beside the exact terminal order for it as a copy button. CARD RANKING on the engines tab shows how the node orders engines when two at one priority ask for the card inside the juggle window: the config order, or card hours over the last seven days.
- -Every count is an event the node actually saw. Berth never estimates what might have happened.
- -Context residency draws the engine's own per-request token figures - cached, fresh prefill and generated - as columns against the model's context window, so a request that would not fit its window is visible at a glance; below the columns sit the engines' live KV sessions. The KV pool is each engine's live KV slots (the llama.cpp family's /slots): how many context tokens each session holds against its window, with 75 and 90 percent marks. Stored ranges show the per-minute peak slot fill the harbor folded from the node's samples; the live slots stay live, whatever the range says. An engine without these endpoints reports no window and no slots, and the panels say so rather than guess.
The scheduled card reports its power draw against its power limit, temperature, utilisation, and in advanced mode its SM and memory clocks, fan, and PCIe generation and width. A reading of n/a means the driver did not report it, not zero. The machine panel is the host itself: CPU, cores, used and total memory, swap, and the one, five and fifteen minute load averages. Its socket line counts event-stream write timeouts and dropped slow readers, so a stalled log on a live node starts there.
- -The library lists the model file roots this machine has, the same rows berth models prints: each model's shelf, quant, size, and its CACHED share with the tier it reads as, COOL at half the model's bytes in the kernel page cache or better, COLD below. The kernel takes those pages back whenever the machine needs the RAM, so the share says a reload may skip the disk; it is an estimate of reload speed, never a statement about RAM held. SERVED BY names each engine that reports the model resident now, and EST VRAM is that engine's learned footprint from its past runs, an estimate of what a run needs and never a reservation. Each row's copy buttons give the exact commands: berth prefetch NAME warms the files, berth models show NAME reads the full header.
A stowaway is any process holding VRAM without a lease. Berth reports it and never kills it. A "no ticket" run is an engine started while the node was down, so it holds the card outside any lease. Both show here read only.
- -The harbor shows the node. Ordering work is coming in later phases, and these rows are marked coming, not working:
-Until then, everything the page shows is also on the terminal:
-berth status +
One berthd governs every card in the machine. Each card it schedules has its own berth panel with only that card's leases and stowaways, and a card it only reads is marked INVENTORY ONLY. A board row, a stowaway and a lease line name their card (gpu1), and a lease on several cards lists them. The tide draws the memory of all scheduled cards together. A card passed to a VM is marked on its own panel, and the others keep serving.
+Each state shows as a shape and its word together on every panel. A dot is working, a ring is waiting, a half-filled circle is in transition, a triangle needs attention, and a square is stopped. A magenta CONTESTED flag on a docked row means the driver saw other VRAM holders at grant time. A green WARM flag marks a parked engine, and its title gives the RAM it holds and how long it has been parked. A boarding row carries a Q flag with its place in the queue and the node's estimate when it sent one. A ticket names the tier the weights live in, HOT or WARM, and gives the exact terminal command as a copy button. CARD RANKING on the engines tab shows how the node orders two engines at one priority inside the juggle window: the config order, or card hours over seven days.
+Every count is an event the node saw. Berth never estimates what might have happened.
+Context residency draws each request's cached, fresh and generated tokens against the model's context window, so a request that would not fit is plain to see. The KV pool shows each engine's live slots (the llama.cpp family's /slots) against their windows, with marks at 75% and 90%. Longer ranges show the per-minute peak fill; the live slots stay live. An engine without these endpoints reports no window and no slots, and the panels say so.
Each card reports power against its limit, temperature and utilisation, and in advanced mode its SM and memory clocks, fan and PCIe link. n/a means the driver did not report a value; it never means zero. The machine panel is the host: CPU, cores, memory, swap and load. Its socket line counts event-stream write timeouts and dropped slow readers, so a stalled log starts there.
+The library lists the model files on this machine, the same rows berth models prints: shelf, quant, size, and the CACHED share in the kernel page cache. COOL means half the file or more is cached, COLD less. The kernel takes those pages back when it needs the RAM, so CACHED predicts a faster reload and says nothing about RAM held. SERVED BY names the engine that has the model loaded, and EST VRAM is that engine's learned footprint, an estimate and never a reservation. The copy buttons give berth prefetch NAME and berth models show NAME.
A game that a hold claim matches holds the card under a claim:NAME lease, so engines drain and wait until it exits. berth hold does the same by hand. A stowaway is any process holding VRAM without a lease: Berth reports it and never stops it. A NO TICKET run is an engine started while the node was down, so it holds the card outside any lease.
The harbor reads the node and changes nothing. Switching and stopping engines from here will need a paired device (berth pair), and that is not built yet. The gateway has its own page at /gui/ on the gateway's port, where an engine with a start command can be launched. Everything this page shows is also on the terminal:
berth status berth events -f -berth run +berth claims +berth hold --reason game berth config check+
The roadmap says what comes next.
+