TrinetraSees what you can’t.

Server monitoring that stays quiet until it matters.

Trinetra is free, self-hosted monitoring for Linux servers. One small daemon per server watches the box, keeps its own history and tells you on Telegram, Slack or email when something is wrong. When you have more than one server, the same daemon becomes a fleet master that groups alerts into incidents, routes them and escalates. No cloud, no Prometheus, no external database.

Memory
11.6 MB
CPU
~0.4% of a core
Core dependencies
Go stdlib only
Licence
FSL-1.1-ALv2
23:00:00

Nine servers, one of them the master. Nothing is wrong, so nothing is sent. Pick a failure.

9 online0 stale0 down
  • ops-mastermaster
    cpu 18%
    tag:master
  • api-01online
    cpu 44%
    tag:prod tag:api
  • api-02online
    cpu 39%
    tag:prod tag:api
  • db-01online
    cpu 31%
    tag:prod tag:db
  • web-01online
    cpu 27%
    tag:prod tag:web
  • web-02online
    cpu 24%
    tag:prod tag:web
  • cache-01online
    cpu 13%
    tag:prod
  • worker-01online
    cpu 45%
    tag:batch
  • edge-01online
    cpu 9%
    tag:edge
  1. The decision trail appears here, the same trail fleet explain prints.
Telegram0 alerts raised · 0 messages to you
  1. No messages. Nothing needs you.

A simulation of a Trinetra fleet in your browser, on the handbook’s timings: stale after 30 seconds, down after 2 minutes, a 30-second wait to group alerts, and a child delivering its own alert when the master has not confirmed it within 2 minutes. Time runs thirty times faster.

At a glance

What it is
Free, self-hosted monitoring for Linux servers: one small daemon per server, with alerts, history, a web dashboard, fleet incidents and a public status page.
Best for
One server up to a few dozen, on VPSes, home labs or small production fleets, when you want Telegram, Slack or email alerts without running Prometheus and Grafana.
Not for
Per-second metrics, custom application metrics, Windows or macOS hosts, or hundreds of nodes, where it has no published benchmark yet.
Compared with
Lighter than Netdata (11.6 MB against 100 to 350 MB), far less to run than Prometheus, Alertmanager and Grafana, and unlike Beszel or Uptime Kuma every server keeps alerting when the central one is down.
Price
Free to self-host at any scale, source-available under FSL-1.1-ALv2.

The whole box on one screen.

Containers, systemd units, filesystems, reachability, a 24-hour availability strip, CPU, memory, swap, load, temperature, network and processes, streamed live, with whatever is firing right now.

Trinetra dashboard: host strip, container and systemd counts, a 24-hour availability strip, live resource tiles and active alerts

The real web UI, trinetra-web, on a demo fleet of twelve servers. Host names, addresses and users are made up.

Rules you can read

Static thresholds, and an opt-in baseline that asks whether a reading is normal for this box. Both are plain arithmetic, so you can predict when an alert fires. No AI decides.

Set by command, not by hand

Every setting goes through the CLI or the terminal UI, which validate it and write one private config file atomically. Most changes apply without a restart.

Works when the network doesn’t

Every host alerts on its own. In a fleet, a child hands alerts to the master and delivers them itself if the master does not answer.

One message when it starts. One when it ends.

Each check is either firing or clear, and Trinetra only speaks when that changes. A disk that stays full for twenty minutes is one message, not twenty. Drag the threshold and count.

A CPU or memory alert also names the culprit, the top process and container, so it reads like cpu = 96.0 ≥ threshold 95.0 (top: ffmpeg 82%, container web 30%). Active alerts survive a restart, so a reboot does not re-send everything that was already known.

60708090100one sample a minute, for an hour
Checked on every sample23 messages
Trinetra2 messages
  1. disk:/ = 86.2 ≥ threshold 85.0
  2. disk:/ back to normal

Seven ways to reach you.

Each channel has its own severity floor, its own kinds of alert and its own quiet-hours rule, so the ops chat hears everything and email hears only criticals. Boot and recovery reports, a daily digest and a weekly rollup travel the same way.

ChannelWhat it needs
TelegramA bot token from @BotFather. The bot also answers /stats, history and controls.
EmailAn SMTP host, a sender and recipients
Slack, DiscordAn incoming-webhook URL
ntfyA topic, on ntfy.sh or your own server
GotifyA server and an application token
WebhookA URL, and a Go template if the receiver wants its own JSON

