Limitations

March Networks limitations in 2026: five documented constraints

What March Networks' own product and integration pages say Command and Searchlight do not do, written for banking, retail and multi-site security teams with an installed camera estate. Every constraint below carries the documentation behind it, the operational impact, and the workaround.

Updated August 17, 2026
10 min read
By Amrish Kapoor, VP of Engineering
March Networks limitations: What March Networks' own product and integration pages say Command and Searchlight do not do, written for banking
How this page is built

Every constraint below comes from March Networks' own current product, integration and news pages, checked on August 17, 2026. Where March Networks documents nothing, this page says so rather than guessing. Spot AI sells a competing platform, so nothing here rests on an anonymous source or an aggregated user rating, and two claims that circulate about established video vendors are corrected on this page: March Networks does not lock you to its own cameras, since it publishes support for thousands of third-party IP cameras and edge devices, and it is not winding down, since it published a mid-year release on August 11, 2026 and no end-of-life notice appears on any page read.

What March Networks publishes in a list, and what it leaves to the call

Two published lists carry most of this platform's evaluation value: the cameras it supports and the transaction systems it reads. What an imported camera gets, and what happens on site, are not on a page.

The published lists and the deployment choice
Cameras
Thousands supported
Around two dozen manufacturers named, with downloadable lists for the recorders and for Command
Transactions
26 point-of-sale systems
Plus four ATM manufacturers, all named on the Searchlight integrations page
Deployment
Cloud, on premise or both
Command Enterprise Cloud is hosted, maintained and sized by March Networks
What the published pages leave to an evaluation
Imported cameras
AI treatment not stated
AI Smart Search is stated across Command; whether a third-party camera gets the same is not
At the moment
No on-site response published
Alerts and business intelligence are documented; no speaker, talk-down, strobe or horn behavior appears
Beyond loss
No safety or operations set
Searchlight is built around banking, retail and transactions on the pages read
Every box is quoted from March Networks' own product, integration and news pages, checked on August 17, 2026. Tones: gate for a documented constraint, none for neutral.

Where March Networks is genuinely strong

A constraint list is only useful next to an honest account of the product.

Third-party camera support published, not implied

March Networks states its recorders and video management software support thousands of third-party IP cameras and edge devices, names around two dozen manufacturers on the page, among them ACTi, Arecont Vision, Axis, Bosch, Canon, Hanwha, Panasonic, Pelco, Sony and Vivotek, and publishes downloadable device lists. An estate holding ten years of mixed hardware can be checked before anybody quotes.

The deepest published transaction integration list in this category

Searchlight names 26 point-of-sale systems it integrates with, including NCR Aloha, Brink, Verifone, Gilbarco, Flooid, Infor, Retalix, Shopify, SpeedLine, Volante and Wayne Fueling Systems, plus four ATM manufacturers in Diebold, Fujitsu, NCR and Wincor. For a bank or a chain that turns a register exception into a clip with the transaction attached rather than an integration project.

Deployment choice, and an owner investing in the product

Command Enterprise Cloud is hosted, maintained and sized by March Networks, Command Enterprise runs on premise, and one estate can hold both, so sites with a retention obligation or a poor uplink stay local while the rest move. March Networks has been part of Delta since 2021, announced the merger of VIVOTEK's branded video security business in March 2026, and published a 2026 mid-year release on August 11, 2026.

Five documented constraints

Each one is a consequence of how the platform is designed rather than a defect. What matters is whether it collides with your starting point.

Constraint 01
Cost consideration

Keeping your cameras does not mean keeping your recorders

What the documentation says

March Networks sells its own recorders and cameras with Command as the video management software over them, and states third-party support for its recorders and VMS software. The two supported-device lists are published the same way: one for cameras supported by the recorders, one for cameras supported by Command. The recorder is in the path by design.

What it means operationally

Camera reuse is real, and it is the cheaper half of the estate. A 90-branch bank still buys and refreshes a recorder per site underneath those cameras, so the three-year number is a hardware curve with a subscription on top rather than a subscription alone.

Workaround

Itemize recorders separately from software in the quote, per site, with the refresh cycle stated, and ask which recorder and camera lines are the long-term ones after the VIVOTEK merger before ordering hardware. Then compare that total against platforms that do not put a vendor recorder in the path.

Constraint 02
Depends on setup

There are two device lists, and a camera on one is not automatically on the other

What the documentation says

March Networks publishes two downloadable supported-device lists, one for cameras supported by the recorders and one for cameras supported by Command. Both are public, which is more honest than a single blurred list, and it does mean two checks rather than one.

What it means operationally

A site survey checked against the wrong list produces a design that looks approved and fails at commissioning, usually on the older half of the fleet where the survey was least careful. On a 40-site rollout that is a delay measured in engineer visits rather than emails.

