Docs / CAMZA.AI
Start small. Write down what good looks like.
A useful evaluation starts with a visible event and a person who can review it. Gather a camera inventory, select representative examples and define the action the team would take. Before connecting any stream, agree scope, data handling and acceptance criteria so the result can support an informed decision.
UPDATED
1. Prepare the inventory
- Camera and recorder models, firmware and stream settings
- Site owner, network owner and authorized technical contact
- One or two specific events, plus normal activity that looks similar
2. Agree the evaluation
Write down what a reviewer will label as relevant, what counts as a miss and how nuisance alerts are measured. Cover ordinary shifts and difficult conditions, not only selected positive examples.
3. Confirm access and data handling
Confirm the supported deployment and approved stream access. Agree processing location, permissions, retained data and deletion before supplying credentials or recordings.
4. Review a complete result
Review compatibility, missed events, false alerts, timing and operational usefulness together. Keep the written limitations alongside any decision to expand.
A few useful questions.
Can I try this on my own cameras?
Start with a compatibility request. Share camera models, firmware and the event you want to find. An evaluation needs an agreed scope before any camera access is arranged.
Is the website demonstration a product benchmark?
No. The sample demonstration uses illustrative scenes and predefined events. It does not measure accuracy, response time or compatibility on your cameras.
What should we agree before a pilot?
Agree which streams are in scope, who can access the data, where processing runs, retention and deletion, expected outcomes, and the person responsible for reviewing results.
YOUR CAMERAS. YOUR CONTEXT.
Start with one
useful question.
A camera inventory. An event to find.
A clear next step for your team.