DEPLOYDatabase

Deploy Alerts

What we notify about, and what we never do

Every other alert system notifies you about coverage: someone wrote an article, someone ran a promotion. Deploy notifies you about reality: the verified record changed. This page is the whole rulebook - what we alert about, what we never alert about, and why.

What fires an alert

One thing, and only one thing: a verified state transition on the record. A model's availability changing from “not yet” to “orderable.” A price moving from undisclosed to disclosed. A safety incident recorded from a primary source. A deployment ending. Each of these is a change to the verified record, anchored to primary-source evidence and dated.

What never fires an alert

  • A press release, a tweet, or a spoken estimate. A maker's claim is not a state change - at most it is a line in the claims ledger you can see on the record.
  • An unverified or contradicted claim. If it has not cleared verification, it does not reach your inbox.
  • Anything a manufacturer or merchant paid for. We never send a sponsored alert. There is no paid placement in a Deploy notification, ever. That is the line our neutrality depends on.

How often you hear from us

Alerts are tiered by how much they matter:

  • Real-time - the things you want the instant they happen: safety incidents, availability changes, price disclosures, deployment endings.
  • Digest - gathered into a periodic summary: new deployments, new claims logged, status reviews, ranking movements.
  • Ambient - the monthly view: index movements and the state of the field.

You start on digest with real-time only for the critical things, and you can promote any single field to real-time - or mute it - without leaving the platform. Mute one field, one entity, or one tier; you are never forced to unsubscribe from everything to escape one alert.

Every alert is on the record

When we alert you, we log it: what fired, when, and which verified change triggered it. The notification itself is auditable. And every alert carries the same one line the whole platform runs on - we tell you when verified state changes, not when someone issues a claim.