Comparisons
License plate recognition
CloudRunner vs Flock Safety: Who Controls Your License Plate Data
Both systems read license plates. The difference is who controls the data. With the platform we deploy, your agency owns the reads, sets the retention, imports its own hotlists, and decides one partner at a time who can see what, with the right to revoke. Nothing is shared by default.
Read the comparisonNational integrator comparison
Confluence Security vs Convergint: An Honest Comparison
If you are rolling out hundreds of sites across many states, a large national integrator is the better choice and we will say so first. If you have one to forty buildings in Colorado, Wyoming, Utah or New Mexico and you want the same person answering the phone in year five, that is the work we do.
Read the comparisonNational integrator comparison
Confluence Security vs ADT Commercial and Everon: An Honest Comparison
Everon, formerly ADT Commercial, is a large and capable national integrator. The documented friction in its public complaint record clusters around contract structure rather than technical competence, which means the questions that protect you are contract questions. This page gives you all eight of them.
Read the comparisonArchitecture decision
Cloud vs On-Premises Video: How to Choose
Cloud video removes the server, the storage array, the software licensing stack and the port forwarding that creates most of the risk in traditional recorder deployments. On-premises keeps recurring cost lower at large camera counts, keeps data in the building and does not depend on upstream bandwidth. Most real answers are hybrid.
Read the comparisonArchitecture decision
Open Architecture vs Proprietary Security Systems
Open architecture means the software layer supports hardware from many manufacturers, so you can change cameras without changing platforms and change platforms without changing cameras. Proprietary welds the two together, which puts the leverage with the vendor at every renewal. The real question is not what happens on install day. It is what happens in year seven.
Read the comparisonUpgrade planning
Analog vs IP Cameras and How to Upgrade Without Replacing Everything
Analog cameras can absolutely be integrated onto a modern platform. Doing it preserves the most expensive asset in an old system, which is the coax already in the walls. Encoders land around 55 to 100 dollars per channel at street pricing, and the usual right answer is a hybrid: keep the low-priority analog views, replace the identification-critical ones, and run all of them on one platform.
Read the comparisonTrust and privacy
Existing camera assessment
Usually yes. If your cameras are IP and were made after about 2012, they most likely support ONVIF Profile S and will work with a modern platform. If they are older, they may still work through a native manufacturer driver. If they are analog, we can bring them in through an encoder for roughly 55 to 100 dollars per channel without pulling new cable. The real question is not whether they will connect. It is whether they still give you enough pixels on target to identify a person, and whether they can still receive security firmware updates.
Read Existing camera assessmentPrivacy and data ethics
You are the data controller and we are not. You own the video, you set the retention, you decide who has access, and any sharing is an explicit act you can revoke. Our job is to design a system that can prove all of that with documents rather than assurances.
Read Privacy and data ethicsWhy Confluence Security
Thirty years in the trade, deep expertise in the platform we deploy, and the same people designing, installing and servicing your system. We are vendor neutral, we work with what you already own, and we hand you the documentation and the credentials so you are never locked in.
Read Why Confluence SecuritySupport, warranty and SLA
Our service covers design, installation, configuration, documentation and on-site response. The platform manufacturer covers software releases, support cases and cloud availability under its own published programs. We keep that boundary explicit, because the most common support failure in this industry is a customer who assumed one party covered something the other party did.
Read Support, warranty and SLA