Standby
Monitor every server. Page the right person. Prove it was handled. One agent for Linux and Windows, with monitoring, on-call, security and compliance in one place, and a status page that stays up when yours do not.
Everything Standby does, area by area
From the first machine you enrol to the auditor who reads your evidence.
Paging that reaches a person, and only once.
Alerts become incidents, the right person is paged by severity, and a storm from one source is capped instead of paging over and over.
Chains by severity and label, paging by voice, text or the app through your own telephony account.
A coverage board, rotations, swaps and a calendar, with the hours nobody covers shown.
When a large part of the fleet goes quiet you get one alert, not one per machine. A critical alert is never swallowed.
Active alerts, your own work, shift handoff, and runbooks suggested on the incident.
A Windows app with tray alerts and an alarm that rings until someone acknowledges.
Overlapping time counted once, leave, and a payroll export.
Gaps shown as gaps. Checks from outside.
Metrics, logs and checks from probe servers you place, with missing data never drawn as zero.
From Debian, Ubuntu, RHEL, Alpine and Windows machines, with dashboards you lay out yourself.
Web, port, ping, certificate and DNS checks. With two or more locations, a public incident opens only when at least two agree.
Know when a backup or a cron job did not run, not only when a server is down.
Service level objectives with burn-rate paging, and capacity forecasting.
Health and an inventory read from your live web servers and databases.
Every machine's page lists what the agent collects there, so a blank chart is never mistaken for a quiet one.
Security on what is really installed.
Vulnerabilities matched to each machine, a threat feed you can act on, and fixes that wait for a person.
On Debian and Ubuntu matched to the exact versions installed, with the upgrade that closes each; on RHEL and SUSE the fixes waiting; on Windows the missing updates.
Failed sign-ins, injection attempts and web-shell detections, and a ranked queue of what needs you first.
On Debian and Ubuntu, updates in maintenance windows to a few machines first, stopping at the first failure.
Firewall policies and drift, a web application firewall, and IP control.
Auto-remediation with approval. Isolating a machine takes a second person.
Access keys, SSH key rotation, secret rotation and a vault, with a recorded terminal on your Linux servers.
Audit evidence, scored from what your machines do.
Technical controls scored live, people and process controls confirmed by your team, and evidence an auditor can open without an account.
ISO 27001, SOC 2, NIS2, DORA, GDPR, PCI DSS, Cyber Essentials, HIPAA, the CRA and the EU AI Act.
A risk register, a policy library, policies mapped to controls, and a Statement of Applicability.
Deadline clocks for the reports NIS2, DORA, GDPR, the CRA and the EU AI Act require.
An audit programme, nonconformities and corrective actions, and a certificates register.
Read-only links that expire, or an auditor portal that shows only their engagement.
Your posture per framework and the documents customers ask for, on a page of its own.
A status page that stays up when yours do not.
In your own brand, on a server of its own, and resolved only when the alert has stayed quiet.
Your customers can read it while the systems it reports on are down.
An incident closes only after the alert has stayed quiet, and reopens if it fires again.
Per-minute uptime bars, SLA targets per component and availability reports.
Email with double opt-in, a feed, and Slack, Discord and Teams.
Your own brand on the page your customers read.
Show live status on your own site with a badge or an embedded widget.
Every machine, and the room it stands in.
Servers and laptops in one place, a service desk with changes and approvals, and the datacenter itself.
Debian, Ubuntu, RHEL, SUSE, Arch, Alpine and Windows, servers and workstations, installed with one command.
Scripts, host access, fleet updates and auto-update policies from one place.
Checked on a schedule, with maintenance windows and recovery planned around them.
Change plans with a blast radius and an approval queue, and a calendar that spots clashes and gaps in cover.
Staff tickets, problems, a knowledge base, SLA policies and a service portfolio.
IP addresses, DNS with a console, switches, every server in its rack, hardware health, power and physical access.
Your install, your data, your rules.
Single sign-on, modules you switch on as you need them, and AI that drafts but never acts alone.
Two-factor codes, passkeys, single sign-on, SCIM and IP allow lists, plus service accounts.
Switch on only the areas your team uses; the rest stays out of the way.
AI staff draft investigations and fixes with your own providers and a spend cap. Every fix waits for approval.
KStack alerts arrive as incidents, and KStack shows the availability Standby reports for each server.
Alert sources, telephony, chat notifications, a notification log, webhooks and an API.
The licence check sends your host name, enrolled count and an install fingerprint; the vulnerability match sends each machine's software list.