Groups and names

With 3 machines any naming works. With 30 the fleet list is the screen you live in, and names are what make it readable.

Names

A machine’s name is yours to set and can be changed at any time — it is a label, not an identifier. Nothing breaks when you rename: rentals, earnings and history follow the machine, not the name.

What tends to work, in order of how often you need it:

• Where it is, if you have more than one location: warsaw-04.
• What is in it, because this is what you compare on price: 4090x8, a100-sxm.
• Which box, so you can walk up to it: a rack position or a case label.

What tends not to work: the hostname the machine came with, and anything that encodes a price or a marketplace — both change while the name stays.

Names are sorted as text

gpu-2 and gpu-10 sort next to each other only if you write gpu-02 and gpu-10. Worth deciding before the fleet grows.

Groups

A group is a label on a machine that the fleet list can filter by. Use it for the split you actually work along — usually a location, an owner, or a hardware class.

Groups matter in three places:

• The fleet list, where the group filter narrows a long list to the machines you are dealing with right now.
• Pricing, where a rule that applies to a class of card is easier to reason about when the fleet is grouped the same way.
• Reading earnings, where per-group totals answer questions like whether a location is paying for its electricity.

Bulk actions

Bulk maintenance across a group is not available yet — queue the command per machine for now. The panel tells you this rather than silently applying to one machine.