A note from the founder

Most monitoring is noise.

Larm is a one-person uptime monitoring product. This page is the whole story: why it exists, what I believe about monitoring, and how the platform is run.

Who builds Larm

Hello, my name is Johanna.

I've been a software engineer for many years now. Many of those years I was also on call. I know how hard it is to keep a system running smoothly, and to feel confident that it's not about to go down.

I've seen tons of false positives from uptime monitoring tools. Enough that you start ignoring the alerts, because they're just as likely to indicate a problem with the tool itself as with your service. Not to mention deployments that cause a wave of false positives. It's exhausting, and it leads to alert blindness.

You'd think someone would have fixed this by now, that we'd have an affordable and reliable tool to use. It's not for a lack of trying. There are a lot of services out there. But the attempts are half-hearted and usually end up as either a tool that's less reliable than the services it monitors, or a startup that raises a Series A and then very quietly adjusts what "starter" means in the next pricing revision. Neither of those is much help when you're the one on call.

So I'm taking the slower route. Larm is independent and self-funded, run by one person. There's no growth team, no expansion sales, no plan to flip the company. The pricing is honest because there's nobody around to hide it from.

If you write to johanna@larm.dev, I'll read it. And I'll write back.

Johanna

Founder · Larm · built in the UK

Why Larm exists

Most uptime monitoring tools check your site from one or two locations and alert on the first failure. The result is alert fatigue. Your team learns to ignore pages because most of them are false positives. When a real outage happens, it gets lost in the noise.

The tools that solve this problem are enterprise-priced. The tools that are affordable don't solve it. We wanted both: reliable monitoring with alerts you can trust, at a price that makes sense for small and mid-sized teams.

So we built Larm. Probe locations across multiple continents, majority-of-probes voting, confirmation windows, full request waterfall traces, status pages included, and a generous free tier with no commercial use restrictions. The whole platform runs on EU-owned infrastructure.

What we believe

INDEPENDENCE

Self-funded, no investors

No board to impress, no growth targets to hit, no pressure to ship features that serve fundraising narratives instead of users. We grow by being useful.

SOVEREIGNTY

EU-owned infrastructure

Your monitoring data lives on EU-owned infrastructure under EU jurisdiction. Not US infrastructure with an EU region label. Hetzner, not AWS. This matters for GDPR, DORA, and NIS2. And even if compliance isn't your thing, it's nice to know where your data lives.

HONESTY

Alerts you can trust

85% of monitoring alerts are false positives industry-wide. We built Larm specifically to fix that. Multi-probe majority voting, confirmation windows, and deep request traces mean that when Larm sounds the alarm, it's real.

SIMPLICITY

Do one thing well

Larm is uptime monitoring, status pages, and alerting. Not incident management, not log aggregation, not APM. We integrate with the tools that do those things well instead of building worse versions of them.

Infrastructure

Larm checks your services from multiple locations across several continents. When a majority of probes confirm the same problem, we know it's real. A network issue affecting one location doesn't become your team's problem.

Nuremberg, GermanyHetzner
Helsinki, FinlandHetzner
Amsterdam, NetherlandsRailway
Virginia, USRailway
California, USRailway
Singapore, SingaporeRailway
São Paulo, BrazilFly.io

The platform itself runs on EU-owned infrastructure. Your monitoring data is stored and processed within the EU.

Start monitoring in minutes.

Free plan. Commercial use allowed. No credit card.

Sign Up Free