A dead-man switch on healthchecks.io can alert you while the box itself is off, which nothing on the box can do.

A fleet is three commands away.

Make one host the master and enroll the rest with a join code. The code pins the master’s certificate authority, so a child never trusts on first use, and from then on every child talks to the master over mutual TLS.

# on the master
sudo trinetra fleet init --address monitor.example.com
sudo systemctl restart trinetra
sudo trinetra fleet token create --tags prod --uses 3

# on each server, with the code the master printed
sudo trinetra fleet join swj1_...
sudo systemctl restart trinetra

A child keeps monitoring, storing and alerting exactly as it did alone. It also ships a copy of its history to the master through an outbox on disk, so an outage only delays the copy.

Fleet mode in 39 seconds, with sound.

Every node at a glance.

Online, lagging, down and revoked counts, a heatmap you can switch between CPU, memory, disk and load, top-five lists and link health. Ctrl-K or ⌘-K opens any child's full dashboard from the master's copy of its data.

Ten servers with one problem page you once.

Alerts from across the fleet are grouped into incidents. Each one has a timeline of what fired, who was told, what was held back and why. The same trail prints on the command line with trinetra fleet explain.

Routes and escalation you can test before you save.

Routes match on tag, node, rule and severity and hand an incident to a policy: the ops chat now, on-call after five minutes, everyone after fifteen. The route tester answers where a made-up alert would go.

Routes editor with ordered routes matching tags, nodes, rules and severities, and a continue toggle

Planned work pages nobody.

One-off silences by node, tag, rule or severity, and maintenance windows that recur by weekday in a named time zone. They are pushed to every child, so a child delivering on its own during an outage still honours them.

Tune a whole tier at once.

The master pushes thresholds, quiet hours and baseline settings to every node with a tag. Each node reports what it applied, and drift or a conflict shows up against its name.

Managed config: fragments by tag and each node's applied, drift and conflict status

Rules across the whole fleet.

Alert on a tier as a whole with a small grammar that is not PromQL. The master checks every rule every 30 seconds against each node’s replica.

avg(tag:api, cpu) > 75 for 5m            # the api tier is running hot
online(tag:prod) < 8 for 2m              # lost production capacity
absent(tag:staging, 10m)                 # staging went quiet
count(tag:web, disk > 90) >= 1 for 5m    # any web node nearly full

It installs nothing it cannot verify twice.

Every release ships a manifest of exact file hashes, signed by the build pipeline and co-signed offline by a maintainer. A host checks both against keys compiled into the binary it is already running, and treats GitHub and the network as untrusted transport.

trinetra update apply restarts under a guard. If the new daemon is not healthy within 90 seconds, it goes back to the build that was. You can also check a download by hand with sha256sum and OpenSSL, without trusting Trinetra at all.

What is true about this release?
$ sudo trinetra update applyInstalled and confirmed

Staged, smoke-tested, swapped in, restarted, and confirmed healthy. The version floor moves up to it.

Signed, tested, health-checked and reversible, in 47 seconds, with sound.

A status page your customers can read.

The same daemon that pages you can tell your customers. Pick what they depend on, publish it, and keep them posted while you fix it. No second tool, no extra subscription.

Publish services, not container names.

Tick the containers and systemd units your customers depend on and publish them as named services. Visitors see Checkout and its state with 90 days of uptime bars, never web-3. The page also has a history, an Atom feed and a JSON API.

Keep customers posted while you fix it.

An outage opens a status incident on its own. Responders post updates as they go, and each update can be echoed to your alert channels too.

A first run that asks, and lets you skip.

sudo trinetra cli on a new server walks through the web UI, a one-time enroll link for the first admin and where alerts go: Telegram, Slack, Discord, email, ntfy, Gotify or a webhook. Every step can be skipped.

Invite people from the terminal.

trinetra users lists, invites, re-roles and removes people, even while the daemon is stopped. A responder can ack alerts and run status incidents without admin rights.

Small, and measured.

Heavy features are separate programs. The web UI and the terminal UI talk to the daemon over a local socket, so their dependencies never reach it, and each runs only if you install it.

Measured on Linux containers with 8 vCPUs over about 72 minutes, sampling every 10 seconds, six times the default rate. A default install is lighter still.

Core daemon11.8 MB static on amd64, 10.9 MB on arm644.3 to 4.7 MB gzipped
Memory11.6 MB RSS on its own12.4 MB as a fleet child, 14.0 MB as a master with two children
CPUAbout 0.4% of one core0.6% as a child, 1.2% as a master with two children
DiskAbout 0.3 MB of history per hostafter the first hour, with tiered retention
Web UI plugin7.7 MB RSS, about 0.07% CPUand only when you turn it on
Third-party code in the coreNonethe daemon is Go's standard library, enforced by a test

