Checkmk

What Is Checkmk?

Monitoring sprawl is one of the most expensive problems in modern IT operations. A typical mid-size company might run Datadog for infrastructure, a separate tool for network devices, another for cloud resources, and yet another for synthetic checks — each with its own billing model, its own learning curve, and its own data silo. The bill adds up fast, and the operational overhead of correlating alerts across four dashboards is rarely discussed in vendor marketing.

Checkmk exists to collapse that fragmentation into a single platform. Built in Munich by Mathias Kettner starting in 2008 — originally as a plugin to extend Nagios — it has evolved into a standalone monitoring system that covers servers, networks, cloud services, containers, databases, and applications. The open-source Raw Edition handles thousands of hosts at zero cost. Commercial editions layer on distributed monitoring, synthetic testing, OpenTelemetry ingestion, and enterprise support.

What distinguishes Checkmk from cloud-native competitors like Datadog or New Relic is the deployment model. Every edition runs on your infrastructure. Your monitoring data never leaves your network unless you explicitly choose the SaaS option. For European organisations bound by GDPR, operating in regulated industries, or simply unwilling to send telemetry to US-owned cloud platforms, that architectural choice matters more than any feature checkbox.

Checkmk GmbH now employs over 200 people across offices in Munich and the US, with team members in more than 35 countries. The company is bootstrapped — no venture capital, no private equity — which means product decisions are driven by engineering priorities rather than growth-at-all-costs pressure.

Key Features

Unified Infrastructure Monitoring

Checkmk's core strength is breadth. A single installation monitors Linux and Windows servers via agents, network devices via SNMP and streaming telemetry, cloud resources on AWS, Azure, and GCP through special agents, VMware and Proxmox virtualisation, Kubernetes clusters, and Docker containers. Over 2,000 monitoring plug-ins ship out of the box — covering everything from Apache web servers to ZFS storage pools — and most require no configuration beyond enabling them.

The auto-discovery engine is genuinely useful. Point Checkmk at a new host and it inventories running services, open ports, filesystems, and hardware automatically. In practice, adding a typical Linux server to monitoring takes under two minutes from agent installation to full dashboard visibility.

Rule-Based Configuration

Rather than configuring thresholds and alerts per-host, Checkmk uses a rule-based engine where you define policies once and apply them across matching hosts and services via labels, folders, and tags. Set filesystem warning thresholds at 85% for all production servers, override to 95% for database hosts, and apply different notification rules for business hours versus nights — all without touching individual host configs.

This model scales far better than per-host configuration for large environments. It also introduces a meaningful learning curve. Administrators accustomed to point-and-click monitoring tools will need to invest time understanding how rules inherit and override before the system feels natural.

OpenTelemetry and Synthetic Testing

Version 2.4, released in May 2025, added two capabilities that significantly extend Checkmk's reach. The integrated OpenTelemetry collector ingests metrics via gRPC and HTTP, and can also pull from Prometheus endpoints. This bridges the gap between traditional infrastructure monitoring and modern application observability without requiring a separate tool.

Synthetic monitoring lets teams upload test robots that simulate user interactions — login flows, checkout processes, API call sequences — and run them from distributed test nodes. Test robots are managed centrally and deployed via the Agent Bakery, and the system supports synthetic testing in isolated offline environments, which is unusual for this category.

Distributed Monitoring

For organisations with multiple sites or data centres, Checkmk's distributed monitoring connects separate instances into a unified view. Each remote site runs independently and continues functioning during network outages, while the central site aggregates data for consolidated dashboards and reporting. This architecture avoids the single-point-of-failure problem inherent in centralised SaaS monitoring.

REST API and Automation

The REST API exposes nearly every function — host management, user administration, downtime scheduling, rule configuration. This enables integration with Ansible (via an official Checkmk Ansible Collection), Terraform, and CI/CD pipelines. Infrastructure-as-code teams can provision monitoring alongside infrastructure, which eliminates the manual step of "now go add it to monitoring" that plagues many operations teams.

Agent Bakery

Commercial editions include the Agent Bakery, which packages monitoring agents with custom plug-ins and configurations and distributes them automatically. For environments with hundreds of hosts, this eliminates the tedium of manual agent deployment and ensures consistent configuration across the fleet.

Pricing

Checkmk's pricing model is refreshingly different from the per-host billing that has become standard in cloud monitoring. Commercial editions price by the number of monitored services — a metric that correlates with actual monitoring load rather than arbitrary host counts.

The Raw Edition is completely free and open-source under GPLv2. There are no artificial limits on hosts or services, no feature gates designed to force upgrades, and no telemetry sent back to Checkmk. For small-to-medium environments, this is one of the most generous free monitoring platforms available.

