Status: DRAFT — product / sales-enablement copy. For human review before external use.
Last reviewed: 2026-07-12
Sources:website/pulse-website-mockup_V10.html(V10 product framing);Docs/TECH-DD-02-Pulse Chronos Architecture and Cybersecurity Overview.pdf; Performance brief (benchmark figures); platform synthesis (wiki/overview.md).
Pulse is an industrial data platform. It ships as two products that share one data backbone — so you can start with the data foundation, the intelligence layer, or both, and grow without re-platforming.
Both run edge / on-prem by default (air-gap capable), and Pulse Copilot can also run as a managed cloud service against an on-prem historian.
| Name | What it is |
|---|---|
| Pulse | The platform / brand — everything below is part of Pulse. |
| Pulse Historian | The historian product: connect → store → monitor → dashboard. |
| Pulse Chronos | The storage engine inside the Historian — the Rust binary TSDB. |
| Pulse Copilot | The AI product: ask questions in plain English, get answers. |
| Clarity AI | The AI engine behind Copilot — a multi-agent system. |
New to the terms in this wiki? See the Glossary. For a technical, code-cited tour, start at the Reading Guide.
The industrial historian for the AI era: one install that captures, stores, monitors, and serves plant time-series data.
Applies to: Pulse Historian · edge/on-prem
An agentic assistant for the plant floor. A shift engineer asks a question in plain English; Copilot retrieves the relevant tags, analyzes them, and answers with the trends and context to back it up — no query language and no specialist required.
Applies to: Pulse Copilot · edge/on-prem or managed cloud
Five layers, from the plant floor up to the person asking the question:
🎞️ [DIAGRAM: styled 5-layer stack] — a designed version lives in System Context (
hld/assets/pulse-stack.svg); the Mermaid above is the regenerable source of truth.
Legacy plant historians (OSI PI, Honeywell, Aspen IP.21, Canary) store data well but stop there — and they are slow and costly to stand up and to grow. Pulse's positioning is a modern install, answers included, and transparent tag-based pricing.
| Legacy historian | Pulse | |
|---|---|---|
| Setup | Multi-month evaluation, multi-week install | Double-click installer; micro-services live in ~10–15 s; first asset onboarded the same day — ~50× faster setup |
| What you get | Storage + trends; you build the rest | Storage plus ready-to-use alarms, anomaly detection, root-cause, EMS, and an AI copilot |
| Query speed | Baseline | ~5× faster data fetch at comparable tag tiers (measured — see methodology) |
| Growth | Edition upgrades / re-platforming to scale | Start at 500 tags or 500,000 — same install, same product; add tags and sites as you grow |
| Pricing | Per-tag + connector + seat + dashboard fees | One tag-based price; Pulse Chronos, EMS, monitoring, the AI engine, and offline licensing included at every tier |
| Deployment | Server-class, often cloud-dependent | Runs at the edge; air-gap capable; active-passive HA failover in ~2–5 s |
| AI | Bolt-on, sold separately | AI-native — the agent engine is built into the platform |
Honest framing. The speed and setup figures above are Pulse's measured/positioning claims, not a certified head-to-head. Vendors' published benchmarks run on different hardware and datasets. Keep the Performance brief methodology note attached to any figure used in a technical proposal. A migration whitepaper is planned but not yet written — do not link to it externally until it exists.
You do not have to rip anything out to get value.
Connect via PI Web API and the other connectors, read your asset hierarchy, onboard tags, and backfill history — consolidating onto one modern platform. Run both systems in parallel during the transition. Start with the PI connector setup guide.
Leave your existing historian in place and point Pulse Copilot at it. Your team gets natural-language answers and diagnoses without a migration project. See Copilot use cases and the Agents architecture.
| edge / on-prem (default, air-gap capable) | managed cloud (optional) | |
|---|---|---|
| Pulse Historian | ✅ Pulse Chronos on the plant server — deployment | managed hosting (planned) |
| Pulse Copilot | ✅ bundled into the historian install — deployment | ✅ Docker/K8s service — cloud deployment |
You decide what leaves the plant network. Pulse is built to run where your data already lives, so adopting Copilot does not change your OT security posture. See the Security Model.
[VERIFY] The precise offline-AI architecture — which model runs where, and which Copilot features are available fully air-gapped — is pending a canonical one-line definition (flagged as an open item in the website mockup). Do not assert offline-AI specifics externally until confirmed.
Reviewer notes before external use: (1) footprint/logo numbers are intentionally omitted — the mockup carries an unreconciled 200+ plants / 300+ sites / 439 customers discrepancy; pick one canonical figure before publishing. (2) "50× setup" and "5× data fetch" need the methodology pointer kept nearby. (3) The migration whitepaper and managed-hosting for Historian are planned, not shipped.