Skip to content
Indagate

Start with the tools and skills you already have.

Beginners, no-code operators and controls engineers get the same governed connection layer — guided presets, copyable setup, and a safe test before real data is introduced.

Connect a systemChoose a learning pathway

Choose, connect, verify.

  1. 01 — Choose

    Recognize your tool

    Matter, The Things Stack, OpenClaw, MCP, n8n, Zapier, Make, or any HTTPS system you already run.

  2. 02 — Connect

    Copy the safe defaults

    Indagate selects the transport and issues a tenant-scoped, rotatable credential. You copy, you do not configure.

  3. 03 — Verify

    Send a test event

    Prove inbound ingestion or signed outbound delivery without touching production equipment.

Building and plant systems

  • BACnet — /IP and MS/TP. Discovery, point read, and supervisory write on presentValue with full priority-array handling and write confirmation. This is the deepest path and the one a supervisory-layer replacement runs on.
  • Modbus — TCP and RTU registers, scaled and mapped into the asset model rather than left as raw addresses.
  • OPC UA — nodes browsed and mapped to modelled points, for plant that already speaks it.
  • PLC — bounded telemetry through a Zephyr companion. Agent surfaces do not directly write PLC values.
  • SCADA — events and state surfaced alongside existing tags.
  • CMMS — work orders raised with the triggering trend, alarm or frame attached.
  • MES / ERP — quality records through governed HTTPS APIs.

Workflow and agents

  • MCP — a governed endpoint for agent tooling.
  • n8n, Zapier, Make — no-code routing with safe defaults.
  • Webhooks — signed outbound, tenant-scoped inbound.
  • Matter, The Things Stack — device and LoRaWAN estates.

Try it out, no strings attached.

Route a single event into a system you already run, with no production equipment involved. The free audit maps the rest of the path from there.

Get a free integration auditRead the docs