Connect, provision, inspect, and operate servers.
A ServerChirp server is a supported Ubuntu machine with the outbound agent installed. Its overview combines connection health, resource usage, managed services, applications, recent operations, and issues that need attention.
The agent publishes a presence heartbeat every 15 seconds and a baseline resource snapshot every 60 seconds. While someone watches live process metrics, ServerChirp asks the agent for a temporary five-second sampling lease. The faster rate expires automatically when it is no longer renewed.
If a connected server stops responding, ServerChirp probes it before recording the cold status transition. A later agent hello or heartbeat restores the connection without requiring a dashboard polling loop.
From a server you can manage:
You can rename a server, assign a color, change managed settings, reboot it, transfer it to another team, or remove it. Destructive actions use explicit confirmation and are recorded with their actor.
For a provider-created server, the removal dialog lets you choose whether to destroy the cloud instance too; that option is selected by default. If you keep the provider resource, ServerChirp removes its records and applications while the cloud instance continues running and generating provider charges.
The agent connects outward to ServerChirp over an authenticated broker. Commands use signed request/reply messages with replay protection. Console input is bound to the active agent process with a challenge nonce and per-session sequence numbers.
This keeps the server manageable without opening a new inbound agent port.