Enterprise starts at approximately €175/month for 3,000 monitored services (roughly 100 hosts). This includes distributed monitoring, advanced analytics, the Agent Bakery, and unlimited support tickets. Pricing scales with service count, and Checkmk provides a 30-day free trial of commercial features.

Cloud (Self-hosted) adds cloud-native capabilities and Azure/AWS Marketplace deployment at roughly €300/month. The MSP Edition at approximately €350/month adds multi-tenancy and white-labelling for managed service providers.

A fully managed SaaS edition is also available for teams that want Checkmk without maintaining the server infrastructure, though pricing requires direct engagement with sales.

Compared to Datadog — where a single host with infrastructure monitoring alone costs $15-23/month before adding APM, logs, or synthetics — Checkmk's all-inclusive approach typically delivers substantial savings at scale. A 500-host environment on Datadog can easily cost $10,000+/month; the equivalent Checkmk Enterprise subscription is a fraction of that.

EU Compliance & Privacy

Checkmk's compliance story starts with architecture rather than paperwork. Because every edition can run on-premise, monitoring data stays within your infrastructure by default. There is no mandatory cloud component, no telemetry phoning home, no third-party data processor to evaluate. For GDPR compliance, this is the simplest possible posture: if data never leaves your network, transfer impact assessments become irrelevant.

Checkmk GmbH is a German company headquartered in Munich, fully subject to EU jurisdiction. The company holds ISO/IEC 27001:2022 certification audited by TÜV SÜD — covering its European operations — and provides Data Processing Agreements for customers using commercial editions. The certification process is being extended to the US subsidiary.

For regulated industries — finance, healthcare, government, critical infrastructure — the combination of on-premise deployment, German legal jurisdiction, and ISO 27001 certification addresses most procurement requirements without the lengthy due diligence that US-headquartered SaaS vendors trigger.

Who It's Best For

Infrastructure-heavy organisations running hundreds or thousands of servers, network devices, and cloud resources that need a single monitoring pane rather than a patchwork of point solutions.

Security-conscious and regulated industries — finance, healthcare, government — where monitoring data must remain on-premise and under direct organisational control.

Cost-conscious operations teams who have watched their Datadog or New Relic bills climb with every new host and want a pricing model that does not penalise infrastructure growth.

Linux-centric environments where Checkmk's Nagios heritage and deep Linux integration feel natural, and where the rule-based configuration model aligns with infrastructure-as-code practices.

Teams seeking polished, consumer-grade dashboards or a pure SaaS experience with zero operational overhead may find Checkmk's functional UI and self-hosted model less appealing.

The Verdict

Checkmk is not the prettiest monitoring tool on the market, and it will not hold your hand through setup the way a SaaS platform might. What it offers instead is depth, control, and economics that cloud-native vendors cannot match. The open-source edition is genuinely generous, the commercial pricing is fair, and the on-premise model delivers EU compliance by architecture rather than by contract. For European organisations that take both monitoring coverage and data sovereignty seriously, Checkmk deserves a place on the shortlist.

Frequently Asked Questions

Is Checkmk open source?

The Raw Edition is fully open-source under GPLv2, available on GitHub with an active contributor community. Commercial editions (Enterprise, Cloud, MSP) build on the open-source core but add proprietary features. The open-source edition has no artificial limits — you can monitor thousands of hosts without ever paying Checkmk GmbH.

How does Checkmk compare to Datadog?

Checkmk covers similar monitoring ground — infrastructure, cloud, containers, applications — but runs on-premise rather than as SaaS. Pricing is service-based rather than per-host, which typically costs significantly less at scale. Datadog has a more polished UI, stronger APM capabilities, and a broader SaaS integration ecosystem. Checkmk wins on data sovereignty, total cost of ownership, and the ability to run entirely air-gapped.

Can Checkmk monitor Kubernetes clusters?

Yes. Checkmk's Kubernetes special agent connects to the cluster API server to retrieve node states, pod health, container metrics, and deployment status. It supports namespace-level monitoring and integrates with Prometheus endpoints for application-level metrics within the cluster.

What is the Agent Bakery?

The Agent Bakery is a commercial feature that packages the Checkmk monitoring agent with custom plug-ins and site-specific configuration, then distributes it automatically to monitored hosts. It supports both Linux and Windows agents and integrates with the rule-based configuration system, so agent packages update automatically when monitoring rules change.

Does Checkmk support OpenTelemetry?

Yes, as of version 2.4 (May 2025). The built-in OpenTelemetry collector ingests metrics via gRPC and HTTP push protocols and can also pull from Prometheus endpoints. This allows teams to consolidate application-level observability data alongside traditional infrastructure monitoring within a single platform.