Skip to content

IoT · Automation · Applied AI

Every dot, checkedWe design and build connected systems for homes, workplaces, farms and fleets — original engineering, verified end to end, from the sensor to the screen.

We design and build connected systems for homes, workplaces, farms and fleets — original engineering, verified end to end, from the sensor to the screen.

Protocols we work with

MatterThreadZigbeeZ-WaveKNXMQTTModbus RTUModbus TCPBACnet/IPLoRaWANNB-IoTCAN busJ1939ONVIFRTSPOPC-UASNMPZigbee2MQTTMatterThreadZigbeeZ-WaveKNXMQTTModbus RTUModbus TCPBACnet/IPLoRaWANNB-IoTCAN busJ1939ONVIFRTSPOPC-UASNMPZigbee2MQTT
Anyone can connect adevice. We make itaccountable.

The Dot Check standard

A dot is a single reading — one sensor, one moment, one claim. Checking it is the whole job: proving it is real, proving it is repeatable, and proving the decision it triggers was the right one.

Field notes

In the field

Five domains, one discipline. Drag through a year of commissioning, cabling, calibration and the quiet moment a system finally runs itself.

01
Sensor meshGreenhouse, block 4
02
Edge rackPlant room, level B2
03
Vision nodeLoading bay, north
04
Fleet telematicsDepot, 06:12
05
Control surfaceResidence, main hall
06
CommissioningHandover day

The method

From the dot to the decision

Every system we build walks the same four steps. Skip one and you get a gadget. Do all four and you get infrastructure.

01 · Sense

Measure the real thing.

The right sensor, in the right place, sampled at the right rate. We would rather spend a week choosing a probe than a year explaining bad data.

  • Sensor selection & siting
  • Calibration & drift checks
  • Signal quality budgets
02 · Connect

Move it without losing it.

Radio, wire or cellular — chosen for the site, not for the datasheet. Segmented, authenticated, and designed to survive the day the link drops.

  • Protocol & topology design
  • VLAN segmentation
  • Store-and-forward buffering
03 · Decide

Turn signal into judgement.

Deterministic rules where physics is enough, models where it is not. Every decision is explainable, testable and reversible.

  • Rules, state machines & models
  • Edge inference
  • Explainable outputs
04 · Act

Then actually do something.

Valves open, setpoints move, gates unlock, the right person gets the right alert. With manual override that always outranks the automation.

  • Actuation & interlocks
  • Human-in-the-loop overrides
  • Alerting that respects attention

Spotlight · Applied computer vision

Cameras that understand

You already have cameras. What you do not have is a camera that can tell you a forklift entered a pedestrian aisle, that the queue is eight deep, or that the seal on line three is drifting. We deploy vision models at the edge, on your hardware, so the video never has to leave the building.

  • Detection & trackingPeople, vehicles, tools and pallets detected and tracked across frames and across cameras.
  • Face & licence plate recognitionRecognition pipelines with an explicit enrolment process and a defensible retention policy.
  • Safety & PPE complianceHelmets, vests, exclusion zones and man-down detection, evaluated continuously instead of on inspection day.
  • Counting & queue analyticsFootfall, dwell time, occupancy and queue length, aggregated to numbers rather than faces.
YOLO familyONNX / TensorRTONVIF / RTSPFrigateNVIDIA JetsonCUDA
Explore Vision AI
Detection, tracking and zone logic running at the edge.

5

Domains

Home, office, agriculture, fleet, vision

18+

Protocols

Fluent, in production, not in a slide

100%

On-prem capable

Every system can run without the cloud

Why Dot Check

The name is the standard

Dot Check is about authenticity: original ideas, honestly built, and proven before we call them done.

01

Original architecture

We do not resell someone else's box with our sticker on it. Every system is designed for your site, your constraints and your budget.

02

Verified by measurement

Claims get instrumented. Before and after, on your data — so the improvement is a number, not a feeling.

03

Yours to own

Open protocols, documented topology, credentials handed over. If you replace us, everything keeps running.

04

Local-first & private

Processing stays on site by default. The cloud is a convenience we add on purpose, never a dependency we inherit.

How we work

Five steps, no surprises

  1. 01

    Discover

    Site survey, constraints, and the outcome you are actually buying.

  2. 02

    Architect

    Topology, protocols, hardware and a written scope you can hold us to.

  3. 03

    Build

    Staged in the lab, commissioned on site, documented as we go.

  4. 04

    Verify

    Acceptance tests against the numbers we agreed at the start.

  5. 05

    Operate

    Monitoring, updates and support — or a clean handover to your team.

Start here

Tell us what should be automatic.

Send a sentence or a specification — both work. You will get a straight answer about whether it is worth building, and roughly what it takes.

Dot Check — Every dot, checked.