Not a canned dataset and not a recorded walkthrough. We run the platform against your footage and your use cases, because that is the only comparison that survives procurement scrutiny.
Prefer email? [email protected] · +1 (301) 392-7621
What Happens Next
Full delivery runs six to twelve months from first qualified conversation to steady-state operations for the IREX platform, and three to nine for Sover, with the procurement route rather than engineering setting the pace. The first three steps are the ones that involve you before any money moves.
We walk the platform through your use cases with your technical and executive stakeholders, and establish the shape of the program: sovereignty posture, budget order of magnitude, and decision timeline.
What you operate, what the network can carry, which integrations matter, and which compliance obligations bind you. Output is a short opportunity brief rather than a proposal nobody asked for.
One site, three to five use cases, six to twelve weeks, and two or three measurable success criteria signed off before it starts. Accuracy is benchmarked on your own cameras, and the measured numbers go into the contract.
Before You Book
None of these are easier to hear later, and a demo booked on a misunderstanding wastes your afternoon as well as ours.
The platform is licensed per camera and Sover per user, but a license figure in isolation is not the number your budget turns on. We quote the whole system with a three-year total cost of ownership against your current stack. How to Buy explains the four models.
IREX publishes no per-module accuracy numbers, because a result from another city’s cameras tells you very little about yours. We measure it on your feeds during the pilot, against criteria agreed in writing, and put the measured numbers in the contract.
The commercial US SaaS runs on ISO 27001-certified colocation in Texas that is not a FedRAMP-authorized cloud. IrexAI is aligned with ISO/IEC 27001:2022 and holds no certification of its own.
See the Full Security Posture →Most will connect: any camera that supports ONVIF or streams RTSP with H.264 or H.265 on a static IP. Whether it meets the resolution a given module needs is the real question, and traffic enforcement is stricter still. A site survey settles it before a statement of work, never during build.
Pilot Prerequisites
Cloud hosting is the default for a pilot, because it keeps the cost and the lead time down: no server hardware to procure, a faster deployment, and easier troubleshooting while it runs. An on-premises pilot on your own hardware is the alternative where the video cannot leave the site. Either way, four things set the start date.
One saved frame per camera, straight from the system you run today. We use it to verify the camera position and the video quality against the modules you want to test, before anyone touches a configuration.
RTSP links with login credentials and reachable IP addresses are the quickest route. Where the cameras sit on a private network, an IPsec site-to-site VPN from your gateway carries the same streams encrypted instead. If the cameras already feed a video management system, their second stream can be used for the pilot.
On IREX cloud hosting the site needs roughly 5 Mbps of uplink per camera, so about 50 Mbps for ten cameras. An on-premises pilot needs no uplink at all, because the video never leaves your network.
One person who can answer the network and camera questions and make the configuration changes. Where a security review is involved, preparation can run past a month; a team that already holds the answers works through this list in a couple of days.
Keep Reading
The platform, the analytics catalog, the industries IREX serves, the ethics framework, how to buy, published case studies, and the full documentation portal are all one click away.