Pilot to production, stated plainly
Nexus is sold per tenant, scoped to that tenant's plant and question. There is no published price list; a pilot is quoted per site, in writing, after a scoping call — and the quote names exactly what it includes. This page states the shape so you are not left to guess.
What an engagement is
Solar PV and hybrid operators today; fuel terminals, tank farms and process plants next.
Your existing PLCs, inverters, meters and gateways are read over MQTT/TLS or an HTTP fetch you configure. Every reading arrives with its source time, is deduplicated on message id, and is held until a person on your side classifies it. Dashboards, alarms with owners, and coverage on every figure.
Sites where money will move on a measured saving: PV self-consumption, generator displacement, tariff optimisation.
Whole-facility baseline against utility and check metering under CYN-NEX-MV-01 Rev A. Days and months are admitted or refused, never prorated. The method is issued; the engine that computes a saving is certified only when the method's fifteen probes pass, and until then no saving is shown to anyone — including you.
Operations teams asking why a plant behaved as it did.
The platform analyst searches your telemetry and the platform's own records and proposes a correlation with the readings that support it. It never writes a position: what it proposes becomes one only when a person on your side declares it, with the evidence cited. A modelled figure is always marked modelled.
How it starts
- 01Scoping call
Which site, which devices, what question you want answered. We read what is already installed before proposing hardware.
- 02One site, one link
A single gateway or API. Devices appear in your portal's holding queue with their receipts; nothing is derived from a reading until you have classified it.
- 03You classify, we do not guess
Each metric's class, unit, cadence, role and asset is a declaration you make in your own portal, corrected only by supersession — never overwritten. Where a declaration is missing, the tile says what is required instead of showing a number.
- 04Your own readings inside a week
Coverage-graded views, alarms with dispositions, a reading time and age on every value. The pilot's length is agreed per site at scoping and written into the quote.
What you can reach in the portal is set by the modules provisioned on your tenant when Cyntech creates it — telemetry, alerts, energy, integrations, documents, projects, support, maintenance, assets, drawings, compliance, process alarms. Measurement & verification is provisioned the same way, per tenant, not switched on by default. A module you have not engaged is not visible, and adding one is a change to the tenant, not a licence upsell.
Cost: per site, quoted after scoping. Duration: agreed per site and written into the quote. Neither is published as a number here because neither is a single number.
What it takes to go live
- A signed data-processing agreement (controller-to-processor, SCCs on file) and named tenant administrators, each with a second authentication factor.
- For any figure with money on it: a metering class declared per series and a point of delivery per site — without them the platform reports kWh with a null cost and the reason, not an estimate.
- For M&V: a baseline admitted under MV-01 §8, a non-routine event register (an open event refuses issuance), and the §13 engine certification — no statement of saving is issued before it.
- Tenant isolation by row-level policy on every table, measured and dated on the Security page rather than promised here.
Hosting region and the data-residency position: /legal/data-residency. Measured service status: /status. Security posture, dated: Security Centre.