Against the industry leaders.

The tools most teams weigh for a handful of Linux servers, from each vendor’s own docs and pricing pages, checked October 2026. Where a vendor publishes no number, the table says so.

Comparison of Trinetra with Datadog, Prometheus + Grafana, Netdata, Zabbix and Uptime Kuma for monitoring Linux servers
Compared onTrinetraDatadogPrometheus + GrafanaNetdataZabbixUptime Kuma
Self-hosted, no cloud accountYesNoYesYes, Cloud optionalYesYes
Alerts still fire if the central server is downYes, Every host decidesNoNoYesNoNo
Containers, services and disks found on their ownYesYesPartly, Extra exportersYesYes, With templatesNo
Incidents and escalationYesPartly, Paid On-CallPartly, Needs an on-call toolPartly, In CloudYesNo
Public status pageYes, With incidentsPartly, Incident ResponseNoNoNoYes
Silences and maintenance windowsYesYesYesPartly, In CloudYesYes
Rules across the whole fleetYesYesYes, PromQLPartly, Per nodeYesNo
Signed self-update with rollbackYes, Two signaturesPartly, Package managerPartly, Package managerPartly, Auto-updatePartly, Package managerPartly, New image
Custom application metricsNoYesYesYesYesNo
Windows hostsNo, Linux onlyYesYesYesYesNo, No agent
The numbers
Memory per host11.6 MB, measuredNot publishedNot published100–350 MBNot publishedNo agent
CostFree to self-hostFrom $15 per host a monthFree, or Grafana CloudAgent free, paid CloudFreeFree
LicenceFSL-1.1-ALv2, Apache-2.0 after two yearsProprietaryApache-2.0, AGPL-3.0GPL-3.0AGPL-3.0MIT

Pick Datadog when you want logs, traces and APM in one place and would rather pay than operate; Prometheus and Grafana for custom metrics and PromQL; Netdata for per-second metrics and anomaly detection; Zabbix for big mixed estates with SNMP gear and Windows; Uptime Kuma for checking sites from outside. Sources: Datadog pricing, Datadog Status Pages, Prometheus alerting, Netdata resource use, Zabbix escalations. The launch post has the long version.

Install it with one command.

Any Linux with systemd: Ubuntu, Debian, Raspberry Pi OS, Fedora or RHEL. Run it on the server you want to watch.

curl -fsSL https://www.infodivelabs.com/products/trinetra/install.sh | sudo sh

It picks the build for the server’s architecture, downloads the latest release and runs trinetra install --require-signed, which checks both signatures and every file hash before anything is installed. Then run sudo trinetra cli for the guided setup. Read the script first if you like.

Or step by step

  1. Download

    Pick the server’s architecture, not your laptop’s.

    Servers, VMs and NUCs

    mkdir -p ~/trinetra-download && cd ~/trinetra-download && arch=linux-amd64
    for b in trinetra trinetra-ctl trinetra-web; do
      curl -fsSL -o "$b" "https://github.com/InfoDiveLabs/trinetra/releases/latest/download/$b-$arch"
    done
    for f in manifest.json manifest.ci.sig manifest.maint.sig; do
      curl -fsSL -o "$f" "https://github.com/InfoDiveLabs/trinetra/releases/latest/download/$f"
    done
    chmod +x trinetra trinetra-ctl trinetra-web
  2. Verify and install

    Checks both signatures and every file hash, refuses on any mismatch, then starts one systemd service.

    sudo ./trinetra install --require-signed
  3. Set it up

    A guided setup turns on the web UI, gives you an admin sign-in link and asks where alerts go. Skip anything and do it later.

    sudo trinetra cli

    Alerts can go to Telegram, Slack, Discord, email, ntfy, Gotify or a webhook.

Running serverwatch? The same install moves your config and history across. The docs cover the web UI, channels, fleets and updates.

On a desk, a tablet or a phone.

Light and dark themes, an icon rail on a tablet and a bottom tab bar on a phone. Sign in with a passkey: Touch ID, Windows Hello or a security key. There are no passwords.

The dashboard in the light theme
The fleet page on a tablet with the icon rail

Questions people ask

