Practical answers before you connect RootTruth to a live environment.

RootTruth^™ is designed for machinery, automation and process investigations across industries, including Manufacturing & engineering, Food & beverage, Pharmaceuticals & medical devices, Chemicals & process industries, Energy & power generation, Oil, gas & petrochemicals, Water & wastewater, Mining, quarrying & metals, Logistics & warehousing, Transport, ports & airports, Marine & offshore, Agriculture & forestry, Packaging, paper, textiles & printing, Waste & recycling, Buildings, infrastructure & data centres. Machine builders, OEMs, systems integrators and engineering service providers can also use it across their customer environments.

This is not an exhaustive list. Suitability depends on available evidence, integration and site requirements. Explore the industry applications or discuss your environment with us.

No. The core architecture is local-first, so event capture, evidence storage and investigation are intended to continue on customer-controlled infrastructure without relying on continuous internet access. Optional cloud-enabled features can be added separately where appropriate.

RootTruth^™ is being designed to surface connection health and data-quality issues rather than silently presenting incomplete evidence. The exact reconnect, buffering and health-monitoring behaviour will be validated during product testing and deployment trials.

No. RootTruth^™ is intended to sit alongside existing automation and video systems as an investigation layer. It does not replace the control system that runs the machine.

That is the intended deployment model for many sites, subject to the required compute, storage, video load and IT/OT policies. Dedicated hardware may still make sense in some environments.

The product direction is that customer event data, video evidence, PLC history and investigation records remain the customer's data. Contractual wording and retention responsibilities will be formalised before commercial launch.

Yes. Local-first deployment is a core design principle. A customer should be able to operate the core platform while keeping captured evidence on infrastructure they control.

The standard evidence workflow is read-oriented: observe, capture and investigate. RootTruth^™ is not intended to command machine outputs as part of normal event investigation.

The current product direction includes named accounts, role-based permissions and auditability, with architecture that can support stronger enterprise identity options later. Final security documentation will follow product validation.

Retention will be configurable to suit the customer's storage capacity, operational needs and governance policies. Video typically drives the largest storage requirement, so sizing will form part of deployment planning.

A pilot starts with a defined machine or problem, establishes a baseline, connects the relevant evidence sources, captures real events and then reviews the measured result. The goal is a clear Expand / Refine / Stop decision.

Useful measures include investigation time, repeat-event frequency, downtime impact, evidence quality, cases resolved and engineering knowledge retained.

That depends on the customer's event frequency, downtime cost and improvement achieved. Even modest reductions in investigation time or repeat downtime can be commercially meaningful, but the business case should be based on measured site data rather than a generic savings claim.