WHERE IMMIX SLOWS YOU DOWN

Workflow software is only as good as the integration underneath.

Immix CS and GF do not record. They consolidate alarms, snapshots and video clips that come from the customer's existing VMS, NVR, camera, alarm panel and access-control kit. Every one of those connections is a separate integration that can age, break, or have to be propped up with brittle workarounds.

SMTP-image alerts are not real-time

A meaningful slice of supported recorders only push alarm + snapshot via SMTP email to a line-handler. Queue backs up, and the operator sees a stale JPEG thinking it is live. TetherX streams native video direct to cloud.

Integration breakage on firmware drift

Camera vendors push firmware; an Immix module that worked at sale time can degrade silently as the kit ages. The integrator finds out when an operator misses an event.

Old firmware is a security tradeoff

Adding a camera with ancient firmware to Immix means exposing a vulnerable device. TetherBox sits between the customer LAN and the Internet so ageing kit never has to be Internet-exposed.

Microsoft SQL Server licensing

Cloud Immix runs on MS SQL Server, flagged on Reddit as a non-trivial per-year cost on top of the Immix licence. TetherX is cloud-native, no SQL licence, no Windows Server, no per-station hardware.

Scale ceiling under alarm spikes

Long-time Immix administrators have described performance challenges at scale, including backend bottlenecks during alarm bursts even on dedicated server hardware. TetherX is horizontally scaled cloud - no per-station ceiling.

Hours-to-days site onboarding

New customer site means: connect each camera or VMS, configure SMTP routing, write SOPs, test escalations. TetherX is 1-click: TetherBox autodiscovers, account provisions, dashboard updates.

Sources: r/videosurveillance Central Station pricing (2023), IPVM Sureview Immix Alternative (Jan 2015).

IMMIX vs TETHERX

Different layers. Different scope.

Immix is workflow on top of someone else's VMS. TetherX is the VMS. When the customer does not need a UL-listed central station, TetherX replaces the whole stack.

Immix CS / GF

Does not record - relies on a third-party VMS, NVR or camera on every site

Many integrations use SMTP image push, not real-time video

Each integration is a separate maintenance burden, fragile to firmware drift

Cloud Immix requires Microsoft SQL Server licensing

Bare-metal server per station; alarm-spike bottlenecks under load

Hours-to-days site onboarding per new customer

No native edge buffering - if the Internet drops, the integration drops

TetherX

Native cloud recording for every camera on every site

Real-time event stream with verified video attached, no SMTP poll

One API to 17,000+ devices from 200+ manufacturers

No SQL Server, no Windows Server, no per-station hardware to maintain

Horizontally scaled cloud - no per-station ceiling

1-click site onboarding: TetherBox autodiscovers cameras, account provisions instantly

TetherBox edge buffer keeps recording if Internet drops

Coexists with Immix - clean events handed to Immix CS via the existing integration

TWO WAYS TO RUN TETHERX

Replace Immix, or feed it.

Run TetherX as the control room

Most "video monitoring" is not a UL-listed central station - it is an integrator watching their own customers' cameras after hours, verifying alarms, dispatching a keyholder or the police. TetherX does this end-to-end: pending events, monitoring strip, multi-operator handling, ARC performance reports, visual timeline. No Immix licence, no MS SQL, no station server.

See the control-room features

Or keep Immix and feed it cleaner video

If the central station is UL-listed or BS8418-certified and Immix is doing what it does best, TetherX sits underneath as the camera-and-recording layer. Immix gets a single tidy event with verified video attached over the existing TetherX-Immix integration. The brittle per-device SMTP integrations on the camera side go away.

See the Immix integration
FAQ

Questions before you replace - or supplement - Immix

It depends what the customer needs. If the operation is a UL-listed or BS8418 central station handling fire, intrusion and police-response alarms with full SOP escalation and multi-tenant SOC workflow, Immix CS or GF remain category leaders and TetherX is not pitching against that. If the operation is video monitoring, remote guarding, after-hours watching or video verification for an integrator that wants to run a control room themselves without becoming a UL central station, TetherX replaces Immix end-to-end at a fraction of the cost and complexity - see control rooms. The two also coexist: many integrators run TetherX as the camera-and-recording layer and feed clean, video-verified alarms into an existing Immix CS station.

Immix is workflow software. The actual video sits on whatever VMS, NVR or camera the customer already owns - and a meaningful slice of those integrations push alarm and snapshot data into Immix via SMTP email rather than a real-time stream. When the recorder firmware ages, the SMTP queue backs up or the network glitches, the Immix operator can be looking at a 5-minute-old JPEG thinking it is live. TetherX records every camera directly in the cloud (with TetherBox edge buffering when the Internet drops), so the operator always sees true near-real-time video with an audited timeline behind it.