How do I get notified when my Linux server goes down?
Install Trinetra on the server and choose where alerts go: Telegram, Slack, Discord, email, ntfy, Gotify or a webhook. It alerts when CPU, memory, disk, temperature, a container or a systemd service goes wrong, once when the problem starts and once when it ends. A server that loses power cannot report itself, so for that case add a dead-man switch such as healthchecks.io, or run a fleet: the master raises a node-down alert when a server has been silent for two minutes.
What is the most lightweight way to monitor a Linux server?
A single daemon that stores its own history and decides its own alerts, without an exporter, a scraper or a database. Trinetra's daemon measured 11.6 MB of memory and about 0.4% of one core, is built from Go's standard library alone, and keeps about 0.3 MB of history per host after the first hour. The web UI is an optional separate process.
How do I monitor Docker containers and get alerts when one stops?
Trinetra discovers every Docker container, systemd service, filesystem and top process on its own, with no per-container configuration. The dashboard shows which are up or down, and a container or service going down raises an alert to your channels, with a recovery message when it comes back.
Is Prometheus overkill for one server or a small fleet?
Often. For host metrics, dashboards and alerts it needs node_exporter on every server, a Prometheus server, Alertmanager and Grafana, plus config files you write yourself, and a single Prometheus server going down stops all alerting. It is the right tool for custom application metrics, PromQL and Kubernetes. For watching a handful of Linux servers, one small daemon per server does the job with far less to run.
How do I monitor multiple Linux servers from one dashboard for free?
Turn one server into a Trinetra master with sudo trinetra fleet init, then join the others with a one-time code. Every server keeps monitoring and alerting on its own and copies its history to the master over mutual TLS. The master shows the whole fleet, groups related alerts into incidents, routes and escalates them, and handles silences and maintenance windows. It is free to self-host at any number of servers.
What happens if the monitoring server itself goes down?
With Trinetra, every server still alerts. A fleet child hands its alerts to the master, and if the master does not confirm delivery within two minutes, the child delivers the alert itself, marked as a local fallback. History waits in an outbox on disk and catches up when the master returns.
Can I host a public status page myself?
Yes. Trinetra includes a public status page: pick the containers and services your customers depend on, publish them as named services with 90-day uptime bars, and post incident updates while you fix things. Visitors see the service name and its state, never your container names. It also publishes a history page, an Atom feed and a JSON API.
How do I stop getting too many alerts?
Trinetra speaks only when a check changes state, so a disk that stays full is one message, not one per minute. In a fleet, alerts with the same rule and severity become one incident, dependent servers fold into the incident of what they depend on, and silences and maintenance windows mute planned work. Each channel has its own minimum severity and quiet hours.
Is Trinetra free and open source?
It is free to use and self-host at any scale, commercially too, and source-available under the Functional Source License (FSL-1.1-ALv2): you may not offer it as a competing product, and each release becomes Apache-2.0 two years after it ships. It runs on Linux with systemd, on x86-64, ARM64 and ARMv7.
What's a lightweight alternative to Prometheus and Grafana for a small VPS?
Trinetra. It is one daemon per server that collects, stores and alerts on its own, using about 11.6 MB of memory, with no exporter, scraper, database or dashboard service to run. You get CPU, memory, disk, Docker and systemd monitoring with alerts on Telegram, Slack, email and more. If you need custom application metrics or PromQL, Prometheus is still the right tool.
How does Trinetra compare with Beszel and Uptime Kuma?
Beszel runs an agent on each server and a central hub; Uptime Kuma checks your services from outside and has polished status pages. Trinetra watches the inside of each server like Beszel, adds incidents, routing, escalation and a status page, and is the only one of the three where every server keeps alerting when the central server is down. Uptime Kuma pairs well with either for outside checks.

What is not done yet.

Written down so nobody has to find out.

  • Linux with systemd only. There are no macOS or Windows builds and no official container image.
  • Channel checks in the web UI. Saving a channel there does not test it end to end yet. The terminal UI does, and so does trinetra channel test.
  • Per-interface throughput alerts. Network throughput is collected and charted, but nothing alerts on it yet.
  • Fleet in the terminal and in Telegram. The terminal UI has no fleet screens yet, and the bot has no /fleet or /incidents commands. Ack and Silence 1h buttons on incident messages do work.
  • Telegram buttons trust the chat. Anyone in the enrolled chat can tap Ack, as anyone in it can already send commands.
  • No metrics export. Nothing speaks Prometheus or remote-write, and none is being built right now.

One eye on every server.

One light is on. Trinetra already told you which one.