One page for every machine you run.

I built Proxima to watch my own hosts and the services on them. It stays quiet when things are fine and it is loud exactly once, when something breaks.

One binary and a config file. No agent on every box.

I check on my machines at 2am, in a dark room, on a phone. The only thing that should glow is the thing that is wrong.

Devansh Parapalli
01What it does

Four things, done properly

Watches hosts and services

CPU, memory, disk, uptime and the state of every container. One line each. Click a line for the rest.

Alerts you can test first

Write a rule and see how often it would have fired over real history before you save it. No surprise pager at midnight.

Says what to do

Every alert carries the note you wrote when you were calm. Future you reads it at 2am and knows where to start.

Guesses where things are going

Trends continue as a dotted line, so you find out about the disk on Tuesday instead of Friday night.

02Weight

Lighter than the things it watches.

Proxima48 MB
Metrics stack940 MB
Full suite2.1 GB

Memory in use while idle, measured on my own boxes. The point is not that the other tools are bad. They do far more than this. I did not need far more.

03Running it

However you like

BINARY

Drop it on a box

One static binary and a YAML file. Point it at your hosts over SSH and it starts reporting.

Download →
DOCKER

Or a container

A single image, roughly 40 MB. Mount the config, expose one port, done.

See the compose file →
SOURCE

Read it first

The whole thing is small enough to read in an afternoon, which was one of the goals.

Browse the source →
DESIGN

Take the interface

The design system behind this site is documented and free to reuse in your own projects.

Open the docs →
04Try it

See your own machines after dark.

Accent