Cloud Immix runs on Microsoft SQL Server, and integrators on Reddit consistently flag it as a meaningful per-year line item on top of the Immix licence - see the r/videosurveillance Central Station pricing thread. TetherX is cloud-native with no SQL Server licence, no Windows Server licence, and no per-station hardware to procure. Spin up, log in, start monitoring.

Immix integrates with 500+ third-party devices via vendor SDKs, ONVIF, dealer alarm protocols and SMTP line-handlers. The library is genuinely the broadest in monitoring-station software. The catch is that quality varies by module - some integrations are deep (PTZ, two-way audio, live playback), others are surface-level (snapshot pull only or SMTP-based). When a customer's recorder firmware is too old to update safely, exposing it to Immix is a security risk; not exposing it means the integration degrades. TetherX is one API connecting 17,000+ devices from 200+ manufacturers, with the TetherBox edge appliance acting as the security boundary so ageing kit on the customer LAN never has to be exposed to the Internet.

Immix site onboarding is hours-to-days of integration work per site: connect each camera or VMS, configure SMTP routing, build SOPs, test escalation. TetherX is one click: plug in a TetherBox, it autodiscovers the cameras on the LAN, the cloud account is provisioned per-site instantly, and the operator dashboard updates. Sites with cellular/4G/5G work the same way - no port forwarding, no static IPs, no working with the customer's IT team.

Yes - and this is the most common path for integrators that already run a UL or BS8418 central station. TetherX is one of the platforms listed on control rooms as natively compatible with Immix CS. TetherX records the video and pre-filters events, Immix gets a clean alarm with verified video attached, the operator workflow you already trained your team on stays the same. The brittle SMTP / per-device integrations on the camera side go away.

Long-time Immix administrators on the r/videosurveillance Central Station pricing thread (2023) have described performance challenges at large camera counts - backend bottlenecks during alarm bursts even on dedicated server hardware, limited reporting depth, and customisation hitting the ceiling of the built-in scripting layer. TetherX is cloud-native and horizontally scaled, so the platform grows with the customer base rather than requiring a per-station server upgrade cycle.

It is a recurring theme on IPVM and Reddit: experienced operators reach a point where Immix licensing plus per-feature customisation costs make in-house development look cheaper. TetherX is designed to give you both paths. Use the turnkey cloud platform as-is for the standard ARC/control rooms workflow, or extend it via the documented TetherX RESTful API to embed events into your own dashboard, build custom escalation logic, or feed downstream automation. No need to choose between "off-the-shelf with limits" and "build everything yourself".

Immix does not publish pricing - it is custom-quoted by station size, operator count and integration count. Reports from integrators managing Immix at multi-thousand-camera scale put the run-rate well into 5-6 figures per year, with Microsoft SQL Server licensing as a separate line item on top of the Immix licence. TetherX is a flat per-channel platform fee plus a per-camera cloud-recording tier, quoted through the integrator partner - no SQL licence, no per-station server, no per-integration build cost.

30 days through an integrator partner, TetherBox included, full platform access including the control rooms features. Extensions on request.
ALSO COMPARED

See TetherX against another VMS

Researching options? Read the side-by-side for each VMS the channel asks about most.

Eagle Eye

Premium pricing and fragmented apps vs simpler unified platform.

Genetec

Enterprise SMA renewals and certification gating vs channel-ready.

Rhombus

Rhombus cameras only vs 200+ manufacturers.

Verkada

Closed proprietary ecosystem vs open cameras, no lock-in.
See all comparisons

Still have questions about ARC integration, pricing or how TetherX handles UL-listed central-station workflow?

Read the full FAQ

Try TetherX free for 30 days

Run TetherX on a customer site next to an existing Immix station. TetherBox included, full platform access, extensions on request.

Start Free Trial

About this comparison. Information about other vendors is drawn from their public product pages, datasheets, integrator forums (Reddit, vendor user groups), public CVE databases (NVD, CISA) and customer conversations - accurate to the best of our knowledge as of 21 May 2026. Pricing, features, security posture and policies change. A vendor may have shipped a fix, dropped a price, added a region or changed an architecture since this page was last reviewed.

If you believe anything here is inaccurate or out of date, please contact us and we will review and correct it. Trademarks and product names belong to their respective owners and are referenced here for identification only.