Skip to main content

Fully Managed
Prometheus Alertmanager
as a Service

Deploy Prometheus Alertmanager as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Prometheus Alertmanager handles routing, grouping, silencing, and inhibition for alerts emitted by Prometheus servers. DANIAN runs it across 21 datacenter locations, with a clustered gossip mesh, persistent silence storage, and a pre-wired SMTP relay. A restart never drops an active maintenance window or pages the on-call rotation by mistake.

Teams that ran Opsgenie are moving in 2026. Atlassian announced on March 3, 2025 that Opsgenie ends sale on June 4, 2025 and ends support on April 5, 2027. PagerDuty Business sits at $41 per user per month. Self-hosted Alertmanager is free software under Apache 2.0, but the gossip cluster, receiver tokens, and SMTP relay need real operators.

Free 7-day trial  99.9% Uptime SLA  No credit card  Cancel anytime

Free 7-day trial  99.9% Uptime SLA
No credit card  Cancel anytime

Prometheus Alertmanager

Prometheus Alertmanager

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Prometheus Alertmanager Preview Image

ABOUT THE SOFTWARE

What is Prometheus Alertmanager

Alertmanager is the alerting component of the Prometheus monitoring stack. It deduplicates, groups, and routes alerts to receivers such as Slack, PagerDuty, email, Microsoft Teams, Telegram, OpsGenie, and any webhook. It runs as a stateful Go service in clustered mode using a gossip protocol.

License is Apache 2.0. The project is maintained by the Prometheus Authors as part of the CNCF graduated Prometheus project, originally built at SoundCloud in 2012. The current stable release is v0.30.0, released on December 15, 2025, following v0.29.0 on November 1, 2025 and v0.28.1 on March 7, 2025. Notable production users include DigitalOcean, GitLab, Cloudflare, Shopify, and CERN.

The Alertmanager binary tar.gz is about 33 MiB. It listens on TCP 9093 for the HTTP API and the web UI, and on TCP and UDP 9094 for cluster gossip between replicas. The data directory stores two files: a silences snapshot and a notification log (nflog). High-availability mode uses HashiCorp's memberlist library, so each Prometheus instance sends the same alert to every Alertmanager replica and the cluster deduplicates notifications.

FEATURES

What Prometheus Alertmanager does

Alertmanager is a single-purpose Go service. It takes a stream of alerts from one or more Prometheus servers, decides who should be notified, when, and in what grouping, and dispatches to receivers. Eight features make up the surface area.

Routing tree

A tree of match rules with continue, group_by, and per-route timing. Alerts traverse from the root and stop at the first matching leaf, or continue if explicitly requested.

Inhibition

A firing alert can mute other alerts that share given labels. The classic example mutes warning-severity alerts when a critical alert is already firing for the same alertname.

High availability via gossip

Multiple replicas join over TCP and UDP 9094 using HashiCorp's memberlist library. Each replica receives every alert. Notifications deduplicate via the nflog.

Templating

Go templates over each alert's labels and annotations. Customize Slack message format, PagerDuty incident title, or webhook JSON body without touching code.

Grouping

Alerts with shared labels collapse into one notification via group_wait, group_interval, and repeat_interval. A cluster outage becomes one page, not three hundred.

Silences

A web-UI rule that mutes matching alerts for a fixed window. Stored on disk as a snapshot file, gossiped across the cluster with last-write-wins.

Receiver integrations

Native config for Slack, PagerDuty, email, MS Teams, Telegram, OpsGenie, Discord, Pushover, VictorOps, SNS, Webex, Mattermost, Rocket.Chat, Jira, incident.io, and generic webhook.

Time-based muting

mute_time_intervals and time_intervals let routes mute outside business hours, or only fire during weekends. Useful for non-paging warnings.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app you deploy includes the full managed service — security, backups, updates, and support from day one.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers on chat. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed Prometheus Alertmanager

The trigger is the contraction in incident tooling. Atlassian ends Opsgenie sales on June 4, 2025 and ends support on April 5, 2027. Grafana put OnCall OSS into maintenance mode on March 11, 2025. PagerDuty Business is $41 per user per month. Teams want their alerting back on commodity open source.

Running Alertmanager looks easy in a docker run command. Production is different. A real deployment needs three replicas in a gossip cluster, persistent volumes for silences and nflog, an SMTP relay for email receivers, receiver-token rotation for Slack and PagerDuty, runbook URL templating, and a load balancer that does not balance Alertmanager traffic the way it balances HTTP. Prometheus must send the same alert to every replica, never round-robin. None of that ships in the Helm chart.

