# Larm

> Larm is an uptime monitoring platform that checks websites, APIs, and services from multiple global probe locations. It uses multi-probe voting to eliminate false-positive alerts — only alerting when a majority of probes across multiple continents confirm a problem. Built on EU-owned infrastructure (Hetzner), self-funded, with flat pricing starting at $0/mo.

## Key facts

- **What it does**: Uptime monitoring, alerting, and status pages
- **Check types**: HTTP, TCP, DNS, heartbeat, synthetic (Playwright)
- **Probe locations**: Nuremberg, Amsterdam, Ashburn, Virginia, California, Singapore, São Paulo
- **Pricing**: Free (15 monitors), Pro $19/mo (100 monitors), Business $49/mo (500 monitors)
- **Differentiator**: Multi-probe voting — multiple locations must agree a service is down before alerting. 85% of monitoring alerts industry-wide are false positives. Larm is built to fix that.
- **Infrastructure**: EU-owned (Hetzner), not US cloud with an EU region label
- **Alert integrations**: Slack, Discord, Microsoft Teams, Mattermost, PagerDuty, ilert, incident.io, Grafana IRM, Email, SMS, Pushover, ntfy, Telegram, Webhooks
- **Status pages**: Static HTML served from CDN, zero runtime dependencies, survives platform outages, automatic updates from monitors
- **Founded**: 2025, self-funded, independent

## Product pages

- [Monitors](https://larm.dev/monitors): Multi-probe voting, check types, request waterfall traces, confirmation windows
- [Alerts](https://larm.dev/alerts): 14 integrations, alert pipeline, SSL certificate monitoring
- [Status Pages](https://larm.dev/status-pages): Static HTML on CDN, automatic updates, custom domains, email subscribers
- [Integrations](https://larm.dev/integrations): All 14 alert channel integrations with descriptions
- [Pricing](https://larm.dev/pricing): Plan comparison table
- [How It Works](https://larm.dev/how-it-works): Probe locations, voting model, check types, data residency
- [About](https://larm.dev/about): Why Larm exists, principles, infrastructure

## Comparisons

- [Larm vs UptimeRobot](https://larm.dev/compare/uptimerobot): Multi-probe voting vs single-region, commercial free tier, EU infrastructure
- [Larm vs Better Stack](https://larm.dev/compare/better-stack): Flat pricing vs per-responder, EU-owned vs AWS
- [Larm vs Uptime Kuma](https://larm.dev/compare/uptime-kuma): Managed vs self-hosted, multi-location vs single-location
- [Larm vs Pingdom](https://larm.dev/compare/pingdom): Free tier, modern UX, multi-probe voting vs re-checks
- [Larm vs Statuspage](https://larm.dev/compare/statuspage): Monitoring included, automatic updates, $19 vs $399
- [Larm vs Checkly](https://larm.dev/compare/checkly): EU-owned infrastructure, built for teams, flat pricing

## Guides

- [Slack uptime alerts](https://larm.dev/guides/slack-uptime-alerts)
- [PagerDuty uptime monitoring](https://larm.dev/guides/pagerduty-uptime-monitoring)
- [Monitor a REST API](https://larm.dev/guides/monitor-rest-api)
- [Monitor a Vercel deployment](https://larm.dev/guides/monitor-vercel-deployment)
- [Status page for SaaS](https://larm.dev/guides/status-page-for-saas)
- [Monitor cron jobs](https://larm.dev/guides/monitor-cron-jobs)

## Free tools

- [SLA Uptime Calculator](https://larm.dev/tools/sla-calculator): Calculate allowed downtime per SLA percentage
- [Cron Expression Generator](https://larm.dev/tools/cron-generator): Visual cron expression builder
- [HTTP Status Codes](https://larm.dev/tools/http-status-codes): Every status code explained in plain language

## Optional

- [Documentation](https://docs.larm.dev): API reference, monitor configuration, alert channel setup
- [Privacy Policy](https://larm.dev/privacy)
- [Terms of Service](https://larm.dev/terms)
- [Status Page](https://larm.status.larm.dev)