For controls contractors & integrators
Your hardware. Your client. Nothing between you and the plant.
The dealer model made you the only route back into a building — and the only one blamed when the graphics page is wrong. Indagate runs on hardware you already deploy, speaks to the controllers already in the panel, and leaves your client’s data on a documented schema. You stay the integrator. You stop being the lock.
Runs on what you already deploy.
NVIDIA Jetson, Raspberry Pi 5, your own Linux or Yocto image on x86_64 or ARM64 — or the QCS6490 reference controller, which is available and never required. The runtime contract is identical on every target: a manifest-scoped runtime and a bounded field edge. Send us your installed base and we will tell you what each device can run.
You are not reselling a box. You are putting a supervisory layer on iron you already trust and already know how to support.
The problem you get blamed for.
Per point, per client, per year. A screen change that is a site visit. A client who cannot leave and knows it. None of that is your pricing — but you are the face of it, because you are the one who commissioned the system that holds them.
Indagate makes leaving easy. That makes staying a choice, and it makes you the one who gave the client the choice. The relationship survives on the work, not on the lock.
What it talks to
- BACnet/IP — Who-Is discovery, object enumeration, ReadProperty, and WriteProperty at a priority you choose per write
- Priorities 1 and 2 refused at the gateway by construction; occupied slots shown before a write lands
- Meters, cameras, CMMS and MES through the integrations paths
- Every write confirmed by the gateway before it is shown as landed, and recorded with who and why
Your client’s controllers keep executing the sequences you commissioned them with. Indagate replaces the supervisory layer, not the control layer, and is not a safety-rated controller.
What the first deployment looks like.
- Day 1
- Gateway on your hardware, read-only. Discovery runs against the panel. You see every device and point as the installer named it.
- Week 1
- Points named against the asset model. First supervisory writes granted per site, on named equipment, at a chosen priority — each one logged with the actor and the reason.
- Handover
- The client owns the record and it exports on a documented schema. You keep the relationship because you set it up, not because they cannot get out.
Specifics
- Runs on
- Jetson, Raspberry Pi 5, your Linux or Yocto image, or the QCS6490 reference controller
- Talks to
- BACnet/IP controllers; meters, cameras, CMMS and MES via integrations
- Exports
- Points, history and records on a documented schema — the client’s, not ours
Common questions
Does this replace the integrator?
It replaces the proprietary supervisory layer. Somebody still has to know the plant, name the points, set the priorities and be there when the sequence needs changing. That is you. What goes away is the part of the job that was holding the client hostage on your behalf.
Can the client leave us?
Yes. They can also leave Indagate — the record exports on a documented schema either way. A relationship that only survives because leaving is expensive was never the relationship. This one survives on the work.
Talk through a deployment.
Tell us the hardware you deploy, the controller vendors you meet most, and the client you would start with. We come back with what day one looks like on that iron.