Weather alerts
Hyperlocal weather alerts for vineyards — frost, freeze, NWS advisories.
Vinifera pulls the National Weather Service forecast for every vineyard on a 30-minute cron, runs your threshold rules against it, and ingests the official NWS advisories — Frost Advisory, Severe Thunderstorm Warning, Hail, Flood, Tornado — that the forecast model alone can't cover. Up to 48 hours of lead time on a freeze warning, deduped so you don't get the same alert twice from two systems.
Two alert engines, one feed
Forecast rules + advisory ingestion.
Generic weather apps show the forecast and stop there. Vinifera evaluates the forecast against your rules and ingests the official advisories the NWS issues for your county — the kind of alert that triggers fan-up decisions, harvest reschedules, and crew calls.
-
Threshold rule editor
Build rules across five categories — frost, freeze, heat, wind, and rain — with operator and threshold per rule. "Min temp ≤ 32°F in next 24h" fires a frost rule; "Wind gust ≥ 25 mph during a planned spray" fires a wind rule. Each rule has its own active window and severity.
-
NWS advisory ingestion
Some kinds — Severe Thunderstorm Warning, Hail, Flood, Tornado — are advisory-only because the model can't predict them, only the NWS office can. Vinifera ingests the official feed for your county and pushes the advisory the moment it's issued. No threshold rule needed.
-
48-hour lead time on freezes
The freeze rule reads up to 48 hours of forecast and fires as soon as the trough drops below your threshold. That's enough lead time to call the wind machine company, schedule helicopter coverage, or move a crew off the morning prune.
-
Dedupe across sources
If your "min temp ≤ 36°F" rule fires and the NWS issues a Frost Advisory for the same window, you get one alert, not two. The dedupe key is (vineyard, kind, window) — same kind in the same window collapses.
-
In-app feed + push
Every alert lands in the in-app alerts feed with severity, source, and the forecast snapshot that triggered it. Push notifications are on by default for Pro and Business; the in-app feed is free.
-
Frost & freeze push — Business tier
The frost / freeze push notification is gated to Business because it's the alert most likely to require a 4 a.m. response. Pro sees the in-app feed and email; Business gets the wake-up push. See the entitlement matrix for the full split.
Free already gets the in-app feed.
Every plan, including Free, sees the threshold-rule alerts and the NWS advisory feed in-app. Pro adds OpenWeather as a second forecast source and email notifications. Business adds the frost / freeze push and weather-station integrations (Davis, RainWise). Pair with scouting to track the canopy damage after a freeze event, or with spray records for the wind-at-apply check the WPS already requires.
FAQ — weather alerts
What growers usually ask.
How often does the alert cron run?
Every 30 minutes. The job pulls the latest NWS gridpoint forecast for each vineyard's lat/lon, evaluates every active threshold rule, and ingests any new advisory items from the county feed. 30 minutes is the floor — pulling more often would burn against the NWS rate limit without giving you meaningfully fresher data.
Why are some alert kinds "advisory-only"?
Severe Thunderstorm, Hail, Flood, and Tornado are short-fuse atmospheric events the forecast model doesn't predict on a granular schedule — only a human meteorologist at the NWS office issues them. So we ingest the advisory directly instead of pretending a rule could catch it. Frost, freeze, heat, wind, and rain are forecastable, so they have rule editors.
Why is frost / freeze push gated to Business?
Frost / freeze push is the only alert that's likely to wake you up at 4 a.m. We treat that as a higher-stakes contract than the rest of the alert system, and we only want to deliver it to operations that have committed to the Business tier. Pro still sees the alert in-app and gets the email.
What if my weather station is offline?
Threshold rules evaluate against the NWS forecast first, not the station. If your Davis or RainWise station goes offline, the rule keeps firing on forecast data. Station outages produce a separate "data source offline" alert so you know to check the unit, but they don't suppress weather-rule alerts. See inventory for the comparable "lot history doesn't get destroyed by an offline event" pattern — same design philosophy.
Can I silence an alert kind I don't care about?
Yes. Each rule has an enable / disable toggle. Advisory ingestion is per-kind too — turn off Severe Thunderstorm Warning if you don't operate during storms, leave Tornado on. The dedupe key respects whatever you've enabled.