Limitations

Genetec limitations in 2026: five documented constraints

What Genetec's own documentation says Security Center does not do, or only does through a partner, written for IT and security teams consolidating video, doors and plates onto one platform. Every constraint below carries the documentation behind it, the operational impact, and the workaround.

Updated August 17, 2026
10 min read
By Sud Bhatija, COO and Co-founder
Genetec limitations: What Genetec's own documentation says Security Center does not do, or only does through a partner, written for IT and security teams consolidating video
How this page is built

Every constraint below comes from Genetec's own Security Center product pages, its FAQ, its supported device list and its compliance portal, read on August 14, 2026. Genetec's site is client rendered and returns almost nothing to a plain fetch, so it was read in a browser rather than left thin. Where Genetec documents nothing, this page says so rather than guessing. Spot AI sells a competing platform, and one claim that circulates about Genetec is corrected here rather than repeated: it is not a closed system. Its own FAQ states that Genetec security solutions are non-proprietary, built on open architecture, and that you choose your hardware, so any page arguing camera lock-in is arguing with a page Genetec publishes.

What Genetec publishes, and what arrives through a partner instead

Openness, deployment choice, export behavior and compliance are documented in unusual detail. Two things are not on any product page, and both of them are the things a shortlist wants scored.

Documented well enough to plan a deployment on
Cameras
Your own hardware
Non-proprietary and open architecture, with a supported device list published to check a fleet against
On site or in SaaS
Streamvault or Cloudlink
Streamvault ships with Security Center pre-installed; Cloudlink publishes camera maximums from 8 up to 800
Archive and export
G64 under the Archiver
G64x is the only re-exportable format; ASF and MP4 are the portable options
Arrives through a Genetec Certified Channel Partner
The demo
Your partner, not a sign-up
Security Center is stated to be exclusively sold through certified channel partners
The detections
KiwiVision, scoped
A Security video analytics module and Privacy Protector are named; the catalog is not publicly specified
The unattended hours
Not publicly specified
Sipelia covers intercom and public address, which is a person speaking
Every box is quoted from Genetec's own Security Center product pages, FAQ, supported device list and compliance portal, read on August 14, 2026.

Where Genetec is genuinely strong

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

Openness stated by Genetec and backed by a document

The FAQ says the solutions are non-proprietary, built on open architecture, and that you can choose your hardware and upgrade as your organization grows. A supported device list is published at genetec.com so a procurement team can check a real inventory against a real list, and Security Center SaaS names ONVIF Profile S plus Axis firmware 6.50 and up as supported by design.

Unification that is named rather than implied

Omnicast for video, Synergis for access control, AutoVu for license plate recognition, Sipelia for communications management and Mission Control for collaborative decision management run as one platform, with intrusion panel integration and industrial IoT beside them. Genetec states Security Center collects data from all your security and operational sensors, from cameras and door controllers to industrial IoT devices.

Evidence handling and compliance are documented in detail

Video sits under the Archiver role in G64 files on infrastructure you run, with Cloud Storage published as an extension of on-premises storage, and deployment published as on-prem, cloud, or hybrid, the choice being yours. The compliance portal carries SOC 2 Type 2, ISO/IEC 27001:2022 and 27017, GDPR, UL 2900-2-3, CMMC and NIS 2, which is weeks of procurement already done for a regulated buyer.

Five documented constraints

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

Constraint 01
Depends on setup

The buying path is documented, and it is exclusive

What the documentation says

Genetec states that Security Center is exclusively sold through our trusted channel partners, and that to get a demo you ask your Genetec Certified Channel Partner or contact Genetec. There is no published self-serve trial anywhere in the product documentation.

What it means operationally

Pointing twenty of your own cameras at the platform this month is a partner engagement rather than an afternoon, and the evaluation timetable belongs to a third party. For a team that wants to prove a detection on a real site before writing a business case, that is the difference between two weeks and a quarter.

Workaround

Genetec's own answer is the certified partner network, and it is a real one: pick the partner as carefully as the platform, ask for a named engineer, and put a scoped proof of concept with an end date into the agreement. Genetec Advantage publishes what it covers, from software releases to support response times, so hold the partner to that rather than to a conversation.

Constraint 02
Design constraint

The AI question is the one the documentation answers least

What the documentation says

KiwiVision is published as the analytics brand, with a Security video analytics module and Privacy Protector named alongside it. The detection catalog itself, whether the modules are separate licenses, and where the processing runs are not stated on the pages read. The documentation names the brand, not the detections.

What it means operationally

A shortlist built on named, shipped detections cannot be scored against a brand name. That turns the AI half of the evaluation into a scoping conversation with a partner, at exactly the point where a buying committee wants a list it can compare, and it usually lands after the platform decision has already gathered momentum.

