Help Center

The edge agent reads OPC UA, Modbus TCP, CSV file watch, and JSON file watch out of the box. It runs on a small Linux box on your IT network or in a DMZ, outbound only to the controllers, with 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 available on the higher tiers; 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. MQTT, native Siemens S7, and EtherNet/IP are on the platform roadmap. See the architecture page for the current and planned coverage.

Tenant telemetry, the audit chain, and the per-tenant signing keys are hosted in the United States and stay there. Some operational sub-processors sit elsewhere: error monitoring, the support platform, the status page, and log aggregation run in the European Union, so anything you put in a support ticket is processed there rather than in the US region. 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. Billing runs through Stripe, with any applicable VAT or sales tax shown before you confirm. Request a quote for the exact number.

The platform includes a built-in CMMS workflow and shipped integration with SAP, Oracle, and Microsoft Dynamics is the next major theme on the roadmap. For other systems we offer webhook contracts and the open Haltless API at docs.haltless.io.