Operating systems and architectures
The agent runs as a service and connects outbound to Uptimo.
- Linux on amd64 and arm64
- Windows on amd64
- Linux installation through systemd
- Windows installation as a scheduled SYSTEM task
Platforms and architecture
Check from the outside. Measure inside the server. Join both in one incident.
Uptimo works through two paths: hosted checking locations observe reachable services, while the optional agent sends measurements from the host.
Both paths end in the same product. You see not only that a service failed, but also what happened on the affected server at the same time.
Compatibility
Environments the agent can recognise and describe
The first row identifies reported hardware or virtualisation environments. The second names the hosted product's technology stack. None of the marks represents customers or partnerships.
Recognised systems and environments
LinuxWindowsDockerAMDIntelNVIDIAQEMUProxmoxVMware
Technology inside the hosted Uptimo service
Next.jsPostgreSQLGoDocker
How signals move through Uptimo
External availability and internal host metrics remain separate measurement paths, but are evaluated together.
Checking locations test services
HTTP, ping, TCP, DNS, and TLS run on the monitor's interval. Every assigned location keeps its own status and incident.
The agent reports the host
The Go binary collects locally and sends outbound to Uptimo. It opens no port and needs no inbound connection.
Rules confirm before they shout
Several failures confirm an outage. Server rules separate warning and critical, minimum duration, and recovery.
Notifications and status pages share context
Incidents can be sent through email, SMS, webhook, Slack, Teams, or Telegram and explained on a status page.
What the agent supports today
The agent supports Linux on amd64 and arm64, plus Windows on amd64. The details are listed below.
Host metrics
The agent collects measurements exposed by the operating system.
- Total and per-core CPU, load, memory, and swap
- Filesystems, inodes, and block-device I/O
- Network interfaces and throughput
- Temperature sensors and top processes
- NVIDIA and AMD GPUs when the required system data is available
Virtualisation and hardware
Uptimo shows the model and environment as reported by the guest.
- Including AMD, Intel, and Arm processor models
- Recognised environments such as QEMU/KVM, Proxmox, VMware, or VirtualBox
- No direct connection to a hypervisor API
- Physical host data appears only when the guest system exposes it
Docker
Container data is a deliberate extra permission and not part of agent collection by default.
- State, health, restarts, image, CPU, memory, and network
- Docker socket mounted read-only
- Access remains opt-in because the socket is highly privileged
- Container alert rules are opt-in as well
Deliberate boundaries
What deliberately does not happen
No process command lines
Uptimo collects names and measurements, but not the full command lines of running processes.
No inbound agent port
The agent accepts no incoming connections. Data transfer always starts from the monitored host.
No vendor partnership implied by a logo
A recognised brand describes the environment. It is not an endorsement or certification by that vendor.
FAQ
Platform questions
Does the Uptimo agent need an inbound port?
No. The agent collects locally and sends reports outbound to Uptimo. It does not open its own network service.
Does Uptimo integrate directly with QEMU or Proxmox?
No. Uptimo does not connect to a hypervisor API. The agent can recognise and display the virtualisation environment reported by the guest operating system.
Does the agent run on Linux and Windows?
Yes. Supported targets are Linux on amd64 and arm64, and Windows on amd64.
Why is Docker not enabled automatically?
The Docker socket grants broad access to the host. Container monitoring must therefore be enabled deliberately, even when the socket is mounted read-only.
Inspect each capability in detail.
Every feature page shows measurements, settings, and limits with captures from the running product.