Workaround

Put a named detection list on the week-one agenda, ask which KiwiVision module each one needs and whether it is separately licensed, and ask where each runs. Where the requirement is a shipped catalog rather than a scoping exercise, price the analytics alongside the platform in the same quote rather than treating them as a later phase.

Constraint 03
Cost consideration

Bridging hardware is a line item in both architectures

What the documentation says

In Security Center SaaS, cameras beyond the named Axis, Bosch, i-PRO and Hanwha models connect through a Cloudlink appliance, published with per-model camera maximums running from 8 up to 800. On premises, Streamvault appliances ship with Security Center pre-installed.

What it means operationally

A 120-camera estate across six sites sizes appliances per site against those maximums rather than against the total, and a site with 90 cameras does not fit the same box as a site with 12. That is hardware and sizing work a per-camera software estimate never showed, and it recurs as sites are added.

Workaround

The publication of the maximums is itself the workaround: size the appliances on paper before the quote arrives, site by site, and check where a site sits against the next model up. Then ask the partner to quote appliances as separate lines so the hardware curve is visible next to the license curve.

Constraint 04
Design constraint

The export format decides what can leave the platform

What the documentation says

The export formats are published in detail. G64x and G64 open in Security Desk or the Genetec Video Player, G64 is deprecated in favour of G64x, G64x is the only format that can be re-exported, and ASF and MP4 are the portable options.

What it means operationally

An insurer, a court or an outside investigator handed a G64x file needs the Genetec Video Player to open it, and a portable MP4 copy cannot be re-exported afterwards. Evidence procedures written without that distinction produce the wrong file at the wrong moment, usually under time pressure.

Workaround

Adopt a two-format rule and write it into the evidence procedure: keep the working copy as G64x because it is the only re-exportable format, and share an MP4 with anyone outside the organization. This is a documented behavior rather than a hidden one, which makes it one of the easier constraints on this page to design around.

Constraint 05
Depends on setup

Response with nobody in the control room is not publicly specified

What the documentation says

Sipelia is documented for intercom and public-address communications, which is a person speaking. No analytics-triggered talk down, strobe or horn behavior appears on the pages read. The documentation covers what an operator can do, not what happens when there is no operator.

What it means operationally

For an estate with a staffed control room this is barely a constraint, because Sipelia and Mission Control are exactly the tools that room needs. For a distribution center at three in the morning, or a site whose control room covers forty locations, the unattended hours are the ones where an incident actually happens.

Workaround

Ask what fires on site when the control room is empty, and ask for it to be demonstrated rather than described. If the answer is that a person is always in the loop, cost the staffing across the unattended hours, because that is the true price of the response rather than the price of the speaker.

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
Channel-only buying path
Security Center is exclusively sold through certified channel partners; the documented route to a demo is your partner
A trial on your own cameras is a partner engagement, not an afternoon
Choose the partner as carefully as the platform; scope a proof of concept with an end date
No published detection catalog
KiwiVision is the analytics brand, with a Security video analytics module and Privacy Protector; the detections are not publicly specified
The AI half of the evaluation becomes a scoping conversation
Put a named detection list on the week-one agenda; price analytics in the same quote
Appliances in both architectures
Cloudlink appliances with per-model camera maximums from 8 up to 800; Streamvault appliances on premises
Sizing per site against the maximums, not against the estate total
Size on paper before the quote; ask for appliances as separate quote lines
Export formats are specific
G64x and G64 open in Security Desk or the Genetec Video Player; G64 is deprecated; only G64x can be re-exported; ASF and MP4 are portable
Outside parties need the Genetec player, and an MP4 cannot be re-exported
Adopt a two-format rule: G64x for the working copy, MP4 for anything shared
Unattended response unstated
Sipelia is published for intercom and public-address communications; analytics-triggered talk down, strobe or horn is not publicly specified
The unattended hours are the ones with no documented behavior
Ask what fires with the control room empty; cost the staffing if a person is required

Swipe the table sideways to see every column.

Genetec data comes from its own Security Center product pages, FAQ, supported device list and compliance portal, read on August 14, 2026. Gaps are marked as not publicly specified.

When Genetec is still the right call

If video, doors, plates, intercoms and intrusion are five systems today and the daily pain is reconciling them, Security Center was built for exactly that and documents it better than most of the field. The open architecture and the published device list make it one of the easier platforms to scope honestly against a real site survey, the compliance portal answers a regulated buyer before the first call, and a certified partner carries the deployment rather than your own team. Most of the constraints above stop applying to an estate with a staffed control room.

How Spot AI addresses the same gaps

