A price we will sign, not a number we invented
There is no published price list, because there is no single number. A pilot is quoted per site, in writing, after a scoping call — and the quote names exactly what it includes. What we can publish is the shape: the modules, what each includes, and what is deliberately not promised.
What a pilot costs
Per site, quoted in writing. The figure depends on what is already installed — a site with readable meters and a gateway is a different job from one that needs hardware — so a published number would either overcharge the easy site or mislead the hard one. Scoping, the quote and the pilot length are described step by step on How we engage.
A pilot runs on your own readings: devices appear in a holding queue with their receipts, you classify each metric in your own portal, and nothing is derived until you have. That is what the quote buys.
What a tenant can run
This is the platform's real module list — the same set the platform administrator assigns per tenant at creation. Modules are not tiers and there is no upgrade screen: what you engaged is what you see, and adding one is a change to the engagement, agreed in writing.
Your meters, inverters, PLCs and gateways read over MQTT/TLS or an HTTP fetch. Every reading carries its source timestamp, is deduplicated on message id, and lands in a holding queue until a person on your side classifies it. Nothing is derived from an unclassified reading, and every figure carries its coverage.
Alarm rules with named owners, recorded dispositions and watchdog findings — including findings about the alarm system itself. Notifications are opt-in everywhere; the default is silence, enforced at dispatch.
A shadow bill recomputed against your declared tariff so you can check the utility invoice line by line, diesel spend measured from generator output and a burn curve, and fuel-tank calibration from measured drawdowns. Where no point of delivery is declared, the platform reports kWh with a null cost and the reason — never an estimate.
External data connections configured per tenant — MQTT bridges, HTTP fetches and webhooks — each with its own credential so its activity is separately accountable.
The asset spine: one identity per physical asset, with aliases and metric bindings. A device string is never an identity, and statement-facing ids are immutable — superseded via alias, never edited.
Alarm and event streams from process plant, treated as event-driven series: silence is a stable session, not a hole, and event streams are never judged by cadence rules.
Controlled documents, drawings and compliance records held against your sites and assets, with revision history retained rather than overwritten.
Project tracking, a support channel with a record, and maintenance registers against the same asset spine the telemetry binds to.
The M&V module, with its status on the face
- Whole-facility (Option C) baseline under CYN-NEX-MV-01 Rev A — the only option the method permits.
- Day and month admission: admitted or refused with a named reason from the method's closed refusal vocabulary — never prorated, never gap-filled.
- A non-routine event register: an open event refuses issuance of any saving statement until it is closed or dismissed by a person, with evidence.
- Metering class declared per series; a null class refuses settlement but reports for information with the null printed.
- Monthly close with frozen regressors, half-even integer rounding done once at statement construction, and the qualifier carried with every figure.
- A saving. The engine is uncertified (13 of 15 method probes pass, 14 Sep 2026); until all fifteen pass, nothing computes, estimates or displays a saving — including to you.
- Estimates where a declaration is missing. A missing metering class, tariff or point of delivery is a refusal naming what is required, not a guess.
- Self-service tiers. Modules are provisioned per tenant by Cyntech at tenant creation; adding one is a scoped change to the engagement, not an upsell screen.
Engine certification status, dated: uncertified — 13/15 probes passing, 14 Sep 2026. The method (CYN-NEX-MV-01 Rev A) is issued; the remaining two probes are blocked on a statement-specification question, not on site data. When the fifteenth probe passes this page changes.
How an engagement starts: /engage. Measured service status: /status. Security posture, dated: Security Centre.