Earthquake alert system for business

If your organisation operates in more than one place, earthquakes are an operational problem, not just a news event. When the ground shakes somewhere you have a facility, the questions come fast: which site was affected, how hard was it shaken, who is on call for that region, and what do we tell insurers and leadership. Tremor is built to answer those questions automatically, within about a minute of the U.S. Geological Survey publishing an event.

The problem it solves

Distributed operations make earthquake response hard in three ways. Sites are spread across different seismic settings, so a single threshold does not fit them all. On-call routing is manual, so someone has to notice the quake and work out which team owns the affected location. And after an event, documenting what happened, for insurance, for leadership, for continuity records, usually means reconstructing it from memory and news reports. Tremor addresses each of these.

What Tremor Business does

You define watchlists, which are saved locations, each with a radius, a minimum magnitude, and an optional minimum shaking intensity, and Tremor monitors them around the clock from the cloud. When an earthquake matches, it notifies your chosen channels: email, push, Slack, Discord, generic webhooks, and, on the Business plan, PagerDuty incidents with severity mapped from magnitude and shaking intensity and deduplicated so one event is one incident.

For multi-site operators, Tremor Business adds portfolio monitoring: upload a spreadsheet of every site you run and Tremor watches all of them at once, ranking them by exposure and by recent shaking. It keeps an impact history, a durable record of which sites were shaken by which events and how strongly, so you have a system of record rather than a scramble after the fact. For screening, it can attach a modelled dollar-loss range to an impact, based on the shaking intensity, the building value, and its construction type.

About the loss figures

Tremor's dollar figures are screening-level estimates, always presented as a range rather than a single number. They use a published damage-ratio model, the HAZUS methodology, to give a fast, order-of-magnitude sense of which sites merit a closer look after an event. They are a triage tool, not an engineering study. Tremor complements, and does not replace, a licensed engineer's seismic assessment or a probable-maximum-loss analysis, and it should not be used in their place.

Getting started

• Add your sites. Enter locations individually or upload a spreadsheet of every site, optionally with each building's value and construction type.
• Connect your channels. Route alerts to email, Slack, Discord, webhooks, or PagerDuty, per watchlist, so the right team is notified.
• Let it run. Tremor monitors around the clock and records every qualifying impact, so alerting and documentation happen without anyone watching a feed.

Honest scope

Tremor reports earthquakes after they occur. It is a monitoring, notification, and documentation service, not a prediction system and not an advance-notice service, and it cannot notify anyone before shaking begins. Its loss numbers are screening ranges to guide attention, not certified risk figures. Within those limits, it replaces manual quake-watching and after-the-fact reconstruction with an automatic, documented workflow. Tremor Business is $49 a month; the underlying alerting is available on Pro at $4.99 a month.