Workaround

Check every model against both lists and record which one it appeared on, in the survey itself rather than in someone's memory. Where a camera appears on only one, decide the design around it before ordering, and treat that subset as the first cohort in the pilot.

Constraint 03
Design constraint

What an imported camera gets from the AI is not publicly specified

What the documentation says

AI Smart Search is stated as a Command capability, using natural language processing and advanced algorithms to identify specific events, people or objects across multiple camera views. The pages this page read do not say whether a camera brought in from the supported list gets the same treatment as a March Networks recorder and camera pairing. The documentation covers which cameras connect, not what each one is capable of once connected.

What it means operationally

On an estate that is half third-party by design, that gap decides whether the AI applies to the whole fleet or to the native half of it. A pilot run on the newest March Networks sites can approve a capability that behaves differently on the branches carrying ten-year-old cameras.

Workaround

Ask model by model for the fleet you actually own and get the answer in writing, then run the pilot on the third-party half rather than the native half. If the answer is that behavior varies, get the variance described rather than acknowledged, because that is what the rollout plan has to be built on.

Constraint 04
Design constraint

On-site response is not publicly specified

What the documentation says

Alerts and business intelligence are documented across Command and Searchlight. No speaker, talk-down, strobe or horn behavior appears on the pages this page read. The documentation covers what reaches an operator and what a report shows, not what happens at the site while the event is still running.

What it means operationally

For a register exception that is the correct design: the value is the reconciliation afterwards. For a car park at 23:00, or a branch forecourt with people on it, the platform records the event and tells somebody, and whether anything changes depends on who is available to respond.

Workaround

Ask what fires at the moment of a detection and through which device, and get the answer per site type rather than in general. Where sites already run a public address system, ask which platforms on the shortlist drive those speakers directly, and price a monitoring service for the sites where the answer is nobody.

Constraint 05
Design constraint

The published intelligence set is security and loss shaped

What the documentation says

Searchlight is built around banking, retail and transactions, and that is what the pages describe: video read against point-of-sale and ATM data, with AI Smart Search over the footage. No safety or operations detection set appears, so personal protective equipment, forklift proximity, dock dwell and standard operating procedure adherence are outside the published scope.

What it means operationally

A grocery chain with distribution centers, or a bank with a facilities team, has one camera estate and two sponsors. The transaction half is well served and the safety and operations half becomes a second platform on the same cameras, with its own contract, its own review and often its own recorder.

Workaround

Put the safety and operations questions on the same evaluation sheet as the loss questions from the start, and price both paths: one vendor for transactions plus a second for the rest, against a single platform that covers both. Let both sponsors see the two totals before the transaction case goes to signature.

Constraints at a glance

The same five constraints in one view, sized to paste into an evaluation document.

Constraint
What the documentation says
Operational impact
Workaround
Recorders stay in the path
Third-party support is stated for the recorders and the VMS software, with a separate device list for each
Camera reuse is real; the recorder per site is still bought and refreshed
Itemize recorders per site with the refresh cycle; ask which lines are long-term
Two supported-device lists
One list for cameras supported by the recorders, one for cameras supported by Command
A survey checked against the wrong list fails at commissioning
Check every model against both and record which; pilot that subset first
AI on third-party cameras unspecified
AI Smart Search is stated across Command; whether an imported camera gets the same treatment is not stated
The AI may apply to the native half of a mixed estate
Ask model by model in writing; pilot on the third-party half
No on-site response published
Alerts and business intelligence are documented; no speaker, talk-down, strobe or horn behavior appears
The platform records and notifies while the event is still running
Ask what fires and through which device, per site type; price monitoring where nobody answers
Scope is security and loss
Searchlight is built around banking, retail and transactions; no safety or operations detection set appears
One camera estate, two sponsors, and a second platform for the second one
Price both paths on one sheet before the transaction case is signed

Swipe the table sideways to see every column.

March Networks data comes from March Networks' own product, integration and news pages, checked on August 17, 2026. Gaps are marked as not publicly specified.

When March Networks is still the right call

If the question is which transaction went with which clip, across hundreds of branches or stores, most of the constraints above stop applying, because the platform was built for exactly that reconciliation and publishes the integration list to prove it. Add the two device lists, the choice between cloud and on premise per site, and an owner investing in the roadmap, and it is one of the easier platforms in this category to scope honestly against a real estate and a real retention policy.

How Spot AI addresses the same gaps

Spot AI answers a different question on the same feeds, which is why its constraint list looks different. 15+ pre-trained Video AI Agents span vehicle break-in, fire, cash register theft, after-hours intrusion, personal protective equipment, forklift near-miss, falls and crowding in hazard zones, so security, safety and operations run on one platform rather than on two contracts, and Iris builds anything not on that list in natural conversation in about eight minutes.

