Cameras that see something, then do something.
LynxVision runs AI detection on your existing cameras and turns what it sees into an action: open the bay door, hold the gate, turn the light red, send the alert. Built by IP Lynx, installed by the same crew that wired the site.
LYNXVISIONDW bridge connected
Cameras
6 streams · 2 models active
Three truck bays, one red light, nobody out of their cab.
An organic waste facility needed safer traffic through three busy truck bays. We put a camera inside and outside each bay, a red and green light at the door, and let LynxVision run the doors. The timing rules are the customer's to change.
- Drivers stay in the truck. No climbing down to push a button.
- A truck can't enter a bay that still has someone in it.
- Fewer pedestrian near-misses around the bays.
- Flow across all three bays improved, because the light does the queueing.
- The delay timer is a setting, not a service call.
Light goes red. Door won't open.
Anything moving inside the bay, a person or a truck, keeps the outside door shut for incoming trucks.
Door opens from the inside.
The inside camera sees the truck lined up to leave and opens the door for it.
Red stays on for a while.
A customer-set delay keeps the next truck out until the bay has settled.
Light goes green.
Nothing moving inside and the timer finished. The bay is open for business.
Door opens for the arriving truck.
The outside camera sees the truck waiting on a green light and lets it in. Then it starts again.
Detect. Decide. Act. Nothing you own gets replaced.
Most camera systems stop at a motion alert. LynxVision sits on a server beside your video recorder, watches the streams you point it at, and calls the equipment you already own when a rule you drew comes true.
01 · Detect
Your cameras
No new cameras needed. LynxVision watches the streams you choose and spots people, vehicles and licence plates.
- DW Spectrum and Nx Witness, through a plugin on the recorder
- Any network camera with an RTSP stream; ONVIF cameras can be discovered
- Pick which streams get AI. Not every camera needs it.
02 · Decide
A rule on the picture
Draw a zone or a line on the camera view and say what counts. The rule is the whole configuration.
- Something is inside the zone, enters it, or leaves it
- Crosses a line in a given direction, or touches it like a photo eye
- Stays too long, or too many of them at once
- Only people, only vehicles, only a certain plate
03 · Act
A real action
When the rule fires, LynxVision calls the thing that needs to happen, with the evidence attached.
- A gate, door opener or light, through any controller that takes a web request
- An event inside DW or Nx, so alarms, bookmarks and notifications work there
- A web call to anything with an address: dashboards, alert tools, your own systems
Draw a zone or a line. Pick what counts.
Every rule is drawn on the camera picture. These are the kinds you can draw today, each with its own filters and timers.
Intrusion
Something is inside the zone. A car in the driveway, a person in a restricted area.
Zone entry
Something moves from outside the zone into it. A truck pulls into the loading area.
Zone exit
Something leaves the zone. A vehicle drives out of a reserved spot.
Line crossing
Something crosses a line, in the direction you pick: A to B, B to A, or either. Gate in versus out, and counting.
Tripwire
Fires when any part of a vehicle touches the line, like a photo eye, after the seconds you set. Once per arrival, so a waiting car doesn't open the door twice.
Loitering
Someone or something stays in the zone longer than you allow. A person at the back door, a car in a no-parking area.
Multiple objects
Fires when the count in a zone reaches the number you set. Two or more people, several vehicles, more than one plate.
Filters that stop false alarms
- Labels only cars and trucks, so a person walking by doesn't open the gate
- Confidence how sure the AI must be
- Cooldown how long before it can fire again
One screen per camera. No scripting.
Open the camera, draw a polygon around the dock, the gate lane, the back door. Pick what should trigger it and how long to wait before it can fire again. No scripting, no vendor ticket. Rules live per camera, so a bay with two cameras gets two rules that each do one job.
Camera Rules · Main gate
Draw the zone or line, then set what counts
Plates, read and acted on.
LynxVision finds the plate, reads it in about 8 milliseconds and keeps the crop whose characters are clearest. Put a plate on a rule and that plate opens the gate. Every read is logged with the time and the camera, and lands in DW Spectrum where you can search it. That settles the "I was never there" conversation.
Live Reads · Main gate
Last 20 plate reads on this camera
| Time | Plate | Crop | Conf. | Action |
|---|---|---|---|---|
| 14:12:08 | CBXK 412 | 0.96 | Open main gate · 200 | |
| 13:58:41 | AVRT 909 | 0.93 | Open main gate · 200 | |
| 13:31:17 | BNPL 274 | 0.89 | Not listed · logged | |
| 12:47:52 | CBXK 412 | 0.95 | Still in view · not re-sent | |
| 12:02:30 | DMKR 118 | 0.91 | Open main gate · 200 | |
| 11:36:09 | AVRT 909 | 0.90 | Open main gate · 200 |
Lives inside DW Spectrum. Talks to anything with a webhook.
LynxVision doesn't replace your video system. A small plugin on the recorder takes every detection and turns it into an event the recorder understands, with the box drawn on the video. So the alarm rules, bookmarks, searches and phone notifications you already use in DW or Nx now react to "truck in bay 2", not just "motion". For everything else, a rule can call any system that takes a web request, such as a gate controller, door opener, lighting or alarm panel, with the plate, camera and confidence filled in.
Your server, your building. It keeps working when the internet doesn't.
LynxVision isn't a cloud service. The AI runs on a server at your site, next to your recorder, and it's locked down like the rest of your security system.
A server in your building
A Windows or Linux server at your site, using an NVIDIA graphics card when there is one. Your camera streams aren't sent to a cloud to be analysed.
Keeps working offline
The licence is checked on the server itself, not online. If the internet drops, detection, rules and the actions on your own network carry on.
Updates when you say so
IP Lynx sends updates, but they install only when someone at your site clicks. You read the release notes first, and a failed update puts everything back.
Everyone signs in
Four roles: viewer, operator, site admin and technician. There's no default password waiting to be guessed.
Passwords stay hidden
Camera and recorder passwords never show up on screen or in the API. Each DW server pairs with its own token.
Your cameras, as they are
Any network camera with an RTSP stream works, and ONVIF cameras can be discovered. Live view runs at about 12 frames a second.
Every event, with the picture that caused it.
LynxVision keeps a history of every rule that fired and every action it called, with the result the other system sent back. When a gate opened for the wrong truck, or didn't open for the right one, you can see why in a minute.
If a camera can see it, a rule can act on it.
These are the jobs that come up most. People, vehicles and trucks work out of the box. Anything site-specific, like a particular machine or a particular part, gets a model trained on footage from your own cameras.
Truck bays and docks
Truck at the door, bay occupied or free, safety light and door control, time in and out for turnaround reporting.
Gates and parking
Open for the plates on the rule, log every read, direction of travel in the lane, vehicles in reserved spots, people walking where only cars should be.
Perimeter after hours
A person or vehicle on the fence line. Rules can be limited to people and vehicles, so only those count. Loitering near doors.
Restricted zones
Someone walks into the area around a machine, a chemical store or a roof access. Warn with a light or a horn, and log it.
Counting and occupancy
Count people or vehicles across a line in each direction, and act when the number in an area reaches what you set.
Garage and overhead doors
A tripwire at the door, set to cars and trucks, calls the door opener. A person walking past doesn't open it, and a car waiting at the door doesn't trigger it twice.
Site-specific detections, say forklifts in a pedestrian aisle or hard hats at a door, are built with LynxCurator from your own camera footage: we collect examples, a person checks them, and the model gets better with each round. We'll tell you up front whether a job is off the shelf or a trained one.
Four tiers, sized by camera streams.
Licensing is by the number of streams the AI watches, not the number of cameras you own. Start with the four that matter and move up when you need to.
Every tier includes plate reading, the review queue, exports and alerts. Pricing is quoted per site after the assessment. The server, cameras and installation are quoted separately, in writing.
You own the system. A Care plan is optional.
Care covers LynxVision the same way it covers the rest of your IP Lynx systems: faster response, cheaper labour and remote time each month. One plan price covers one system, with a discount for the second and third.
- 24-hour response
- 5% off labour
- 4-hour response
- 1 remote hour a month
- 15% off labour
- 2-hour response
- 2 remote + 1 on-site hour a month
- 25% off labour
Response times are business hours. 24/7 emergency availability is $99 per site per month. Canadian dollars, plus tax.
Straight answers.
Still wondering about something? Call (548) 200-5969 or book a site assessment.
Do I need new cameras?
Usually not. LynxVision works with any network camera that has an RTSP stream, and ONVIF cameras can be discovered. Old analogue cameras are normally worth replacing. We'll tell you which is which on the site walk.
Does it keep working if the internet goes down?
Yes. Detection, rules and the licence check all run on the server in your building. Actions on your own network, like a gate or a bay door, carry on. Updates and remote help from IP Lynx wait until the connection is back.
Do I need DW Spectrum?
No, but it gets the most out of LynxVision. With DW Spectrum or Nx Witness, events and plate reads become searchable and drive the recorder's own alarms and notifications. Without one, rules can still call any system that takes a web request.
Does it recognise faces?
No. LynxVision detects people and vehicles and reads licence plates. It doesn't identify people.
Is there an app?
Alerts reach your phone through the DW Spectrum app's notifications. LynxVision itself is managed from a web page on your network.
Who sets up and changes the rules?
IP Lynx sets them up during the install. After that, your site admin can change zones, timers and filters, or ask us to do it.
Can it learn something specific to my site?
Yes. Things like forklifts in a pedestrian aisle need a model trained on footage from your own cameras. We'll tell you up front whether a job is off the shelf or needs training.
What does it cost?
It's licensed by camera streams: Edge 4, Standard 8, Pro 16 or Enterprise 64. Every site is quoted in writing after the assessment, with the server, cameras and installation priced separately.
Have a process you want to automate?
Tell us the thing that keeps going wrong, or the thing someone has to stand there and watch. We'll walk the site, look at the cameras you have, and tell you plainly what a rule could do about it.