For IT teams
Your own servers, from the inside and out.
You run Linux servers for your own company: an internal application, a portal, a database. Lynx Heartbeat shows which of them needs attention, what is out of date and what is about to run full — and sums up the week every Monday.
What IT teams run into
Which server needs attention right now?
Ten servers, several tools, and the full disk is reported by a colleague.
How Lynx helps
The agent reports CPU, load, memory, disks, network and the state of MySQL, PHP-FPM and Apache every minute. The overview shows which server needs attention first.
Updates and known vulnerabilities pile up
Nobody can follow every security notice for every package on every server.
How Lynx helps
Every night Lynx compares the installed packages with public vulnerability databases and the security notices of the distribution. A finding is critical only when the affected service is reachable from the outside; pending security updates and required restarts are listed per server.
Backups and cron jobs fail silently
A backup that stopped three weeks ago is noticed on the day you need it.
How Lynx helps
A heartbeat monitor expects a call from your job and alerts you when it does not arrive in time. The agent also reports a backup that is older than it should be.
Management wants to know how the week went
Availability and incidents end up in a spreadsheet that someone fills in by hand.
How Lynx helps
The weekly report arrives every Monday at 07:00: availability, incidents compared with the week before, and what will expire or fill up within the next 30 days.
Who may change what?
Shared admin logins and one password for everybody are hard to justify.
How Lynx helps
Every user has their own login with an optional second factor, which the owner can make mandatory. Roles decide who manages users, who changes alert rules and who only reads.
An agent on our servers? Only a careful one.
Anything that runs on your servers has to justify the rights it has.
How Lynx helps
The agent runs under its own unprivileged account, opens no port and makes one outgoing HTTPS connection. It never sends file contents, command lines or environment variables, and its updates are signed.
Which plan fits
Start · Team
Team is the plan for companies with their own IT. It adds Slack, Microsoft Teams and webhook, a second factor that is mandatory for everyone, status pages on your own domain and the AI summary in the alert.
| Included | Start | Team |
|---|---|---|
| Servers included | 3 | 15 |
| Monitors included | 10 | 50 |
| Status pages | 1 | 3 |
| Alerts to Slack, Microsoft Teams and webhook | not included | included |
| Second factor mandatory for the whole team | not included | included |
| Status pages on your own domain | not included | included |
| AI summary in the alert, with your own key | not included | included |
Questions
Which servers does Lynx Heartbeat support?
The agent runs on Ubuntu 20.04 to 26.04 with systemd, on amd64 and arm64. Other distributions are not released yet. Checks from the outside work for any website or service that is reachable from the internet, whatever it runs on.
Does the agent need root?
No. It runs under its own account without root rights and without sudo, opens no port and talks to Lynx over one outgoing HTTPS connection on port 443.
Does Lynx install updates for me?
No. Lynx shows pending updates, security updates, required restarts and known vulnerabilities per server. Installing them stays with you.
Where is my data stored?
On servers at Hetzner in Germany (Nuremberg), with the encrypted backup in Falkenstein. The outside checkers are in Nuremberg, Helsinki, Ashburn (USA) and Singapore; they only fetch the public addresses of your monitors and send the results to the central.
How many servers do you look after?
Start the trial and install the agent on your first server with one command.