The most common production failure is silences disappearing on restart. The --storage.path flag points to a directory holding the silences snapshot and the nflog. If that path lives on ephemeral container storage and the pod restarts, every active silence is gone. The on-call team gets paged at 3 a.m. for the maintenance window they thought they had muted. The prometheus/alertmanager GitHub tracker has reported this since issue #1673 in 2018, with related complaints in issue #2370 and a long thread on the prometheus-users mailing list.

DANIAN runs three Alertmanager replicas per tenant in a gossip cluster, with a persistent volume mounted at /alertmanager and a daily off-site snapshot of the silences and nflog files. The SMTP relay is pre-wired and DKIM-signed. Receiver tokens for Slack and PagerDuty are stored in the DANIAN secret store with rotation reminders. The webhook receiver retries are capped to prevent backoff loops.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run Prometheus Alertmanager on DANIAN

These are representative team types we set up most often. Each starts with the same flat €9 plan.

SRE TEAM · B2B SAAS

Frankfurt, Virginia, Singapore

A twelve-person SRE team running a B2B SaaS platform across three Kubernetes clusters. They maintain 200 alert rules covering API latency, database replication lag, and queue depth. The routing tree splits by severity: critical pages PagerDuty, warning posts to Slack #alerts, info goes to email. Two-hour repeat_interval on critical routes.

PLATFORM ENGINEERING · FINTECH

Dublin

A six-person platform team at a payments company. They route payment-pipeline alerts to a five-person on-call rotation. Inhibition rules suppress per-merchant alerts when the upstream gateway alert fires. Webhook receivers push events into the case-management system for the PCI-DSS audit log. Silences are tied to deploy windows.

INFRA · VIDEO STREAMING

Singapore + Tokyo

A four-person infrastructure team running live video for a regional streaming app. Only paid-tier customer impact pages the on-call; free-tier degradation goes to a daytime Slack channel. Time-based muting prevents weekend pages for non-revenue services. Routing is by customer_tier label populated in Prometheus rules.

COMPARISON

Four ways to run Prometheus Alertmanager

The same software runs in four shapes: a SaaS competitor that does the same job differently, a single VPS, a homelab box, or a managed platform like DANIAN. The cost math at one user, five users, and ten users diverges fast because PagerDuty bills per seat and DANIAN bills per app.

 PATHCOST (1 USER)COST (5 USERS)COST (10 USERS)OPS TIME NOTES
PagerDuty
Business tier
$41/mo$205/mo$410/mo0 hours
Per-seat, annual billing. AIOps and Status Pages are paid add-ons. List prices from pagerduty.com/pricing (Professional $21, Business $41).
Self-host on a VPS
$24/mo production-class
$24/mo + ops$24/mo + ops$24/mo + ops5–10 hrs/moYou install Alertmanager, configure the three-replica gossip cluster, set up persistent volumes, configure SMTP, rotate receiver tokens, and monitor the monitor.
Home server
e.g. Synology DS923+
~€700 + €15/mo~€700 + €15/mo~€700 + €15/mo2–4 hrs/moNot suitable for production alerting. Home internet uptime is the limiting factor. When the residential link drops, the alert pipeline drops with it.
DANIAN Managed Prometheus Alertmanager€9/mo flat€9/mo flat€9/mo flat0 hoursPer-app, not per-seat. Three-replica HA cluster. Persistent /alertmanager volume with daily off-site backup. Pre-wired SMTP. 99.9% uptime SLA.

At one user, PagerDuty Business is roughly four times the DANIAN price. At ten users, it is forty-five times. PagerDuty pricing scales with the on-call rotation; Alertmanager does not care how many humans are on the receiving end, and neither does DANIAN. Self-hosting on a single VPS works for a homelab; for a real production pipeline it leaves the cluster, the SMTP relay, and the secret rotation as the operator's homework. Home servers fail the basic test of an alerting system: they cannot alert when the house internet drops.

BY INDUSTRY

Prometheus Alertmanager for specific industries

Alerting requirements differ sharply by industry. A payments processor needs an audit trail of every ack. A streaming game studio needs sub-minute notification latency. A connected-device platform needs high-cardinality routing. DANIAN configures Alertmanager for the realistic shape of each. Compliance certifications are the customer's to obtain.

