Built, Proven, Live

How Automatry turns ambitious controls software into dependable products for buildings, engineers and operators.

A look at the engineering path from a working idea to reliable operation across Automatry Core, Edge and site tooling.

Automatry builds software around the whole life of a controls system: how it is designed, commissioned, operated and improved. That view connects our site engineering, gateway platform, commissioning tools and next-generation controls engine.

The result is a faster route from a useful idea to software that engineers and operators can rely on.

Start with the operating problem

Our products begin with work that happens in buildings. Engineers need to trace points across imperfect networks. Commissioning teams need repeatable tests and clear records. Operators need to understand an issue quickly and see what happened after an intervention.

Starting from those jobs keeps product decisions practical. A gateway needs more than a polished interface; it needs durable identity, patient discovery, local buffering and predictable recovery. A controls program needs more than valid syntax; it needs explicit inputs, outputs, timing and safety behaviour.

Design for demanding conditions

Site software has to deal with interrupted networks, restarts, phased handovers, incomplete metadata, duplicated device identifiers and field buses that respond at different speeds. Control tooling has to handle device variants, unavailable equipment, rejected writes and values that do not restore as expected.

We make those conditions part of the design. Persistent commissioning actions are disclosed. Higher-impact changes are owner-gated. Simulations include a restore path and writes are checked by readback. Gateways buffer data through connectivity gaps and use outbound connections so the building network remains protected.

These behaviours make the software easier to operate on an ordinary day and much easier to understand when conditions change.

Build momentum through repeatable tools

Agents help us move from project information to programs, tests and commissioning plans quickly. Contracts, interpreters, simulations and signed artefacts keep that work structured. Engineers can spend more time on operating intent and unusual conditions while the toolchain handles repeatable production work.

Automatry Core brings this approach into controls execution. It is our next-generation, deterministic controls-execution engine and the longer-term execution layer for our agentic direction. The Builder turns readable source into verified, simulated and signed controls code.

The Builder and lab testing are proving out well; field adoption is the next step. We're looking forward to deploying our take on what will help the industry.

Learn continuously from operation

Automatry Edge connects the site to the same engineering loop. At Thirty High, it structures live data across more than 1,000 mechanical plant assets and gives operators a clearer route from equipment behaviour to action. Gateways and tailored supervisory tools support other projects with commissioning workflows, local interfaces and system health.

Each project strengthens the platform. It sharpens how we handle network variation, asset identity, handover information and the relationship between a finding and the work that follows. Those lessons return to the common gateway, data path and operator experience.

Built for where controls are going

Building controls are becoming more connected, more software-defined and more capable of working with agents. Automatry combines dependable local operation with tools that can understand project context, prepare engineering work and support authorised action.

That is the direction across Core, Edge, Hearth, FSM and our commissioning software: one connected engineering system that helps people build faster, operate more clearly and keep improving what the building does.