Skip to content

The full picture of your server's health.

CPU, memory, disk, network, PHP-FPM, uptime, site health checks — all in one dashboard with notifications to Telegram and email.

  • 7 days free
  • No card required
  • Payment in rubles
prod-01 203.0.113.21 · sampled every minute
CPU28%
CPU, 15 min avg63%
Memory61%
Disk48%
Network12.4Mbps
Uploading0.42
100% threshold 90% 50% 0% above threshold 28 min one-off spike — no alert
−60 min −45 min −30 min −15 min now

prod-01CPU at 91% on average over 15 minutes

Telegram Email
60s
the on-server agent sends a fresh sample every minute
25
values in every sample: from CPU to inodes
15min
averaging window: a one-off spike does not raise an alert
30days
of APM history: p95 and errors for every endpoint

What's tracked

Hardware, network and sites on one screen.

The agent takes a sample every minute. The server dashboard shows current values and charts for an hour, 6 hours, a day or a week.

CPU and Load Average

Current CPU load, load average 1/5/15 min, number of running processes.

What you see CPU % Load 1/5/15 Temperature Uptime

Memory and Swap

RAM and swap partition usage. See when memory is running out before the OOM killer kills a process.

What you see RAM % Swap % Used / total

Disk and inode

Device, mount point, FS type, size/used/free, usage percentage, unallocated space.

What you see Partitions inode Disk I/O Forecast

Network RX/TX

RX/TX bytes and packets per network interface. Traffic history.

What you see RX TX Packages Interfaces

CPU Steal

Detects virtualization overhead. Shows how much CPU time the hypervisor takes from your VM.

What you see Steal % Host overselling

PHP-FPM

Requests/second, active processes, total processes. See whether you have enough workers for the current load.

What you see req/s active total

Site availability

HTTP status, response time, online/offline detection for every site.

What you see online / offline Response time

Services and daemons

Nginx, MySQL, Redis and Supervisor processes are checked every 5 minutes. If a service fails, you get an alert.

What you see systemd Supervisor failed

Diagnostics

See right away what is loading the server.

The process hogging the CPU, the partition running out of space and the site short on workers are found in a minute — without SSH and top.

Every server process under control

Running processes sorted by CPU, memory and RSS. Filter by PID, user or command and send a signal right from the panel.

  • Load average and the top consumer sit above the table
  • SIGTERM for a graceful exit, SIGKILL for an immediate one
  • System processes are protected from an accidental signal
Processesprod-01 · 127 processes
ProcessCPU ↓
php artisan horizonPID 15210 · RSS 96 MB
SIGTERM 3.1%
php-fpm: pool shopPID 2291 · RSS 312 MB
SIGTERM 2.4%
mysqldPID 8891 · RSS 724 MB
SIGTERM 1.8%
nginx: workerPID 1204 · RSS 94 MB
SIGTERM 0.3%
Load average · 1 min0.64

Alerts

Hear about failures first. No false alarms.

Every alert type can be routed to any number of channels. You set the thresholds for CPU, memory and disk.

Alert rules

Alerts for real problems, not for spikes

CPU and memory are compared against a 15-minute average, so a short peak does not raise an alert. For disk, the panel warns at your threshold and again at 90% and 95%.

  • CPU, memory and disk thresholds from 50 to 95%
  • One alert per incident, no repeats
  • Rules for CPU, RAM, disk, SSL and server unreachability
Alert thresholdsprod-01 · every 5 minutes
ResourceThreshold
CPU15-minute average: 38%
90%
Memory15-minute average: 61%
90%
Disk/mnt/data: 69%
80%90%95%
Sent14:02 · Telegram
Channels

Notifications to the right channel

Telegram, email and the in-app inbox. Each channel has its own delivery hours: outside the window, alerts are not lost — they wait until it opens.

  • Email, Telegram, in-app notifications
  • One alert type to any number of channels
  • A test message checks the channel before the first incident