PCI-DSS Requirement 10 (audit trails for all access to cardholder data systems) requires that every alert acknowledgement, route, and resolution is timestamped and retained. DANIAN configures the Alertmanager webhook receiver to also POST to your case-management system, producing a parallel audit trail for the assessor. The gossip cluster runs across two DANIAN regions for survival of a single-region outage, matching the 99.99% uptime SLA most fintech customers contractually owe their counterparties. Routing trees split by payment-rail (cards, SEPA, ACH) so the right on-call rotation responds. Sub-minute alert-to-page latency is preserved by keeping group_wait at 15 seconds on the critical route. The customer remains responsible for PCI-DSS attestation; DANIAN provides the infrastructure configurations that support the technical requirements.
SLA contracts with named customers often carry meantime-to-acknowledge clauses (frequently 15 minutes) and meantime-to-restore clauses (often 4 hours). DANIAN's persistent silences ensure that planned-maintenance windows declared before a release are not lost in a pod restart — a common cause of accidental SLA breaches. Routing rules direct enterprise-tier customer alerts to a dedicated receiver with shorter group_wait. The /-/reload endpoint is authenticated and rate-limited so a misclick does not blank out the routing tree at the wrong moment. Engineering-support response time on DANIAN is part of the alerting chain itself — if the platform misbehaves, you reach an engineer, not a tier-one queue. Daily off-site backup of alertmanager.yml lets you roll back a bad change.
Peak-season traffic during Black Friday and Cyber Week runs roughly 2x a normal day per Queue-it's 2024 Black Friday Statistics report, and alert volume often scales with it. DANIAN sizes the Alertmanager cluster ahead of seasonal events and pre-tests the gossip mesh under load. Routing by customer_tier label sends platinum-account incidents to a dedicated PagerDuty service while consumer-tier issues route to a Slack channel. Inhibition rules suppress per-product-page alerts when an upstream CDN alert fires, so a CDN event does not page the catalog team four hundred times. mute_time_intervals turn off non-revenue alerts during peak hours so the on-call focuses on checkout, payments, and fulfillment. Configurable webhook retry caps prevent retry-storms against a backend already under load.
High-cardinality alert sources are the norm — a fleet of 10,000+ devices each capable of firing alerts with device_id and firmware_version labels. DANIAN tunes group_by to ['alertname', 'firmware_version', 'region'] so a firmware-rollout bug becomes one alert per affected version, not ten thousand. The --alerts.per-alertname-limit flag is set so a runaway device fleet cannot exhaust memory. Webhook receivers push into a fleet-management API for automatic device quarantine on critical alerts. Silences are scoped by firmware_version so a known issue in v1.2.3 does not silence v1.2.4 devices. Time-based muting prevents pages during scheduled firmware deployment windows. The cluster is sized so the Alertmanager API handles bursty alert volume during fleet-wide events without dropping.
HIPAA breach-notification rules require notification within 60 days of discovery. DANIAN configures dedicated routing for security and PHI-access alerts to a HIPAA-trained on-call rotation, with the webhook receiver writing to your case-management system to start the breach-notification clock immediately on ack. Escalation chains are templated so a missed acknowledgement promotes to a secondary on-call within five minutes. mute_time_intervals are not applied to security alerts under any circumstance. Daily backup of the alert ruleset and silences supports the audit trail. DANIAN does not claim HIPAA compliance itself; the platform supplies the technical configurations a covered entity needs to meet the HIPAA Security Rule's incident-response controls under §164.308(a)(6).

FAQ

Frequently asked questions

Everything teams ask before signing up — answered straight, without sales speak.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

TEXT
TEXT
TEXT
TEXT
TEXT
TEXT
TEXT
TEXT
TEXT
TEXT

02

Migration and onboarding

We can activate your app on your own custom domain/subdomain. Examples: mydomain.com, anyword.mydomain.com.
Or, on our randomized free subdomain. Example: 963.apps.danian.cloud
If you wish to use a custom domain/subdomain, select that option when ordering your app (or notify us later). We will send you the required DNS records and if needed, our tech team will modify them for you.
21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
TEXT
TEXT
TEXT
TEXT
TEXT

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on Email/LiveChat. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 Live chat and email support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed Prometheus Alertmanager for 7 days

No card. Cancel from the dashboard.