Servers

What is a server?

A server is a Linux machine you own, running Pierrr Agent, a small program that talks to your hub over HTTPS. Every enrolled server shows up as a card on the Servers page; it is the machine that runs the containers of the projects you deploy onto it.

A server of your own is in no way required: by default a project is deployed on Pierrr's own infrastructure. You only go through an agent if you want your containers to run on your own machine, which the project calls self-hosted mode.

Pierrr Agent licences

Each server consumes one Pierrr Agent licence seat, an add-on billed per server and independent of your main plan. A counter permanently shows how many seats are in use out of those you hold, and the page offers to subscribe one more unit when the quota is reached.

The "I have a code" button redeems a Pierrr Agent voucher handed out by the Pierrr team: it creates a server in the organization without consuming a seat.

Enrolling a new server

Connect a server mints a single-use enrollment token and the install command to paste on the target machine. You can name the server on the way; its real hostname is picked up on the agent's first connection. The token is shown only once: if it is lost, revoke the entry and mint another. The install detail lives on the Install Pierrr Agent page; the machine appears in the list around thirty seconds after a successful install.

The server list

The Servers page shows each agent as a card: name, hostname, agent version, enrollment date and last seen. A coloured dot marks its state. Tabs filter the list: all, online, offline, revoked and deleted.

Server states

An agent's status reflects its connectivity to the hub:

• Pending, the agent was created but has not registered yet: the enrollment token has not been used.
• Online, the agent is sending its presence signals; it can receive deployments.
• Offline, no recent signal (network down, machine off, agent stopped). Surfaced as a point of attention on the dashboard.
• Revoked, the agent's access has been cut; it can no longer connect and no longer sends metrics.
• Deleted, the entry has been removed from the active list; the agent is disconnected and can never reconnect.

Server detail

Open a server to reach four tabs:

• Machine, the agent's identity (name, hostname, version, system, enrollment date, last contact), the list of projects deployed on it with their container and deployment counts, and the agent update block.
• Health, the latest snapshot sent by the agent: processor, memory, disk, and the list of containers with the count of healthy and failing ones. A button requests an immediate snapshot, a switch turns on live streaming.
• Metrics, processor and memory usage container by container: the trend over the last ten samples and the current split.
• Settings, the server's display name. Renaming it leaves the machine's real hostname untouched.

When the agent has not been seen recently, live metrics pause and say so: they resume on the next presence signal.

Updating the agent

The agent never updates itself. The Machine tab says whether a newer version exists, with a button to check on demand and another to trigger the update. The agent has to be online to accept it.

A progress bar follows the four stages: download, verification, install and restart. The binary is verified before being installed, and the previous one is kept so a failed start can be rolled back.

Revoking or deleting a server

The server's danger zone offers two actions, both confirmed by typing the hostname:

• Revoke immediately cuts the agent's credentials and closes its session. The machine has to be enrolled again to come back.
• Delete removes the entry from the active list and disconnects the agent for good, with no way back from the console.