Why per node
A node is a connected thing the operating system reasons about: a truck, a sensor source, a connected system endpoint. Pricing per node ties cost to the actual surface area the Engine is governing, not to a vague seat count.
As a site grows, the per-node rate scales sensibly, so standing the operating system up across more of the site does not punish you for expanding. The bigger the surface area, the better the per-node economics.
Why we quote on a pilot
There is no list price, because the honest number depends on your site: how many nodes, which systems you connect, and how you want it hosted. Anything we published as a flat figure would be wrong for most sites.
So we quote on a pilot. We scope your node count and connected systems, run the Engine against real data, and give you a number that actually matches your operation.
What sits outside the per-node price
The client runs their own OpenShift or infrastructure. That keeps the per-node price clean and lets you host wherever you need: cloud, local cloud, or on-prem in an OpenShift container.
The per-node price covers the operating system itself: the Engine pipeline and the Platform layer your teams log into. Book a pilot and we will scope the full picture for your site.