In development

You are welcome to use it on real jobs. Feedback shapes what gets built next, and beta testers keep their pricing fixed for life.

In development · Beta pricing fixed for life

Tell us what you think

Connectors and partnerships

You know what your devices do. We know where they are.

Every manufacturer platform knows a device's serial, model and status. Almost none of them know the coordinate it sits at on a drawing, who installed it, when it was commissioned, or what the client signed off. Graftix does, because an engineer pinned it during first fix.

What we bring

The data nobody else in the chain holds

Installation is where device data is created, and it is also where most of it is lost. Graftix sits at that moment, which makes it worth connecting to.

01

Physical location

Not a postcode. The coordinate on the drawing, the floor, the room, the riser. Pinned by the engineer who installed it, on the sheet the building was built from.

02

The commissioning record

Who addressed it, who tested it, what the result was, and the date the client accepted it. Information that currently evaporates the week a job finishes.

03

Asset lifecycle

Serials, models, install dates and warranty start, held in an asset register that outlives the project and feeds the maintenance contract after it.

Where things stand

Honest status, not a wall of logos

One integration described properly is worth more than twelve greyed-out badges. This is exactly what exists today.

Live

Extreme Networks XIQ

Device status pulled from the network estate onto the drawing, matched to pinned tasks by serial number, with hostname push back to the controller as devices are commissioned. Read-only by default; every write is explicit and logged. Built during a live campus refresh across eighty-plus buildings.

In testing

On-premise node connectors

A lightweight agent for IP device monitoring inside the estate, for the large proportion of installed kit that has no cloud platform behind it at all. Currently in testing rather than released, and we will say so until it is not.

In development

Fire alarm panel gateway

Panel state surfaced against the devices on the drawing, so a fault has a location rather than just a zone number. This is Graftix Live for the fire trade, and it is the integration we get asked about most.

Wanted

Cable certification testers

Link test results attached to the outlet they belong to, instead of a bulk export filed at the end of a job and never opened again. Open a task, see the full result. The join is the cable ID the engineer already typed into the tester.

What we are looking for

Categories, not a shopping list

If you build any of these and the idea of your devices carrying a physical location and a commissioning history is interesting, we would like a conversation.

Network and device platforms

Cloud management for switches, access points and connected hardware, where live status belongs on the drawing.

Access control and intruder

Controller and panel platforms where door and device state should map to a real position in a real building.

Fire detection

Panel manufacturers willing to expose device and fault state, so a fault reads as a location rather than a loop address.

Test and certification equipment

Cable certifiers, electrical test instruments and anything producing structured results that should live on a task.

Product data and specification

Datasheets, symbol libraries and specification data that could populate technical submittals automatically.

Distribution and stock

Live pricing and availability feeding take-off lists, purchase orders and material pools directly.

Warranty registration

We already hold serial, install date and location. Most manufacturers spend real money chasing exactly that and rarely get it.

Business systems

Accounting, payroll and CRM, so project cost and labour stop being re-keyed between systems.

How we build them

An open standard, not a proprietary SDK

Graftix speaks the Model Context Protocol, the open standard Anthropic built for connecting AI assistants and systems to real data. That means an integration does not have to start with someone learning our API, and it means an AI agent can already query a live Graftix project directly.

Where a platform has a REST API we will build to it, as we did with XIQ. Where a manufacturer would rather define a custom workflow, we are happy to start there instead. What we are not going to do is ask you to adopt something proprietary.

  • Read-only by default, with writes explicit, scoped and logged
  • Regional data residency, so integrations respect where a customer's data lives
  • Customer credentials held in an end-to-end encrypted vault we cannot read
How we handle data

Shot CN1

Live device status from an integration, shown on the drawing

1600 × 1200

Get in touch

Your devices are already in our drawings.

If you manufacture, distribute or platform anything that gets installed in a building, there is a conversation worth having. Tell us what you build and what you would want out of it.