Type: explanation · Last reviewed: 2026-07-16
Pulse is the platform. It has two products:
Both run edge / on-prem (air-gap capable) or as a managed cloud service.
This wiki has two layers — read the one that fits what you need:
concepts/ and guides/ pages, product) — plain-language "why / what / how-to", organized by what you're trying to do; the full page list is in the master index.New here? Read the Overview first (~10 min), or jump straight into Your first 15 minutes with Pulse Historian to write and read your first data point. Then follow your path below.
Pages that are product- or deployment-specific are tagged > Applies to: <product> · <deployment>.
| edge / on-prem (default, air-gap capable) | managed cloud (optional) | |
|---|---|---|
| Pulse Historian | Pulse Chronos on the plant server — deployment | managed hosting (planned) |
| Pulse Copilot | air-gapped / bundled with the Historian — deployment + Agents | cloud deployment + Agents |
The deployment pages are currently named for the old modes (
historian/standalone/cloud-copilot); they'll be renamed during the reader-layer rollout. Content is correct.
/docs)All examples in this wiki use one running dataset — the
acme-power / plant-1 / boiler-2 / default_gridcollection with tagssteam_pressure,steam_temp,feedwater_flow,idfan_vibration. See Data model & scope.