Skip to content
NewNow in GermanAuf Deutsch
Camzify
Book a Demo
AI detection · Built to order

Custom AI detections, built to order

When none of the 23 standard detections covers what a site needs, Camzify builds the detection. The requirement is defined with you first, the build is priced once, and the finished detection is licensed per camera like any other, in the cloud or on premises.

Discuss a detection The 23 standard detections
  • One-off build price, then per camera
  • Cloud or on premises
  • Build footage deleted afterwards

Detections already built for customers

These started as requirements the standard detections did not meet. They are examples, not the limit of what can be built.

  • License plate recognition

    Reads US and Singapore plates from the camera image and alerts on a watchlist, for the gates and car parks where a plate matters more than the vehicle.

  • Facial recognition

    Built only on request, for a customer with the legal basis to use it. Never part of the standard detections; see below.

  • Eating and drinking detection

    Flags eating or drinking in the areas of a site where it is not allowed.

  • Shoplifting detection

    Flags shoplifting behavior on store cameras, beyond what the standard detections look for.

Before you commission one

Try a plain-language alert first

Some needs do not call for a new detection at all. Behavioral anomaly detection, one of the 23, lets you describe the behavior to watch for in your own words, such as someone smoking in the loading bay or a fire door propped open, and alerts when it sees it. If that covers the need, nothing has to be built. If it does not, that is the point to request a custom detection, and the sentence you tried is a good starting point for the requirement.

How a build works

  1. Step 01

    Define the requirement

    We agree what should count as a detection, on which cameras, and what should happen when it fires. What the build itself needs depends on the detection, and is settled here.

  2. Step 02

    Price and timeline

    Once the requirement is agreed you get the one-off build price and the timeline. Both depend on the detection, so neither is given before this point.

  3. Step 03

    Build

    Camzify builds the detection. Any footage used for the build is deleted once it is finished.

  4. Step 04

    Deploy and license

    The detection goes live in the cloud or on premises and is licensed per camera, one detection instance per camera it runs on, like the standard detections.

What it costs

Two parts. A one-off build price, quoted once the requirement is agreed, and then the normal per-instance pricing: each camera the detection runs on takes one detection instance, exactly as with the standard detections. Nothing about the rest of the account changes.

Where it runs

In the cloud or on premises, the same choice as the rest of the platform. A site that keeps its footage on its own servers can run a custom detection there too. The footage used to build the detection is deleted once the build is finished.

Identity

Facial recognition is a custom build, never a default

None of the 23 standard detections identifies anyone. Attribute extraction and suspect search work on clothing, carried objects and timing, the details a witness would give, not on faces.

Facial recognition exists only as a custom build, made on request for a customer that has the legal basis to use it. That basis is the customer's to establish: under the GDPR, facial images processed to identify a person are special-category biometric data, and in Illinois the Biometric Information Privacy Act requires notice and written consent before biometric identifiers are collected. Other places have their own rules.

Related

The 23 standard detections

What ships today, with the catalog of what each one catches.

AI architecture

How the standard detections process video, layer by layer.

Security and compliance

Encryption, access control and where footage is kept.

FAQ

Frequently asked questions

Yes. When none of the 23 standard detections covers what a site needs, Camzify builds the detection. The requirement is defined with you first, the build is priced once, and the finished detection is licensed per camera like any other.

For customers so far: license plate recognition, facial recognition, eating and drinking detection and shoplifting detection, among others. Each started as a requirement a standard detection did not meet.

A one-off build price, then the normal per-instance pricing: each camera the detection runs on takes a detection instance, exactly as with the standard detections. The build price depends on the detection and is quoted once the requirements are agreed.

It depends on the detection. The timeline is set together with the requirements, before any work starts, so you know it before you commit.

It is deleted once the build is finished.

Yes. A custom detection can be deployed in the cloud or on premises, the same choice as the rest of the platform.

Not as a standard feature. None of the 23 standard detections identifies anyone: attribute extraction and suspect search work on clothing, carried objects and timing, not faces. Facial recognition exists only as a custom build, made on request for a customer that has the legal basis to use it.

Try behavioral anomaly detection first. It is one of the 23 standard detections: you describe the behavior to watch for in your own words, such as someone smoking in the loading bay, and it alerts when it sees it. If that covers the need, nothing has to be built; if it does not, that is the point to request a custom detection.

Ready to patrol your site 24/7?

Book a 15-minute demo and see a live patrol run on your own cameras.

Book a DemoCalculate Your Savings