Compositions

A composition is a named group of instances launched together — for example a Redis and a Postgres VM for the same app, or an Open WebUI service wired to a local LLM. You manage the list under Compositions, and you build the graph on the Compose tab.

Compositions list

Open Compositions in the sidebar. Each row is a composition:

• Name on the left
• CPU / memory bars for the group
• Member instances (VMs, LLMs, services), with state
• Row actions: open related views, add members, monitor, delete

Use New composition (orange) to create an empty group, then switch to Compose to place nodes.

TIP

Deleted members still appear in the list until you clean the composition. That is normal after you tear down a stack — recreate or remove the stale rows when you are done.

Compose canvas

1. Open Compositions → Compose.
2. Pick or create the composition name in the header dropdown.
3. Drag items from the left palette (Services, VMs, or LLMs) onto the canvas.
4. Connect nodes: click an output pin, then an input — or drag between pins.
5. Pan by dragging empty space; scroll to zoom. Use the + / - / fit controls at the bottom-left of the canvas.
6. Select a node to edit it in the right property panel.
7. Save, then Deploy composition when you are ready to provision.

The palette is the inventory of droppable services (and VMs / LLMs on the other tabs). Search by scrolling; names match the Service catalogue.

Watch the CPU / memory bars in the header while you add nodes. Deploy composition is the commit step — it launches the graph on this host.

When to use a composition

Situation	Prefer
One throwaway VM	Images → Launch (no composition needed)
App stack (DB + UI + model)	Composition + Deploy composition
Same members relaunched often	Save the composition and redeploy

Next

• Compute — launch a single VM outside a composition
• Services — what each catalogue pack installs