Spot AI is a narrower product deliberately, and that is where the difference sits. The detections are named and shipped rather than scoped: 15+ pre-trained Video AI Agents span security, safety and operations, covering after-hours intrusion, vehicle break-in, personal protective equipment, forklift near-miss, falls and hazard-zone crowding, and Iris builds a detection that is not on the list in natural conversation rather than through a partner engagement. A shortlist can be scored against that list on day one.

The route in is shorter too. Any ONVIF or RTSP IP camera works at full functionality with legacy analog through the Intelligent Video Recorder, full-resolution video stays on that recorder in the building with only event metadata crossing the network, and response runs autonomously through talk down, strobes and horns on standard speakers already installed, which covers the hours when the control room is empty rather than the hours when it is staffed.

  • A named, shipped detection set, with Iris for anything not on the list.
  • Autonomous response through standard speakers, covering the unattended hours.
  • Camera agnostic: any ONVIF or RTSP IP camera at full functionality, plus legacy analog through the IVR.
  • Full-resolution video on the IVR in the building, with only event metadata leaving it.
Key takeaway

The question is not which platform has fewer constraints, but whether you are buying one system out of five, or one answer the cameras cannot currently give.

None of that makes Spot AI the right answer for every buyer, and Genetec is ahead on several axes worth naming. It unifies access control, plates, intercoms and intrusion as one platform where Spot AI reaches those through integrations, it publishes a supported device list and export formats in more detail than Spot AI does, and Security Center can run entirely on premises under the Archiver role where Spot AI is hybrid by design and sends event metadata out of the building. Its compliance portal lists SOC 2 Type 2, ISO/IEC 27001:2022 and 27017, GDPR, UL 2900-2-3, CMMC and NIS 2, which is a longer public list than Spot AI maintains, and the certified partner channel that costs you an afternoon buys an integrator who owns the estate at three in the morning.

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.

25+

Bridge33 Capital standardized video across 25 plus properties, each acquisition arriving with a different camera system, and cut footage search from hours to minutes.

Bridge33 Capital, commercial real estate
7 weeks

Staccato went from first conversation to full deployment across an 800-acre campus in seven weeks, on the camera infrastructure it already had.

Staccato, firearms manufacturing
5 min

Liberty-Perry School District resolves an incident in about five minutes, after evaluating ten systems before choosing Spot AI.

Liberty-Perry School District, education

"With Spot AI, we're focused on three things: safety, productivity, and security."

Brock Harlow
CIO, Allied Stone

Frequently asked questions

What are the main limitations of Genetec Security Center?

Five, all documented: it is exclusively sold through certified channel partners, so there is no self-serve trial; KiwiVision is named as the analytics brand without a published detection catalog; Cloudlink and Streamvault appliances are line items in both architectures, with Cloudlink camera maximums from 8 up to 800; the export formats are specific, with only G64x re-exportable; and analytics-triggered response with nobody in the control room is not publicly specified.

Does Genetec Security Center work with third-party or existing cameras?

Yes, and Genetec says so in its own FAQ: its solutions are non-proprietary, built on open architecture, and you can choose your hardware and upgrade as your organization grows. A supported device list is published at genetec.com so a fleet can be checked model by model, and Security Center SaaS names ONVIF Profile S support with Axis firmware 6.50 and up supported by design. In SaaS, cameras beyond the named Axis, Bosch, i-PRO and Hanwha models connect through a Cloudlink appliance.

What AI detections does Genetec Security Center include?

KiwiVision is the published analytics brand, with a Security video analytics module and Privacy Protector named alongside it. What is not publicly specified is the detection catalog itself, whether the modules are separately licensed and where the processing runs. The platform's documented strengths are unification, automatic license plate recognition through AutoVu and collaborative decision management through Mission Control, so treat a named detection list as a question for the evaluation.

What compliance does Genetec publish, and what is missing?

The compliance portal publishes SOC 2 Type 2, ISO/IEC 27001:2022 and ISO/IEC 27017, GDPR, UL 2900-2-3, CMMC and NIS 2, and Genetec states its solutions are built with cybersecurity and privacy by design. NDAA, FIPS and TAA do not appear on that portal alongside the certifications that do. That is an absence rather than a finding, and a federal or critical-infrastructure buyer should ask for it in writing rather than read anything into it.

What is the best Genetec Security Center alternative in 2026?

It depends on which constraint is real for you. If unification across doors, plates and intercoms is the requirement, Genetec is hard to beat and the openness question is settled by its own FAQ. If the same cameras have to cover safety and operations, or you want to prove a detection on your own fleet without a partner engagement, a camera-agnostic platform such as Spot AI fits: 15+ pre-trained Video AI Agents run across the fleet already installed and full-resolution video stays on the Intelligent Video Recorder in the building.