Pricing
Per site. Not per device, not per camera.
Adding a sensor should make Powoflow more useful, not more expensive. Here is how the model works and what actually scales, and why there is no price list on this page yet.
Why per-site
The unit you pick decides the behaviour you get.
Density is the point
Per-device and per-camera pricing punishes the exact thing that makes Powoflow work. More sensors on a site means better data, better alarms and a better reason to keep paying. Charging for each one sets us against you.
A site is a place you operate
A plant, a vessel, a solar farm, a building, a depot. It is the unit your own budget is usually organised around, which makes the bill easy to explain internally and easy to forecast.
No multi-year lock-in
Monthly or annual, with a discount for annual. Three-year commitments are the single most common complaint about this category and we would rather earn the renewal.
What scales with a tier
Four dimensions. Everything else is the same product at every level.
Edge devices per site
Field Agents and sensor nodes reporting into one site.
Seats per site
People with a login. Field users and office users count the same.
History retention
How far back telemetry and audit records stay queryable.
AI actions per month
Assistant calls, drafting, extraction, anything that runs a model.
Limits are hard caps with a warning well before you reach one. There is no surprise overage bill, and nothing in the billing system is allowed to interrupt a safety-relevant path. A quota problem stops you creating new records, never finishing work already under way.
Modules
| Assets & hierarchy | Always included. There is no version of this product without the graph. | |
| Alarms & telemetry | Always included. | |
| Work orders | Optional module. | |
| Projects | Optional module. | |
| Inventory | Optional module. | |
| Data Explorer | Optional module. |
Turning a module off is a commercial change, not an operational one. Existing records stay readable and work in progress can still be completed, what stops is creating new objects in that module. See multi-tenancy and entitlements for how that is enforced.
Why there is no price list here yet
Powoflow is pre-launch. There is no self-service signup, every tenant so far has been set up by hand, and the price we would publish today is not the one we would still be charging in six months. Putting a number on this page would make it look more settled than it is.
What we will do is quote you properly against the sites, devices and modules you actually need, and be clear about what is included at that price and what is not built yet. Early customers get terms that reflect the stage, and we will say so rather than pretending it is a discount.
Tell us how many sites
Sites, roughly how many devices per site, and which modules matter. That is enough for a real number rather than a range.