Capability

Know the moment a server breaks, and why

brynko pulse installed in one click: alerts within seconds by email, WhatsApp, Telegram or Slack, fixes with your approval, and an alert even when a whole server goes down.

Create account See the full flow

brynko pulse Linux and Windows Disks and memory Services and containers Websites and SSL Logs and heartbeats Email WhatsApp Telegram Slack Webhooks

In your words

Ask it like this

No syntax to learn. These are real requests, phrased the way people actually phrase them.

›turn on monitoring for the web servers ›alert me on WhatsApp if the shop stops answering ›why did I get a disk alert on db-1 ›restart nginx by itself if it stops, but ask me for anything else ›silence alerts for 30 minutes while I deploy ›which servers have nothing watching them

Capability

What it does here

Everything below is what the agent does today, not a roadmap.

Installs brynko pulse, our open-source monitor, on Linux and Windows servers in one click, checked against the release checksums
Watches disks, memory, CPU, services, Docker containers, ports, websites, SSL certificates, logs and cron heartbeats
Alerts within seconds by email, WhatsApp, Telegram, Slack or webhook, quiet until a problem lasts
Restarts a failed service or container for you, after your approval or by itself, a limited number of times
The dead-server alert emails you when a whole server goes silent, and again when it is back
Investigate with AI on any alert: the agent goes and finds the cause

What it looks like

One question, one answer, one fix

The checks on the left of each reply are the reads it did before committing to an answer. That is the difference between a diagnosis and a guess.

Every exchange ends in a verified outcome. It goes back and confirms the result rather than assuming the fix worked.

brynko devOps Agent

monitor web-1 and tell me on WhatsApp if the shop goes down

installed pulse found nginx and php-fpm added a website check

pulse is running on web-1. It watches the disk, memory, nginx, php-fpm and https://shop.example.com, and alerts your WhatsApp channel. Want it to restart php-fpm and nginx by itself if the shop stops answering?

yes, but ask me first

added the fix set it to ask sent a test alert

Done. If the shop stops answering, you get the alert with the fix waiting for your approval. A test alert just went to your WhatsApp.

Monitored · alerts on WhatsApp

Common cases

The ones that cost you an afternoon

Each of these is a specific failure with a specific set of checks behind it, not a general promise to help.

Customers find the outage first

The site has been down for an hour and the first anyone hears of it is a customer on the phone.

What it does. pulse checks the site, the services behind it and the disks they live on, and alerts you within seconds by the channel you actually look at.

The whole server died, so nothing alerted

A monitor running on the server goes quiet with it. A power cut or a lost network looks exactly like everything being fine.

What it does. With the dead-server alert on, pulse checks in with the brynko relay every minute, and the relay emails you after 5 minutes of silence and again when the server is back.

Too many alerts, so nobody reads them

A check that flaps sends forty messages in an hour, and the real one is lost among them.

What it does. An alert waits for a problem to last, recovers with a margin, reports flapping once, and folds a storm of failures into one message.

The fix is always the same restart

Every few weeks php-fpm hangs, someone is woken up, and the fix is one restart.

What it does. Give the monitor a fix and pulse restarts it for you, after your approval or by itself, a limited number of times, and tells you what it did.

An alert says what, not why

You know the disk is full; finding what filled it is another half hour on the server.

What it does. Investigate with AI hands the alert to the agent, which runs the checks you would have run and tells you the cause.

Setting up monitoring is a project

A full monitoring stack needs its own server, its own care and someone who knows it.

What it does. One click per server installs pulse; the app gives you forms built from the server's own disks, services, containers and ports, and every server at a glance.

Start to finish

What happens between the question and the fix

You turn monitoring on
Pick a server; the app installs pulse over the SSH you already have and checks the download first.
It suggests what to watch
Disks, memory and CPU from the start, plus the services, containers and ports it finds on the server.
You choose who hears about it
Email, WhatsApp, Telegram, Slack or a webhook, and the dead-server alert for the server itself.
It alerts within seconds
Only when a problem lasts, once, with a fix ready to approve where you gave it one.
You ask why
Investigate with AI goes from the alert to the cause, and proposes the fix.

The part that matters

Reading is free. Changing asks first.

Reads run instantly and need no permission, because reading cannot break anything. Anything that changes a system, whether that is a restart, an edit, an install or a delete, stops and tells you what it is about to change, on which server, and why. You see it written out, as the command it will run or a red and green diff of the file, so you are approving the actual thing rather than a description of it. Changes are backed up first, so undoing one is a click.

Read the security model

Questions

Monitoring, specifically

What is brynko pulse?

Our free, open-source server monitor (GNU AGPL v3). One small program per Linux or Windows server, configured with plain files, that you can also use on its own from the command line. The app installs it and gives you screens for everything it does.

Does it open a port on my servers?

No. pulse only connects out, to the channels you choose and, with the dead-server alert on, to the brynko relay.

What happens when the whole server goes down?

The dead-server alert covers it. pulse checks in with the brynko relay every minute; after 5 minutes of silence the relay emails you, and when the server is back it emails again.

Will it fix things without asking me?

Only if you tell it to. Self-healing is off until you add a fix to a monitor, and each fix either waits for your approval or runs by itself, a limited number of times an hour.

What does monitoring cost?

pulse is free. Alerts sent through your own email, Telegram, Slack, WhatsApp or webhook cost nothing extra; the dead-server alert email is free with credits on your account, and messages through the brynko relay are charged per message.

Does it replace Datadog or Grafana?

For server health and alerts, often yes. It does not collect application traces or keep months of metrics for graphs; if you need those, keep that tool alongside it.

Also covered

The rest of the stack

Docker, without memorising the flags

Inspect containers, read logs, check stats, restart services and run Compose stacks, just by describing what you want.

Your reverse proxy, explained and fixed

Test configs before they go live, read the right log, and reload safely, on nginx, IIS or Tomcat.

From code to a running site, and know what shipped

It builds the deployment with you: the deploy script, Docker, nginx and pipeline files, a ready server, then the release itself, checked afterwards.

Every script in one place, written with you

A library for every script your team runs on its servers: written with the agent or by you, organised in groups, every version kept, run with one click.

Ask your database what is wrong

Read-only checks and queries over your existing SSH connection, with credentials encrypted at rest.

Wildcard HTTPS, sorted in one step

Issue trusted, auto-renewing certificates, wildcards included, and get the paths handed straight back.

Try it on something that already annoys you

Point it at one server. You will know within an hour whether it earns its place.

Create account See pricing