Your cameras see it. Now they act on it.

The problem

Repeated near misses at one machine

Everyone knows the spot. Nobody can say how often it happens, or when.

The problem

People in areas that should stay clear

A fence or a painted line works until the day it doesn't.

The problem

Forklifts and people sharing aisles

Crossings and blind corners that nobody can watch on every shift.

Watching 3 zones Demo site · 3 cameras online

Demo site.

Now

Sees

Someone on the infeed while the baler runs

Acts
  • Stack light red at the machine
  • Stop signal to your control system
Keeps

The clip, ready to review

Now

Sees

Someone inside the Gate 2 enclosure

Acts
  • Gate beacon red
Keeps

The clip, ready to review

Now

Sees

Someone inside a forklift’s envelope

Acts
  • Siren in the aisle
  • SMS to the supervisor, where supported
Keeps

The clip, ready to review

The envelope applies where technically supported and validated.

Being hit by moving plant or vehicles or injured when working with fixed machinery are preventable.

Trent Curtin, Head of SafeWork NSW, March 2025

The next near miss. With and without.

Same spot. Same camera. A different outcome for the person, the machine and your team.

A site camera's view of the baler: a person steps onto the infeed while it runs, and nothing else happens.
Recorded. Nothing else happens.
The next near miss. With and without.
Without With MachineWatch
The person Without: No warning. With MachineWatch: Warned at the spot, as it happens.
The machine Without: Keeps running. With MachineWatch: Your control system gets a stop signal.
Your team's time Without: Hours searching footage. With MachineWatch: The clip's already kept.

Not after. In the moment.

It acts.

It warns the person, signals your control system to stop, and keeps the clip, while it's happening.

See how it works
The same baler with MachineWatch: the zone around the infeed is red and the stack light is on as the person steps onto it.

Mark the zone. Choose what happens.

MachineWatch is software for your site cameras. Your team marks the zone and sets the rule. From then on it watches the zone on every shift, and acts when someone's in it while the rule applies.

Mark the zone

Draw it on the camera view: the infeed, the gate, the aisle.

Set the rule

Someone in the zone at any time, or only while the machine runs, from its running signal.

Choose what happens

A light or siren at the spot, an SMS where supported, a stop signal to your control system. The clip is kept each time.

Then it acts

While someone's in the zone, it does what step 3 says, and keeps the clip with the time, camera and rule.

The baler's infeed band marked in amber on the camera view. Infeed conveyor band

When Person is in Infeed conveyor band and Machine active (DI-1) is On

  • Stack light: red, flashing: on
  • Shutdown-request signal on DO-2 to site control: on Your control system performs the machine response.
  • Save event image and clip, 4 s before and 4 s after: on
  • Send SMS to shift supervisor (where supported): off
The baler infeed: someone on the infeed while the baler runs. The zone around it is red and the stack light is on.
Now · Baler line 114:32:11 What it did
  • Stack light red at the machine
  • Shutdown-request signal sent
  • Clip kept, 4 s before and after

That's one rule.
Build your own.

Templates are ready for machine zones, restricted areas, and forklifts and people. Advanced Rules combine your own from these.

Your rules live in the portal
Infeed, running, no bypassAdvanced Rule

IfA personis inInfeed bandand the machine isRunningandBypassisOff

ThenSeverity: HighShutdown-request signalStack light redSMS to the supervisorKeep the clip

Machine idle? Same zone, Severity: Low log it, no light, no signal.

Also: A supported vehicleWithin a set distance of a vehicleOther digital inputsDigital outputsEmail

Distance conditions apply only where technically supported and validated. SMS where supported. Illustrative.

One portal for every zone it watches.

Your team signs in to see every event, review it, set up zones and rules, and check that everything is running.

Events

Every event, in one list

Across every camera and zone: what happened, how serious, what it did, and whether someone has looked.

Illustrative portal view: the list of events for a site, with severity, response and review status.

Review

Review it, note the fix

Watch the seconds before and after, note what was done about the cause, mark it reviewed, and export the evidence.

Illustrative portal view: an event under review, with its response, the system state and a note on the fix.

Zones

Draw the zone

Place points on the camera view to mark the zone, and choose what to watch for in it. Change it whenever the site changes.

Illustrative portal view: points placed on the camera view to draw a zone, with its settings.

Rules

Set the rule

Start from a template or build an Advanced Rule: who, where, the machine's state, the severity and what happens.

Illustrative portal view: a machine-zone rule with its inputs, severity and responses.

Health

Know it's running

Compute, cameras, inputs and outputs, with a lamp at the machine. If a camera drops out, you see it here.

Illustrative portal view: system health for compute, cameras, inputs and outputs, with one camera offline.

Runs on site. Managed in the portal.

A small computer on your site runs the rules on the camera video. Your team works in the portal: events, evidence, rules and health.

Your site

On your network. Keeps working without the internet.

What goes in

A white bullet IP camera on a wall mount.

Cameras

Supported IP cameras, existing or supplied.

Machine signals

Wired to the I/O module.

  • Machine active
  • Bypass
  • Other inputs
The Standard MachineWatch compute: a black finned box with the MachineWatch logo.
Standard
The Rugged MachineWatch compute: a low black finned box with the MachineWatch logo on its side.
Rugged

