What Rhombus' own documentation says it does not do, or only does under a particular license, written for IT and security teams running due diligence. Every constraint carries its documentation, its operational impact, and its workaround.
Every constraint below comes from Rhombus' own current product, pricing and support documentation, checked on August 17, 2026. Where Rhombus documents nothing, this page says so rather than guessing, because an absence in a document is a question to ask rather than a finding to claim. Spot AI sells a competing platform, so nothing here rests on an anonymous source or an aggregated user rating, and this page corrects two things Spot AI has itself published about Rhombus. We wrote that its accepted protocols were not publicly specified: Rhombus support documentation states that Relay Core connects RTSP streaming cameras, with ONVIF used where the camera supports it. And we named the N100 appliance as the route for third-party cameras: Relay Lite is published as a second route that needs no appliance at all.
The commercial side of this platform is documented in unusual detail. The detection side, and what happens after a detection, is where the pages go quiet.
A constraint list is only useful next to an honest account of the product.
Camera MSRPs run from the R120 Mini Dome at $399 through the R200 at $599 and the R410 Dome and R360S Fisheye at $1,499 each to the R600 Multisensor at $3,299, with per-camera licenses from $149 for Professional up to $649 for Enterprise and terms of 1, 3, 5 and 10 years beside them. Days of storage are published per model on default settings, alongside 10-year camera warranties.
Dome, fisheye, bullet and multisensor cameras, door controllers, readers and intercoms, plus audio, environmental, motion, entry and multipurpose panic sensors, with alarm monitoring described as TMA 5-diamond certified live agent verification and dispatch. Rhombus describes the architecture as a cloud-edge system that lets a site scale infinitely, operate offline and minimize latency.
A 100% open API and more than 50 integrations across access control, identity, alarm and communication systems, with documentation that is not behind a partner agreement. The compliance posture is stated up front as SOC 2, NDAA, GDPR and TAA on the product pages rather than produced halfway through a security review, which shortens the part of an evaluation that usually drags.
Each one is a consequence of how the platform is designed rather than a defect. What matters is whether it collides with your starting point.
Rhombus publishes two routes for cameras it did not sell you. Relay Core is the N100 appliance, listed on the pricing page at $2,999, and Rhombus support documentation states it connects RTSP streaming cameras, with ONVIF used where the camera supports it. Relay Lite is published as the option with no extra hardware, and it ties a third-party stream to a Rhombus camera.
A 120-camera estate across six sites with no Rhombus hardware yet is buying hardware in order to reuse hardware, either an N100 per site at the published figure or enough Rhombus cameras to carry the Relay Lite streams. That spend lands before any AI value arrives, and it recurs as sites are added, which is the same shape as any bridged architecture rather than something unique to Rhombus.
Count third-party streams per site rather than across the estate, because that count is what decides between an appliance and Relay Lite. Phase site by site, put the N100 figure into a three-year model at the published term lengths, and check whether a site being newly fitted is cheaper native than bridged.
Rhombus publishes a per-camera Professional license from $149 which it states excludes AI features and cloud archiving, and a per-camera Enterprise license up to $649 which adds them. Terms of 1, 3, 5 and 10 years are published against both.
A fleet quoted entirely at the entry tier is a fleet quoted without the analytics, and the gap between the two published figures is large enough to reshape a business case. On a 200-camera estate the decision is not really per camera either, because the cameras that need detection tend to be the ones covering doors, tills and yards rather than corridors.
Split the fleet before asking for a quote: mark which cameras genuinely need detection and which only need recording, then price those groups separately and ask whether tiers can be mixed within one site. Because the term lengths are published, model three years rather than one so the archiving decision is priced across the whole contract.
Actionable AI insights and AI-powered search are the public surface. No named detection list, no count of detections and no path for building a custom one appears on the product pages, and the license pages state which tier carries AI features rather than what those features recognize. The documentation covers where the AI sits commercially, not what it looks for.
That is an absence of published detail rather than evidence of a weak model, and it still shapes an evaluation: two vendors cannot be compared on detections when one of them has not named any. A safety lead asking whether forklift proximity or a blocked exit is covered has nowhere to read the answer, so the shortlist stalls until a call happens.
Ask for the detection list in writing before the shortlist closes, and ask specifically which detections are configurable and which are fixed. Then run a pilot scoped to the three events you actually care about, on your own cameras and your own lighting, rather than accepting a demo reel as the answer.
Which AI features run on a Relay stream rather than on a Rhombus camera is not publicly specified. Rhombus does state one thing plainly about third-party hardware: users will need to manage updates to their non-Rhombus cameras. So firmware on the reused fleet stays with the customer, and the analytics question on those streams is unanswered in public.
On a mixed estate this is the question that decides whether the older cameras are participating or simply visible. It also creates unplanned work: a fleet nobody has touched in five years needs a firmware program owned by somebody, with a maintenance window per site, and that job does not appear on any quote.
Ask feature by feature which analytics run on a Relay stream, and put the answer in the evaluation record rather than in a memory of a call. Pilot on the oldest cameras rather than the newest, and name the firmware owner and the maintenance window in the runbook before the rollout is scheduled.
Audio sensors are sold as a product and alarm monitoring is published as TMA 5-diamond certified live agent verification and dispatch. What is not published is the automated behavior: no documented sequence describes what the platform does with a speaker when a detection fires and nobody is watching. The documentation covers the devices and the monitoring service, not the automation between them.
For a yard, a lot or a distribution site where the useful outcome is that somebody leaves rather than that the event is recorded, that distinction decides the whole business case. A monitored response through live agents is a real answer, and it is a recurring service cost rather than an automation, so the two options should be priced as the different things they are.
Ask for the sequence rather than the hardware list: what fires, in what order, with what human in the loop, and how quickly. If the intended answer is the monitored alarm service, get that priced per site alongside the licenses, and compare it against platforms that automate the same response through speakers already installed.
The same five constraints in one view, sized to paste into an evaluation document.
Swipe the table sideways to see every column.
Rhombus data comes from Rhombus' own product, pricing, Relay and support documentation, checked on August 17, 2026. Gaps are marked as not publicly specified.
If you are fitting out a site rather than bridging into one, most of the constraints above stop applying, because the Relay question disappears and the license tier is a straightforward choice on new hardware. A team that wants cameras, doors, sensors and a monitored alarm response from one vendor, with MSRPs, license tiers, contract terms and days of storage all published before a call, is buying an unusually transparent project.
Spot AI takes the opposite architectural route, which is why its constraint list looks different. It is camera agnostic by design: any ONVIF or RTSP IP camera works at full functionality with no bridging appliance in the path, and legacy analog cameras come in through the Intelligent Video Recorder, so a mixed estate does not split into a native half and a relayed half whose capabilities differ.
The detections are named and they ship with the platform rather than sitting behind a tier. 15+ pre-trained Video AI Agents cover vehicle break-in, fire, cash register theft, after-hours intrusion, personal protective equipment, forklift near-miss, falls and crowding in hazard zones, and Iris builds anything else in natural conversation in about eight minutes. Full-resolution video stays on the IVR in the building with only event metadata crossing the network, and an event is answered on site through talk down, strobes and horns on standard speakers rather than through a monitoring subscription.
The useful question is not which platform has fewer constraints, but whether you are buying the cameras in the same project or bridging into the ones already on the wall.
None of that makes Spot AI the right answer for every buyer. Rhombus' catalog runs wider than video: door controllers, readers, intercoms, five sensor types and a TMA 5-diamond monitored alarm service are one relationship, where Spot AI is a video AI platform and access control and sensors arrive through integrations. Camera MSRPs run from $399 for the R120 Mini Dome to $3,299 for the R600 Multisensor, with the N100 Relay Core at $2,999 and per-camera licenses from $149 to $649, so a Rhombus estate can be costed early. Spot AI states camera compatibility by protocol rather than by manufacturer, which is less specific than a published hardware list. A constraint list earns its keep by lining each platform's shape up against your starting point.
A live pilot on your cameras answers in a week what a spec sheet cannot.
Customer-reported outcomes from named Spot AI customers.
Cambridge City cut footage search from two hours to 30 seconds after consolidating seven municipal locations on one platform.
YMCA of Greater Richmond deployed 17 locations in two weeks with standardized 30-day retention and single sign-on through Active Directory.
Staccato went from first conversation to a live deployment across an 800-acre campus in seven weeks, with protective equipment rules set by zone.
"With Spot AI, we were able to standardize video surveillance across existing and newly acquired assets, regardless of what cameras were already installed."
Five, all documented. Existing cameras arrive through Relay Core, the N100 appliance published at $2,999, or through Relay Lite tied to a Rhombus camera. AI features and cloud archiving sit in the Enterprise license published up to $649 rather than the Professional license from $149. What the AI detects is not publicly specified. Which AI features run on a Relay stream is not specified either, and Rhombus states that users manage updates to their non-Rhombus cameras. And no automated response sequence is published.
Yes, and the correction is worth making plainly: Rhombus is not proprietary-cameras-only. It publishes two routes, Relay Core and Relay Lite, and its own wording is that they let you connect existing ONVIF and RTSP cameras into the Rhombus console without ripping them off the wall. The constraints are the ones around that route: the N100 appliance is published at $2,999, Relay Lite requires a Rhombus camera to carry the stream, and firmware on the reused cameras stays with the customer.
No. Rhombus publishes its per-camera Professional license from $149 as excluding AI features and cloud archiving, with the Enterprise license up to $649 adding them, on terms of 1, 3, 5 or 10 years. That makes the license tier, not the camera count, the line that decides whether a site has analytics, so it is worth splitting the fleet into cameras that need detection and cameras that only need recording before asking for a quote.
Not publicly specified, and that is the finding rather than a criticism. The published surface is actionable AI insights and AI-powered search, with no named detection list, no count and no documented path for a custom detection, and the license pages describe which tier carries AI rather than what it recognizes. Ask for the detection list in writing, ask which detections are configurable, and scope a pilot to the three events that matter on your own sites.
It depends on whether the cameras are already on the wall. If the project buys the hardware too, Rhombus prices that project in public. If the estate is a decade of mixed manufacturers that has to stay in place, a camera-agnostic platform such as Spot AI fits: any ONVIF or RTSP camera works at full functionality with no bridging appliance, legacy analog comes in through the Intelligent Video Recorder, and 15+ pre-trained Video AI Agents run across the whole fleet rather than a licensed subset.