RECORDED
Your cameras saw it.
A person by the fence. A truck at the dock. A door left open. Recording is only the beginning.
Camera intelligence · for the cameras you already own
Ask your
cameras.
Then let
them act.
Search what your cameras saw.
Understand the alert. Give it a next step.
Explore the idea on a synthetic scene, then talk to us about your own cameras.
EXISTING CAMERASONVIF / RTSP · TO EVALUATE
01 / OPEN FRAMEINTERACTIVE PREVIEW
FENCE LINE / CAM 03SYNTHETIC
MATCHING EVENTS
22:14:07person · fence zone · 11 s23:41:12person · fence zone · 26 s02:08:312 people · fence zone · 43 s
12 SYNTHETIC EVENTS · 3 MATCHES
Watch for this →Synthetic scene · illustrative overlay, not product output
How this demo works
This browser searches 12 authored synthetic events across four schematic views. It uses a bounded word matcher, with simple time and duration filters. No AI inference, footage playback or customer data is involved. Your queries stay in this browser.
Rules and action previews are simulated. No messages are sent. Product detection, deployment and integration availability must be confirmed for a pilot.
Explore the complete sample index →A small sample of what you could ask.
No camera connection or sign-up required.
From a recording to a reason
A camera records.
A team needs to know.
The same scene. Three ways to see it.
An illustrative walkthrough of the workflow.
EXPLAINED
Find the moment that matters.
Bring the object, the place, and the time together. See why an event matched—and why another did not.
ACTED
Give the moment a next step.
Explore an alert with context, a person who acknowledges it, and a written record of what happened next.
SCHEMATIC / 01
ILLUSTRATIVE EVENT TIMELINE22:00 — 23:00
22:14:07Person in fence zoneMATCH
22:16:32 Headlight sweep SUPPRESSED ⌄
Illustrative rule: no person in the selected zone, so this motion does not match.
RULE MATCHED→PERSON NOTIFIED→RECORD KEPT
Simulated sequence. No notification is sent.
03 / WATCH FOR THIS
A search, once.
A rule, from now on.
Turn the moment you found into a condition to watch. Tune this synthetic example, then preview what reaches your team.
01 / THE CONDITIONPREVIEW
Notify me when a person enters the fence zone for more than 10 seconds, between 22:00 and 06:00.
Five conditions are included in this sample. Availability on your site is confirmed in a pilot.
3 matches in the synthetic event index.
02 / THE WATCH ZONESYNTHETIC
SCHEMATIC / 01
MATCHING MOMENTSSIMULATED SHIFT
- 2 people · fence zone · 43 s
- person · fence zone · 11 s
- person · fence zone · 26 s
Synthetic scene · illustrative overlay, not product output
03 / THE ACTIONSIMULATED
These are interface examples. Live integration status is pending verification.
SIMULATED · NO MESSAGE SENT
Watch rule matched
Inspect the draft payload
DRAFT v0 · An illustrative format for this demo.
{
"schema": "camza.rule.draft-v0",
"simulated": true,
"message_sent": false,
"condition": {
"subject": "person",
"zone": "fence",
"predicate": "present",
"dwell_seconds": 10,
"schedule": "night",
"cooldown_minutes": 5,
"zone_x": 0.1,
"zone_width": 0.8
},
"destination": "slack"
}Different questions. The same cameras.
Four teams.
One frame.
A fence line to one team. A missed handoff to another. Start with the question your team needs answered.
01 / SECURITY
Every alert, with a reason.
Explore an after-hours fence event, inspect why it matched, and follow the proposed response.
Explore security02 / OPERATIONS
See where work gets stuck.
Explore dock dwell, open doors, and the handoffs that need someone’s attention.
Explore operations03 / QUALITY
Check the step. Keep the record.
Explore visible process checks, from an unlabeled pallet to a missed sequence.
Explore quality04 / SAFETY + MORE
Make the near miss visible.
Explore forklift and pedestrian zones, with context for a person to review.
Explore safety + moreScenarios describe evaluation ideas. Detection availability is confirmed for each deployment.
Your site. Your boundary.
Know what leaves
the building.
Before you connect a camera, understand where processing happens, what crosses your network, and who can access it.
Architecture examples below. Camza’s available modes and hardware requirements are awaiting confirmation.
Read the trust centerTO CONFIRMDeployment · retention · identity policy · offline behavior
Show the work
Clarity is part of the product.
A useful demonstration should tell you
exactly what it proves—and what it doesn’t.
01 / THE DEMONSTRATIONILLUSTRATIVE
SCHEMATIC / 01
The scene is synthetic. The distinction matters.
These drawings explain an interaction. They are not customer footage, product search output, or evidence of detection accuracy.
How to evaluate a real deployment02 / CAMERA CHECKBENCH PENDING
Start with the camera you have.
Find a vendor to begin a compatibility conversation. A listing means there is something to evaluate—not that a model has passed a Camza test.
Model, firmware, and stream settings all matter.
Published bench resultsNot yet published
Timing measurementsNot yet published
Open the compatibility log Know the limits
A clear boundary.
A better conversation.
- 01
A visual aid for human review.
Not a safety-rated interlock. - 02
Visible process checks.
Not micron-level inspection. - 03
An evaluation on your site.
No unsupported accuracy claim.
The people behind the frame
Building with the
questions that matter.
Camza.ai is being built around a simple idea: the cameras already in a building should help the people who work there understand what happened—and decide what to do next.
01What can I try on this website?
You can search a small synthetic event index, inspect matching events, and simulate a rule and action. The scene and overlays are illustrative. This website does not connect to your cameras or run Camza’s production models.
02Will Camza work with my existing cameras?
The proposed integration path uses ONVIF or RTSP. Support for your model, firmware, stream settings, and deployment must be checked. Send us those details for a compatibility conversation; a protocol name alone does not establish tested support.
03Where does video processing happen?
Available deployment modes and any hardware requirements are awaiting product confirmation. Before a pilot, ask for a written description of where processing runs, what leaves your network, and how long data is retained.
04Does Camza use facial recognition?
The product’s identity-features policy is awaiting confirmation. This illustrative website demo uses geometric scene objects and creates no face templates or personal identifiers.
05What does a pilot cost?
Pilot pricing, duration, and terms are not published yet. Share your camera setup and the workflow you want to evaluate so the team can discuss a scoped proposal before you commit.
Your site. Your next question.
Now ask
your cameras.
Start with a camera, a place, and one thing you want to know. We’ll use that to begin the conversation.
- 01 Share your camera setup.
- 02 Define a workflow to evaluate.
- 03 Agree scope and terms before a pilot.