MachineWatch compute

Runs your zones and rules on the camera video, on site, on every shift.

The MachineWatch I/O module.
I/O module

4 inputs and 4 outputs. Machine signals in; the light, the siren and your control system out.

What comes out, on site

The MachineWatch light and siren, its ring lit red.

Warns at the spot

The light and siren, at the machine.

  • Stack light
  • Beacon
  • Siren

Signals your control system

Your control system decides and acts.

  • Shutdown-request signal
  • Digital outputs
  • System active or fault

Publishes to your site systems

Each event, on your site network.

  • MQTT
Internet events, clips and health email and SMS alerts

MachineWatch Cloud

Over the internet. Your team signs in to the portal.
Illustrative portal view: the Events screen, each event with its frame, time, severity, response and review state.

In the portal

Events, evidence, rules and health

The video is processed on site. Each event's image, clip and context goes to the portal.

  • Events
  • Zones and rules
  • System health

To people

Email and SMS

By severity, where supported.

For your controls and IT teams

What your engineers will ask.

Deployment and security
Does it control our machines?
No. It sends a shutdown-request signal. Your control system decides and performs any machine response.
Is it a safety system?
No. MachineWatch works alongside your guarding and safety controls, never in place of them.
Where does the video go?
It's processed on site. Each event's image, clip and context goes to MachineWatch Cloud.

From $55
a camera, a month.

The monthly price covers the software, the portal and your alerts. Own the hardware outright, or have the compute built in.

Own the hardware

Buy the compute once, then pay for each camera.

From$55

Per active camera, per month Plus the compute, bought once. From $2,341.
Billing starts
On your order date
Money back
On the hardware, within 14 days of your order
  • The compute is yours: Standard or Rugged
  • Add the I/O module and the light and siren
  • Use your supported cameras, or add ours
No compute to buy

Compute included

No compute to buy upfront. Its price is spread across your cameras.

5 cameras

$83.61

Per active camera, per month, for the first 18 months $55, plus $28.61 for the compute, spread over 18 months with a 10% funding charge.
Billing starts
On your order date
Minimum term
18 months. Cancel sooner and you pay out the rest of the compute.
After 18 months
$55 a camera, a month
  • The compute included: Standard or Rugged
  • Add the I/O module and the light and siren
  • Use your supported cameras, or add ours

Several sites

Order for each site and manage them yourself, or talk to us about a wider rollout.

Same prices

Per camera, at every site, on either plan
Each site
Its own compute, owned or included
Our help
Planning a wider rollout, if you'd like it
  • Every site in one portal for your team
  • Sites added on the same subscription

Every camera, every month

Whichever way you pay, each camera's monthly price covers all of this.

  1. The portal for your team
  2. Zones and rules
  3. Events and evidence
  4. Health monitoring
  5. Processing on site
  6. Email and SMS alerts, where supported

No site minimum.

Illustrative portal view: an event with its clip, before and after frames and what happened. Illustrative portal view
The Standard MachineWatch compute.

Prices in AUD, including GST.

Questions before you order.

What people ask about ordering, setting up and day to day. These come up first.

All questions

Ordering and billing

What's in the box?

The compute you chose, Standard or Rugged, with the I/O module and the light and siren if you added them. Our cameras too, if you ordered them.

When does billing start?

On your order date, whichever way you buy.

Is there money back?

Yes, on the hardware: within 14 days of your order.

Can we use our existing cameras?

Often. Supported IP cameras can be reused, or add ours when you order.

[How to check a camera is supported. To confirm.]
Can we run several sites ourselves?

Yes. Order for each site and see them all in one portal. Talk to us if you'd like help planning a wider rollout.

Setting up

What does the electrician connect?

Machine signals in, such as machine active and bypass. Out: the light, the siren and the shutdown-request signal to your control system. The I/O module has 4 inputs and 4 outputs.

How fast is the signal?

It depends on your network and your control system, so test it on your site when you set up the rule.

Day to day

Is MachineWatch a safety system?

No. It watches configured spaces, sends signals and keeps evidence. It works alongside guarding and safety controls, never in place of them.

What if it triggers when it shouldn't?

Rules combine the zone with the machine-active and bypass inputs and a severity, so a request is sent only when the rule says so. Test each rule when you set it up.

What if a camera or the compute goes offline?

The portal shows camera, compute and output status, and a local active or fault indication can be fitted at the machine.

Will we see near misses we didn't know about?

For the zones and rules you set, yes. Each configured event is recorded, so you can see how often it happens and where. Expect more events at first: better observation shows what was going unseen.

Is this workplace surveillance?

Yes. Cameras on workers count as surveillance under NSW and ACT law, so notice and signage rules apply. MachineWatch watches configured spaces around machinery and records the events that match a rule.

Order it. Plug it in. Draw the zone.

Everything ships in one MachineWatch box. You plug it in, your electrician wires the I/O module, and your team draws the zone.

What's in the box: MachineWatch compute. Runs your zones and rules on site, on every shift. I/O module. Machine signals in; the light, the siren and your control system out. Light and siren. Warns the person at the machine. Camera. Ours, or your own supported IP cameras.