The architecture removes the recorder question rather than answering it. Any ONVIF or RTSP IP camera works at full functionality and legacy analog comes in through the Intelligent Video Recorder, which holds the full-resolution video in the building while only event metadata crosses the network. The same AI runs on every connected camera regardless of make, and the response goes out through talk down, strobes and horns on standard speakers already installed on site.

  • The same AI on every connected camera, rather than a capability that may vary by how a camera arrived.
  • One platform across security, safety and operations, so one estate does not need two sponsors and two contracts.
  • A documented response on site through standard speakers, not only an alert and a report.
  • Camera agnostic: any ONVIF or RTSP IP camera at full functionality, plus legacy analog through the IVR.
Key takeaway

Ask both vendors to state plainly what is still not covered after the deal closes. On this pair the honest answer differs by category rather than by feature count.

None of that makes Spot AI the right answer for every buyer. March Networks publishes 26 named point-of-sale systems and four named ATM manufacturers, and Spot AI names none: transaction data reaches it through open APIs, webhooks and an MCP endpoint, which is integration work rather than a shipped connector, so a bank or a chain whose whole case is the register will find more of it already built on March Networks' side. March Networks also publishes two downloadable device lists where Spot AI states compatibility by protocol rather than by model, and it offers a fully on-premise deployment where Spot AI is hybrid by design and event metadata does leave the building. A constraint list earns its keep by holding each platform's shape against your starting point.

Check the constraints against your own fleet

A live pilot on your cameras answers in a week what a spec sheet cannot.

Request a demo

Proof points from Spot AI customers

Customer-reported outcomes from named Spot AI customers.

1M sq ft

Unique Industries covers more than a million square feet with a three-person safety team, catching near misses and falls on the cameras already installed.

Unique Industries, manufacturing and distribution
22

Silver Bay Seafoods replaced fragmented legacy camera systems across 22 locations, including remote Alaska facilities, and lifted operational efficiency 15%.

Silver Bay Seafoods, seafood processing
30 sec

Cambridge City cut footage search from two hours to 30 seconds after consolidating seven municipal locations on one platform.

Cambridge City, municipal government

"The biggest benefit of Spot AI is how easy it is to look up incidents, see the footage, and then share it and collaborate."

Ben Grady
Manager of IT and Database Administration, Nashville Rescue Mission

Frequently asked questions

What are the main limitations of March Networks?

Five, all documented: camera reuse still runs through a March Networks recorder per site; there are two supported-device lists and a camera on one is not automatically on the other; whether an imported third-party camera gets the same AI treatment as a native pairing is not publicly specified; no on-site response behavior appears on the published pages; and the intelligence set is security and loss shaped, so safety and operations questions fall outside it.

Does March Networks support third-party or existing cameras?

Yes, and it is one of the better published answers in this category. March Networks states that its recorders and VMS software support thousands of third-party IP cameras and edge devices, and its third-party camera page names around two dozen manufacturers including ACTi, Arecont Vision, Axis, Bosch, Canon, Hanwha, Panasonic, Pelco, Sony and Vivotek. Two downloadable lists are published, one for the recorders and one for Command, and a camera on one list is not automatically on the other.

Which point-of-sale systems does March Networks integrate with?

Searchlight publishes 26 point-of-sale systems, including NCR Aloha, Brink, Verifone, Gilbarco, Flooid, Infor, Korona, MicroSale, Retalix, Shopify, SoftTouch, SpeedLine, Volante, Wayne Fueling Systems and Xpient, plus four ATM manufacturers in Diebold, Fujitsu, NCR and Wincor. That is the deepest published transaction integration list of any vendor in this comparison set, and it is the main reason a bank or a chain shortlists the platform at all.

Who owns March Networks, and is the product still being developed?

March Networks has been part of Delta since 2021. In March 2026 it announced that VIVOTEK's branded video security business would merge into it, with the combined organization led by Peter Strom, its president and chief executive, and it published a 2026 mid-year release on August 11, 2026. No end-of-life notice appears on any page this page read. The reasonable question is not continuity but which camera and recorder lines are the long-term ones, so ask that before ordering hardware.

What is the best March Networks alternative for safety and operations coverage?

It depends which constraint is real for you. If the problem is the register and the branch network, March Networks is hard to fault and publishes more of its answer than most. If the same cameras also have to cover safety and operations, or something has to happen on site at the moment of a detection, a camera-agnostic platform such as Spot AI fits: any ONVIF or RTSP camera connects as it is, 15+ pre-trained Video AI Agents run across the whole fleet, and deterrence runs through standard speakers already installed.