|
Do I need a recorder on site?
|
They come out of the path. Camcloud's own NVR/DVR support article says the platform does not connect to a local DVR or NVR. Each camera has to reach AWS independently, so a retrofit behind an existing recorder needs rewiring. |
TetherX provides recording, viewing, search and monitoring through one system and one app. TetherBox records locally, with optional TetherX cloud recording, so no existing recorder or third-party cloud video service is required. It can also work alongside either where needed. |
|
Which devices you can connect
|
Any ONVIF or RTSP IP camera the installer can point at the cloud. Camera-agnostic, but camera-only. |
1,000+ integrations across 17,000+ device models, plus ONVIF and RTSP sources. Check model-specific recording, analytics and control support. |
|
What your operators see on one timeline
|
Cameras only. Alarm panels and access control are not in the same dashboard. |
Video, access control, intruder and automation. One operator, one timeline, one dashboard across all four. |
|
Who monitors your alarms
|
Not an ARC platform. Monitoring-station signalling and alarm-panel integration are absent, so a monitored site keeps a separate path. |
A control room is built in: operators act on each event in full context, while site users get critical alerts that sound through silent mode and pass on instructions. Choose professional monitoring through a TetherX control room, run your own, or keep an existing provider; Patriot-based centres such as IMS connect directly. |
|
What you can still do when the internet drops
|
Depends on the camera. A local cache on the camera SD card or an optional NAS keeps events through an outage. SD retention runs 24-48 hours at a usable bitrate, the NAS is an extra box to source, and neither is the default. |
Keeps recording and keeps working. Recording, doors and alarms run on the TetherBox on the local network, and the console picks up where it left off when the link returns. |
|
What gets sent over my internet connection?
|
The camera streams to AWS continuously, so the uplink carries the recording itself. A thin line caps how many cameras a site can run. |
Thumbnails, metadata and events, plus the clips an operator opens. Any camera your integrator sets to record to the cloud uploads on top of that; the rest record to the TetherBox alone, so a thin line still records every camera. |
|
Who you buy it from
|
Both. A mature reseller and white-label programme since 2013, alongside self-serve sign-up on camcloud.com. The installer can meet the platform's own funnel on the same job. |
Through the professional channel: an installer, security distributor or control room. |
|
What you actually pay for
|
Per camera per month, from a free home tier through roughly $6-10 for motion recording to around $15 for 30-day continuous 2MP. |
An annual platform subscription by channel count, from £100/site/year. TetherBox AI is included; additional modules and retention can cost extra. Cloud recording is optional; specialist analytics and professional monitoring are quoted separately. |
|
Where your recordings are stored
|
In AWS. Cloud is where recordings live rather than a copy of them, because there is no on-site recorder in the design. |
Choose local and cloud retention per camera: mostly local, mostly cloud, or a mix. TetherBox provides on-site recording. Cloud recording is optional per camera, in a UK, EU, US, Canadian, Indian or Australian region the customer picks. |