DeploykinChannel connectedtest notification delivered
Deploykinprod-01CPU at 93% on average over 15 minutes
Deploykinshop.example.comSSL certificate expires in 14 days

What Deploykin will warn you about

  • Server unreachable

    No response to monitoring for more than 15 minutes.

  • High CPU load

    The 15-minute average is above the threshold — 90% by default.

  • High RAM usage

    The same rule for memory: a 15-minute average.

  • Disk filling up

    At your threshold, then again at 90% and 95%.

  • Service failed

    Nginx, MySQL, Redis or another systemd service entered the failed state.

  • Daemon down

    Horizon or a queue worker went down and Supervisor could not bring it back.

  • SSL certificate expiry

    14, 7 and 3 days before expiry, and on the day it expires.

  • Deploy failure

    A site deployment finished with an error.

  • Backup failure

    A backup profile did not complete.

  • SSH login from a new IP

    A successful login from an address not seen before.

  • Site security

    Files changed since the last deploy, or a dependency vulnerability was found.

  • Denied MCP call

    An AI client was denied: wrong scope, access level or a dangerous command.

APM and analytics

See what is slow. Without a line of code.

Latency, errors and traffic are computed from the Nginx access log: nothing is installed in your code and nothing is loaded on the page.

  1. APM

    p50, p95 and p99 for every endpoint

    Latency percentiles and error rate for every endpoint. Not a line of code in your application — metrics are computed from the web server logs.

    • /orders/8123 and /orders/9977 are one endpoint, /orders/:id
    • Percentiles are computed correctly for 24 hours, 7 and 30 days
    • Every request over a second is stored individually
    • Works with Laravel, WordPress and someone else's legacy system
    Performanceapi.example.com
    7 days
    Endpointp95
    POST
    /orders/:id/checkout
    3000 ms
    GET
    /reports/revenue
    1000 ms
    GET
    /orders/:id
    500 ms
    GET
    /
    100 ms

    Requests over a second

    12:38
    /orders/7760/checkout
    5003.10 s
    12:41
    /orders/8123/checkout
    2004.82 s
    412kRequests
    640 msp95
    0.42%Errors
  2. Site analytics

    Analytics for every site

    Requests, unique visitors, traffic, HTTP statuses, top pages and referrers. Granularity — by day.

    • Stats are collected on the server from logs — without Google Analytics or pixels.
    • Zero scripts on the page: nothing loads for the visitor.
    • Separate stats for each site in the project — out of the box.
    shop.example.comAnalytics · from the Nginx access log
    Today7 days30 days
    Requests338.0k
    Visitors74.2k
    Traffic16.8 GB
    Errors0.4%

    Top pages

    /
    128.9k
    /catalog
    56.7k
    /cart
    37.4k
    96.2%2xx
    3.4%3xx · 4xx
    0.4%5xx

Metric collection

Metrics are read by an agent on the server itself.

Deploykin installs its own metric collection agent on the server. It reads the values on the spot and pushes them to the panel itself — continuously, with nothing for you to do.

  • Installs and updates itself — on servers already in production there is nothing to do by hand.
  • Processes, network interfaces and the website log summary are computed right on the server.
  • The agent build is verified against its checksum before installation.
  • If the agent goes quiet, the panel raises an incident instead of showing yesterday's numbers.
prod-01On-server agent
Online
Versionv0.1.2
Samplejust now

Next sample in60 s

What the agent collects

  • CPU, memory, disk and network
  • Processes and network interfaces
  • Site log summary
ChecksumMatches

In the panel 203.0.113.21 Connect done in 4 min 52 s

Be the first to know about problems.

Connect a server — and monitoring and alerts start working automatically.

  • 7 days free
  • No card required
  • Human support

We use cookies and the Yandex Metrica web-analytics service (including Session Replay) to improve the site. Details are in the privacy policy.