The Prophesee™ Platform

Four engines.
One decision layer.

Enterprises have digitised their workflows and their reporting, but not their decisions. Prophesee closes that gap: it predicts what is coming, flags what needs you, tracks every plan, and remembers everything your business learns. Governed by construction. Proven daily.

The estate

Four engines become hundreds of applications

One structure carries every capability: engines power suites, suites carry modules, modules ship applications. Build the intelligence once and it flows the whole way down.

Built once. Proved once. Governed once.

Foresight's predictions feed Horizon, Pulse and Nexus. Pulse and Horizon share one event backbone. Nothing is modelled twice.

CHANGE LANDSKPI RECOMPUTESRULE EVALUATESALERT FIRESPLAN ODDS MOVEAUDIT RECORDS3 need youP 48% → P 71%

One event backbone. The exception that interrupts someone this morning is the same event that moves the year's odds, and the audit records it all.

Foundations

Engineered for the real world

Your data stays yours

AI runs where your data lives, including fully on-premises with no external APIs. Search and inference inside your own boundary.

Offline & edge

Models that keep working where the network doesn't reach: local inference, syncing when reconnected, conflict resolution built in.

Time-travel data

Point-in-time history of every record. Analyse how the data evolved, recover any prior state, detect drift.

APIs & streams

Predictions, alerts and events consumable over APIs, streams and webhooks, into your own applications without point-to-point integration.

Trust & governance

Governed by construction

An engine that watches everything needs controls stronger than the process it replaces. Governance isn't a policy document here. It's how the platform is built.

Model passports

Every model on record: training data, features, version, owner, backtest, calibration curve and approval. Governance without notebooks.

Versioned and reversible

Every rule and calculation carries its full history. Kill-switches per rule, metric and channel. Instant, platform-wide.

Append-only audit

Every prediction, alert, plan change and approval on the permanent record: who, what, when, and what the model claimed at the time.

One number per viewer

Visibility enforced at the data layer from the caller's identity. Predictions, alerts and plans scoped to each viewer's permissions.

Fail-loud validation

Invalid configuration refused at definition time: circular metrics rejected, typos caught as you type, gates that cannot be skipped.

Proven daily

Champions re-scored every day against live data. A model left alone is quietly wrong. These are never left alone.

Full detail on PBAC, audit and our security practices on the Security page.

Questions enterprises ask

See the four engines on your data

An eight-week value evaluation. Not a pilot, not a demo.