Skip to main content

How Haltless Works

How Haltless works​

Haltless sits between your machines and your team. Sensor data flows in, anomaly detection watches it in real time, and the signals come back out as alerts you can act on — in the dashboard, over the API, on a live WebSocket stream, or delivered straight to your own systems.

This page is a conceptual map. You don't operate any of this infrastructure yourself; you integrate with the hosted platform at https://api.haltless.io/api/v1.

The path your data takes​

flowchart LR
  M[Machines and sensors] --> E[Edge Agent]
  M --> D[Direct ingestion API]
  E --> C[Haltless cloud]
  D --> C
  C --> A[Anomaly detection]
  A --> AL[Alerts]
  AL --> DB[Dashboard]
  AL --> API[REST API]
  AL --> WS[WebSocket stream]
  AL --> WH[Webhooks]

The pieces​

Your machines and sensors​

Everything starts with the equipment on your floor — temperature probes, vibration sensors, pressure gauges, and whatever else reports the health of a machine. Each machine has an identifier you choose, and each reading carries a metric name, a value, a unit, and a timestamp.

Getting data in​

There are two ways to move readings from your equipment into Haltless:

  • The Edge Agent. A lightweight agent you run near your machines. It connects to your sources over OPC-UA, Modbus, CSV, or JSON, collects readings, and streams them to Haltless. This is the usual choice for continuous production data. See the Edge Agent overview.
  • Direct ingestion. Send readings yourself with POST /api/v1/ingest. This is ideal when your data already lives in a system that can make HTTP calls, or when you want to try things quickly. See the direct ingestion guide.

Both paths carry the same kind of readings and feed the same pipeline.

Anomaly detection​

As readings arrive, Haltless compares each one against what "normal" looks like for that machine and metric. When a value drifts outside its expected range, Haltless raises an alert. You can shape when and how alerts fire with alert rules, and Haltless also surfaces forward-looking predictions about equipment health.

Getting signals out​

Once an alert exists, you can consume it in whichever way fits your workflow:

ChannelBest forLearn more
DashboardPeople watching the fleet in a browser—
REST APIPulling alerts and data on your scheduleAlerts
WebSocket streamReacting the instant something changesWebSocket integration
WebhooksPushing alerts into your own systemsWebhook setup

Webhook deliveries are signed, so your receiver can verify they genuinely came from Haltless.

From alert to action​

Alerts are the starting point, not the end. Around them, Haltless gives you the maintenance building blocks to close the loop: work orders, maintenance records, downtime logging, OEE, and more — all reachable through the API.

Security and access​

  • Encryption everywhere. Traffic to the API is protected with TLS in transit, and sensitive data is encrypted at rest.
  • Two kinds of credentials. API keys authenticate data coming in from your machines; Bearer access tokens authenticate people and applications reading and managing data. See Authentication.
  • Role-based access. Your role controls what you can see and do; account admins manage your team's roles.

Next steps​