Help Center

The edge agent reads OPC UA, Modbus TCP, Modbus RTU, Siemens S7, EtherNet/IP, Mitsubishi MELSEC, Omron FINS, Beckhoff ADS, BACnet/IP, MQTT, Sparkplug B, AVEVA PI Web API, CSV file watch, and JSON file watch out of the box. It runs on a small Linux box on your OT network, or in an industrial DMZ if your segmentation puts it there, and it only makes outbound connections: to the controllers or MQTT broker, and over TLS 1.3 to the Haltless cloud. Full deployment notes at docs.haltless.io.

No. One edge agent typically covers a line, a cell, or a small plant, polling many controllers concurrently. Sizing comes down to tag count and sample rate; a typical agent reads thousands of tags per second on commodity hardware.

All tenants are hosted in the United States. The audit chain and your operational data are bound to that region for the lifetime of the tenant.

The cloud platform is the default deployment. Single-tenant private cloud and customer-VPC deployment are scoped per deal; talk to sales about specific cloud and region pairs.

Most single-site pilots are productive within two to four weeks: connect the edge agent, validate the tag mapping, let the detectors settle, agree the alert thresholds with the maintenance lead. Multi-site rollouts add a configuration-template step on top.

OPC UA, Modbus TCP, CSV file watch, and JSON file watch are in production, and the edge agent reads Siemens S7 and EtherNet/IP natively, with no gateway in between. It also subscribes to MQTT brokers, plain values or JSON. It reads Modbus RTU, Mitsubishi MELSEC, Omron FINS, Beckhoff ADS and BACnet/IP natively as well, decodes Sparkplug B from a broker, and takes current values from the AVEVA PI Web API. See the architecture page for the current and planned coverage.

Tenant telemetry, the audit chain and its signing key are hosted in the United States and stay there. Two sub-processors keep data elsewhere: HubSpot holds our CRM, including what you send through our website forms, in its EU data centre, and Cloudflare serves the client portal from the edge location nearest each user. Our Google Workspace mailboxes use Google's data centres, which are not limited to one region. The status page runs on Atlassian Statuspage in the United States. Annex III of the Data Processing Addendum lists every sub-processor with its processing region.

No, by design. The three detection methods (static baseline z-score, EWMA, rate-of-change) are deterministic. The health score is a published formula with a documented per-event deduction schedule. Customers and their auditors can reproduce every number.

Per machine, with the specific figure and machine limits quoted per opportunity. Contracts are annual as standard, invoiced monthly or annually, and both the term and the billing frequency are stated in your contract. Invoices are issued through QuickBooks and paid by bank transfer, with any applicable VAT or sales tax shown on the quote and the invoice. Request a quote for the exact number.

The platform includes a built-in CMMS workflow and production adapters for SAP S/4HANA, Oracle EBS and Microsoft Dynamics 365, which open and update work orders in the system you already run. For other systems we offer webhook contracts and the open Haltless API at docs.haltless.io.