Glassmkr vs Datadog: bare-metal monitoring without the per-host scaling problem.

What’s the same

Both products do infrastructure monitoring at their core. Both ship agents that run on your servers. Both detect failure conditions and route alerts to notification channels. Both have dashboards, alert rules, and integrations with the tools your team already uses.

Both can monitor Linux servers running on bare metal. Both support multi-channel alerting (Slack, email, PagerDuty, webhooks).

If you only need monitoring, either product can do the job.

What’s different

The pricing model question

Datadog’s pricing is per host, per product. If you want infrastructure monitoring with logs, APM, and security posture, you stack three independent per-host charges. A single Datadog host running Infrastructure Pro + APM + Log Management (annual) is $15 + $31 + log volume costs ¹.

This works fine for cloud workloads where teams pay per usage and the value is high enough to absorb the cost. For bare-metal fleets where you’re monitoring stable hardware that doesn’t generate much application telemetry, the per-host model means you pay for product modules you don’t fundamentally need.

Glassmkr is one product at one price. No tier, no module stacking. You can read the entire pricing equation in one line: $3 × (nodes − 3).

Pricing comparison

Datadog (Infrastructure Pro, annual billing)

Datadog rate: $15/host/month, annual billing, Infrastructure Pro tier, no add-ons ¹.
Glassmkr rate: $3/node/month with 3 free nodes ^G.

Add-on cost considerations

Datadog’s Infrastructure Pro at $15/host includes basic infrastructure monitoring. Adding APM is +$31/host/month (annual) ¹. Adding Log Management is $0.10/GB ingested plus indexing fees at $1.70/million events (annual, 15-day retention) ¹. Custom metrics beyond the 100/host allotment are billed separately ¹.

Glassmkr’s $3/node includes the full product. There are no add-ons because there’s only one product.

When Datadog is the right choice

We’re honest about cases where Datadog fits better:

You need APM, RUM, or log management alongside monitoring.

Glassmkr does monitoring. Datadog is an observability platform. If you have applications generating traces and logs and you want one tool that correlates them with infrastructure metrics, Datadog covers that ground.

Your infrastructure is primarily cloud workloads.

Datadog’s strength is monitoring ephemeral containers, AWS/GCP/Azure services, Kubernetes clusters, and microservices. Their integrations for cloud-native infrastructure are extensive.

You have a security team using Cloud Security Posture Management.

Datadog’s DevSecOps SKUs combine infrastructure monitoring with CSPM, CIEM, and workload protection. If you need these in the same tool, Datadog ships them.

You have a Datadog enterprise contract already in place.

If your organisation already pays for Datadog and has it deployed, the marginal cost of adding bare-metal hosts is just per-host pricing. Glassmkr’s savings show up most clearly when you’d otherwise be paying full per-host pricing from scratch.

When Glassmkr is the right choice

You run bare-metal infrastructure and want predictable pricing.

$3/node/month, no surprises, no add-ons, no tier upgrades. Easy to forecast for finance, easy to justify for procurement.

You want monitoring without becoming a Datadog expert.

Datadog has 30+ product modules and a learning curve. Glassmkr has one product with 60 alert rules that work out of the box.

You care about reading the agent that runs on your servers.

Crucible is MIT licensed; ~150-line installer; runs as non-root user. The Datadog Agent is Apache 2.0 ² (also open source) but the install footprint and operational complexity are different orders of magnitude.

You don’t need APM, log management, RUM, or SIEM.

If your monitoring needs are infrastructure-focused, you’re paying for products you don’t use with Datadog.

You operate in Europe and care about data residency.

Glassmkr is operated by an EU-based team with EU-stored data. Datadog has EU regions but the company is US-based.

Migration: switching from Datadog to Glassmkr

If you’re moving from Datadog to Glassmkr, here’s the conceptual mapping:

Datadog Host → Glassmkr Node. Same unit of accounting. One server is one node.

Datadog Monitors → Glassmkr Alert Rules. Datadog requires you to author monitors. Glassmkr ships 60 rules enabled by default. You’ll likely want to disable some that don’t apply to your fleet (e.g. ZFS rules on Btrfs systems).

Datadog Dashboards → Glassmkr Server Detail Pages. Per-server, with metrics charts, alert state, and remediation guidance on each alert. Custom dashboards aren’t a Glassmkr feature (yet); if you have custom Datadog dashboards you depend on, evaluate whether Glassmkr’s per-server view covers your use case before migrating.

Datadog Integrations → N/A in scope. Glassmkr doesn’t ingest from AWS/GCP/Azure APIs, application traces, or external SaaS. It monitors what its agent observes on the server. If you depend on Datadog’s cloud integrations for half your visibility, Glassmkr doesn’t replace that part.

Datadog Notification Channels → Glassmkr Notification Channels. Telegram, Slack, Discord, PagerDuty, email, webhooks. Migration is reconfiguring routing once.

Operational migration steps

1. Install Crucible on 3 servers (free tier covers this). Verify alerts fire as expected on hardware that Glassmkr already covers.
2. Verify the remediation guidance on each alert matches what your runbooks describe. Tune any thresholds that fire too sensitively for your environment.
3. Confirm notification channels deliver to the right places.
4. Expand fleet-wide. Run both products in parallel for 30 days to compare alert coverage.
5. Decommission Datadog Infrastructure Pro on bare-metal hosts (keep on hosts where you genuinely use it).

Email [email protected] if you want help with the migration. The whole company is a small team; you’ll get a real reply.