TL;DR: An installer who wants to offer CCTV monitoring in Australia has two delivery models to choose between. The first is a graded control room, built or partnered with, where licensed operators verify signals and action a response plan that can include guard dispatch. The second is an AI detection and notification layer over the cameras you already install: our team configures detection profiles for each site, the software screens camera events, and verified events notify everyone who needs to know, with the evidence attached. The second is not a monitoring service, and plenty of installers sell both. This guide covers what each path requires, what each one does and does not commit you to, and how to choose per site. You may need a state security licence depending on the activities you perform. This is general information, not legal advice.
Ongoing services are what turn project income into monthly recurring revenue, which is why nearly every installer looks at monitoring eventually. The question is not whether to offer an ongoing service but how to deliver it. This guide is about the delivery model. For the pricing structure and the revenue arithmetic, see how CCTV installers build recurring revenue in 2026, and for the buyer-side comparison of the models, see back to base monitoring vs AI CCTV detection.
Before you start: the compliance picture
Australian security licensing is regulated at the state and territory level, and the rules differ depending on what you actually do. Both paths sit inside that framework. A graded control room performs a licensable activity and is certified to standards for it. A software detection layer screens and verifies camera events; it does not perform graded operator dispatch and it does not remove any licence you would otherwise need. Where an incident requires physical attendance, that comes from appropriately licensed responders: your own keyholders, a patrol company, or a graded alarm receiving centre you escalate to.
Two practical consequences. Confirm your state licensing requirements for the activities you intend to perform before you sell anything. And be precise with customers about the difference between automated notification and licensed response services, because that distinction is what they are actually choosing between.
Path 1: a graded monitoring centre
The established route. Signals from the site reach a control room graded under standards such as AS 2201.2:2022, where a monitoring operator verifies them and works the response plan. Installers reach this path in one of two ways: by building a centre, which very few do, or by partnering with an existing one under a wholesale agreement, which is how most of the market operates.
What the graded path requires
- Continuous staffing. Around-the-clock rosters, trained and licensed operators, and cover for leave and turnover.
- Certified infrastructure. Redundant power and communications, physical security of the control room, and a monitored signalling path to every site.
- Audited process. Documented procedures, retained records and periodic audit against the standard.
- A dispatch relationship. Patrol contractors or in-house guards who actually attend, with agreed response times.
- Capital and time. Building a centre is a capital project measured in years. Partnering with one is a commercial agreement measured in weeks.
When the graded path is the right answer
Whenever a contract, tender, lease or insurance schedule names graded monitoring, this path is the answer and the decision is already made for you. It is also the right call where a customer needs an agreed physical response service, where police response may form part of the plan, and where the site is a full alarm system with panels, sensors and duress rather than a camera network. A graded centre is a serious operational commitment and it is what customers with those requirements are correctly buying.
Path 2: an AI detection and notification layer
The newer route. Software sits over the cameras already on site, checks camera events against detection profiles configured by our team for each site, and notifies everyone who needs to know when it verifies a person or vehicle. There are no human operators on the software vendor's side, which is what keeps the cost structure flat and what defines the limits of what it can promise.
What the software path requires
- Supported cameras or an NVR. Vael works with most IP cameras and NVRs after a compatibility check. Common brands include Hikvision, Dahua, Axis, Bosch, Hanwha Vision, Uniview, Honeywell, Avigilon and Pelco. No proprietary hardware swap is needed.
- A connection from the site. A reliable internet connection at the site, confirmed during onboarding.
- Detection profiles and coverage windows. Our team configures detection profiles for each site and camera, including stricter settings where you want fewer, stronger alerts, and the hours each camera is covered.
- A written escalation path. Who is notified, in what order, and when it rolls to a patrol company or a graded centre.
- A licensing check. Operating an automated alerting service can itself be a licensable security activity in some states and territories.
What the software layer does not include
Being explicit here protects the sale. The layer does not include human operators, graded operator dispatch, or any guaranteed physical attendance. Notifications are automated and go to the people you nominate. If somebody needs to turn up, that comes from your escalation path. Selling it as anything more creates a gap between what the customer thinks they bought and what happens at three in the morning.
When the software path is the right answer
It fits unattended yards and depots that have cameras and no panel, sites where false alarm volume is the actual cost problem, and customers who want to know promptly that a person is on site out of hours. It also fits in front of a graded centre, screening events so that operators see fewer routine ones. Detection is configured around what each site needs caught, such as perimeter integrity, gates and depots, yards and plant, and rubbish dumping and fire.
Comparing the two paths
| Graded monitoring centre | AI detection and notification layer | |
|---|---|---|
| Who verifies | Licensed human operators | Software, against detection profiles configured for each site |
| Physical response | Contracted patrol or guard attendance | Your escalation path, outside the software |
| Standing cost | Rosters, certified infrastructure, audit | A subscription quoted per site |
| Time to offer it | Weeks to partner, years to build | Days, on cameras already installed |
| Cost of a false alarm | Operator time, and attendance billed per event | Mostly screened out upstream |
| Meets a "graded monitoring" contract clause | Yes | No, use it alongside a graded centre |
| Best fit | Panel-based sites and requirements for graded monitoring; physical response contracted separately | Unattended yards and depots with existing cameras |
Setting up the software layer
If the software path is the one you are adding, the sequence is short.
- Define the service and the target sites. Construction, plant and equipment yards, contractor depots, warehousing, retail. Match the model to the risk at each one, and write down what "a response" means for every tier you sell.
- Connect the cameras. Confirm the camera models and network with Vael, and our team handles the connection during onboarding. You work with the cameras already on site or the ones you are installing.
- Configure detection. Our team configures detection profiles for each site, with stricter settings where you want fewer, stronger alerts, and coverage windows per site.
- Agree who is notified. Decide who needs to know about which events, and when. Vael notifies everyone who needs to know, with the evidence attached, subject to system availability.
- Define escalation. Name who is notified, in what order, and when it rolls to a patrol company or a graded centre. This is where licensed responders take over.
- Price it. Partner terms are agreed in your quote, and you set the price to your customer, keeping the spread as recurring revenue. Notifications go out under your brand. The arithmetic is worked through in the recurring revenue guide.
What Vael handles and what you handle
| Vael AI provides | You provide |
|---|---|
| Detection profiles configured by our team for each site | Camera supply and installation |
| Screening that removes most false triggers | The customer relationship |
| Notifications to everyone who needs to know, with the evidence attached | Escalation path (keyholder, patrol, or graded centre) |
| Australian-only processing for sites that need it | Pricing to your customer and contracts |
| Notifications under your brand | State licensing compliance |
| Verified events handed to a monitoring station by notification, where one is used | Your brand and go-to-market |
Choosing between them, site by site
Treat this as a decision per site rather than one you make once for the whole business. The sequence is the same each time.
- Read the contract and the insurance schedule first. If either names graded monitoring, the graded path is the answer and everything else is designed around it.
- Ask what has to happen at 2am. If the answer is that somebody must attend within a set time, you need a dispatch relationship. If the answer is that the right person must know promptly, verified notification does the job.
- Look at where the false alarms are landing. A site generating repeat attendances for wildlife or weather is a candidate for verification in front of whatever it already uses.
- Check what the site actually has. Panels and sensors point to the graded path. Cameras and no panel point to the software path.
Common mistakes to avoid
- Overpromising guaranteed dispatch. Automated notification is a different commitment from graded operator response. Describe the service and any attendance commitment separately. Centre grading alone does not guarantee a patrol arrival.
- Skipping the escalation path. A verified intrusion needs a defined next step. Decide it before you sell, not after the first incident.
- Treating the service as an upsell. It is the recurring revenue engine. Quote it as a standard line on every job.
- Talking down the graded path. Plenty of your customers need it, and the ones who do will notice if you argue against what their insurer requires.
- Assuming where data is processed. Where a customer requires processing to stay in Australia, raise it up front: Australian-only processing is available for sites that need it.
Related guides: back to base monitoring vs AI CCTV detection, recurring revenue for CCTV installers and how to integrate AI CCTV with your monitoring system. Installers can find partner details on the partners page.
Frequently asked questions
How can an installer offer CCTV monitoring in Australia?
There are two delivery models. You can build or partner with a graded control room, where licensed operators receive signals and action a response plan that can include guard dispatch. Or you can add an AI detection and notification layer to the cameras you already install, where software screens camera events and notifies the people you nominate about verified ones. Many installers use both, matched to each site. Australian security licensing is set state by state, so confirm the requirements for the activities you perform.
What does it take to run a graded monitoring centre?
A graded centre commits to continuous staffing, redundant power and communications, physical security of the control room, audited procedures and retained records, certified under standards such as AS 2201.2:2022. That means capital, around-the-clock rosters and ongoing audit. Most installers reach a graded response by partnering with an existing centre under a wholesale agreement rather than building one.
What do I need to offer AI camera verification?
Supported IP cameras or an NVR, a reliable internet connection at the site, a written escalation path for verified events, and a check of your state licensing requirements. Our team configures detection profiles for each site. Vael supplies detection and notification, with notifications under your brand; you supply the cameras and the customer relationship.
Which cameras does Vael AI support?
Vael works with most IP cameras and NVRs after a compatibility check. Common brands include Hikvision, Dahua, Axis, Bosch, Hanwha Vision, Uniview, Honeywell, Avigilon and Pelco.
Does Vael AI have human operators watching cameras?
No. Vael has no human operators watching cameras. Software checks camera events and notifies the people you nominate when it verifies a person or vehicle. Where an incident needs somebody to attend, that comes from your escalation path: a keyholder, a patrol company, or a graded monitoring centre.
How quickly does Vael notify after a detection?
Notifications are automated, so a verified event does not wait in an operator queue; delivery is subject to network conditions and system availability. Because Vael screens out most false triggers, the notifications people receive are the ones worth acting on.
Where is the data processed and stored?
Processing location depends on the configuration agreed for the site. Australian-only processing is available for sites that need it; confirm the data flow during onboarding.
Ready to add an ongoing service to the installs you are already doing? Book a free Detection Brief: our team will review a customer site with you, the cameras on it and what needs catching, and show you how the service would run.