From severe-weather intelligence to prioritized, auditable action.
StormTrust turns forecast, radar, observed, property, operational, and campaign intelligence into an auditable answer to seven questions:
- Where is severe weather likely?
- What does radar indicate is happening?
- What was actually observed or reported?
- What geographic area was probably impacted?
- Which properties were probably exposed to damaging hail?
- Where should people deploy, and who may be contacted?
- What action was taken, and what happened afterward?
The complete product lifecycle is:
Weather
↓
Evidence
↓
Storm
↓
Property
↓
Decision
↓
Action
↓
Evidence
↓
Outcome
↓
AttributionThe product model requires each transition to remain understandable, attributable, and reproducible.
| Intent | Start here |
|---|---|
| Learn by doing | Read an evidence record |
| Complete a task | Review a product change |
| Look up facts | Datasets and source contracts |
| Understand the model | Product principles |
| Run the software | Local application stack |
Foundations
Learn the evidence model and understand the product principles and architecture.
Operations and growth
Turn intelligence into field work, opportunities, campaigns, reports, and public content.
Platform and data
Explore Forecast, Alert, Radar, Map, Impact, Report, History, and Replay with their shared data and release contracts.
Build and operate
Review product changes, testing requirements, and current versus planned API contracts.
Strategy and reference
Use the catalogs, competitive requirements, release plan, changelog, and source references.
Each subject hub links to its tutorials, task guides, reference, and explanations. Read Applications for implementation boundaries and Operations for executable procedures. The release roadmap records requirements rather than deployment status.
StormTrust succeeds when it preserves a defensible chain from uncertain atmospheric signals to measurable outcomes. The chain, not the map alone, defines the product.