Custom Operations Builder: Unlock More From the Devices You Have

We're excited to share that the Custom Operations Builder has now reached Limited Availability, meaning customers can put it to use in their live environments. Its purpose is straightforward: help teams get far more out of the devices they already own by opening up new commands and control.

Unlocking what your devices can already do

Modern security devices ship with far more capability than most teams ever put to use. A camera or controller often supports advanced settings for hardening, performance, and configuration that would meaningfully improve a deployment, but reaching them is the hard part. Each capability tends to require its own specific configuration, and that configuration is rarely the same twice. It varies by vendor, by model, and often by firmware version, so the exact command that enables a setting on one device may not work on the next. Applying a single change across a large, mixed fleet becomes a long sequence of one-off, device-specific work that few teams have the time to take on, and so those capabilities sit unused.

The Custom Operations Builder removes that friction. It gives teams one place to build an operation and run it across the whole fleet at scale. Capabilities that were technically available but practically out of reach become something a team can actually turn on and manage at, which is how customers get real, additional value out of hardware they have already bought.

Behind the scenes, the Custom Operations Builder is the vehicle that runs operations across the fleet at scale, carrying out the "recipes" that define what each operation does. Teams build those recipes directly today, and as part of SecuriThings' Agentic Device Orchestrator, the orchestrator's AI is designed to build them as well, so that over time even less has to be defined by hand or through programming languages.

How the Custom Operations Builder Works

Building an operation starts with defining it and setting the response that will signal success. You can scope it to the vendor, model, and firmware it should apply to, so that a single operation behaves correctly across a varied fleet. Teams that would rather not start from a blank page can draw on a SecuriThings library example and adjust from there, while teams with more specific needs can build their own from the ground up.

Running an operation is a matter of selecting the target devices, choosing the operation, and applying it. The Custom Operations Builder automatically sets aside any devices that do not match the operation or cannot be reached, so a run only touches the devices it should. From there, a real-time progress view shows each device as the operation completes, and historical logs let you go back and confirm exactly what ran, and where. Because all of this happens inside the same device management experience teams already use, there is no separate tool or workflow to learn.

Where it's already adding value for customers

The first operations customers are running in the Early Access Program came directly from their own requests, and several put a device capability to work that was already present in the hardware but hard to use at scale. Each one applies across a large group of devices in a single pass rather than device by device.

Here are some examples we've seen:

• Using a camera's built-in IP filtering as an edge firewall. Many devices include an IP address filter that limits which addresses are allowed to connect to them. Turning it on and maintaining the approved list across the fleet adds a layer of hardening at the edge.
• Disabling unused audio on cameras. Many camera deployments never use onboard audio capture but leave it enabled by default. Turning it off removes a function the organization is not using and reduces both privacy exposure and attack surface, and applying it fleet-wide ensures no camera is quietly left recording audio.
• Disabling IEEE 802.1x authentication. 802.1x is a network access control method that requires a device to authenticate before it is allowed onto the network. When a fleet moves onto a segmented or isolated network, or the access policy changes, applying the same setting to every affected device at once keeps them consistent and avoids devices dropping offline one at a time.
• Adjusting IR intensity. Infrared illumination determines how well a camera sees in low light. Tuning it across a group of cameras corrects images that are washed out or too dark, without sending a technician to each location to adjust settings by hand.
• Changing camera stream settings. Stream profiles govern resolution, frame rate, and bitrate, which together set the balance between image quality, bandwidth, and storage. Standardizing them across the fleet enforces a consistent recording standard and keeps footage predictable for the systems that consume it.
• Configuring NTP settings. NTP keeps each device's clock synchronized to a common time source. Consistent time is what makes footage and logs from different devices line up during an investigation, and it underpins certificate and security functions, so setting a single NTP configuration fleet-wide removes a common source of drift.
• Setting device coordinates. Assigning accurate location data to each device keeps the platform's map of the fleet correct, which speeds up locating a device and responding when something needs attention. Correcting coordinates in bulk is far faster than editing devices one by one.

The common thread is repetitive, fleet-wide work that operations teams handle by hand today, and that normally consumes a meaningful share of a dedicated team's time.

What's next

This first release concentrates on changing device configurations. From here, the Custom Operations Builder is planned to grow in a few directions, including applying configuration changes on the management-system side and collecting data back from devices, each of which broadens what a single operation can accomplish. Over time, building these operations is also set to become increasingly AI-assisted, reducing how much a user has to define by hand.

Get started

The Custom Operations Builder is included in the Operational Management add-on and is available to customers now through Limited Availability. Customers interested in trying it out should contact their Customer Success Manager.