Quick answer: The current CASE catalog describes CASE Cloud for remote NVR configuration and troubleshooting. That is a different job from customer viewing, cloud recording or off-site backup. Confirm the exact recorder, firmware and service scope before relying on remote configuration for a project.
On this page
What is actually described for CASE Cloud?
The catalog’s software pages describe remote access to NVR configuration, P2P connectivity without port forwarding and no additional service fees for that described function. They print the service name cloud.case.cam. These are the documented scope statements, not proof that every recorder, region or requested maintenance task is supported.
Ask Anabon technical support to confirm current access and eligibility for the complete SKU and installed firmware. Record the service/version context and test the required functions on an authorized device. Do not turn a printed software description into a promise of permanent availability or unlimited features.
| Requirement | What to confirm |
|---|---|
| Remote recorder settings | CASE Cloud model/firmware eligibility and the actual settings reachable through the approved service. |
| Phone viewing and playback | CASE Connect device/software support, account arrangement and approved access method. |
| Desktop monitoring | CASE Station version, supported devices and required layouts/functions. |
| Video stored away from site | A separately documented storage, retention, security and recovery design. The CASE Cloud name does not establish it. |
Does the word cloud mean video is backed up?
No. A path to the recorder’s settings does not establish that recordings are copied off site. Identify every actual recording destination and who maintains it. If a customer needs off-site video, retention guarantees or recovery after the recorder is stolen, treat those as separate design requirements.
Do not claim that no data passes through a service, that every session is direct, or that video is never relayed without documented data-flow information. Remote configuration, connection brokering, live viewing and recording storage are distinct questions. The cloud and NVR storage guide helps frame the discussion.
How does it differ from CASE Connect and CASE Station?
CASE Connect is the primary CASE camera-control software direction. Android is available and iOS is forthcoming. A web version exists, but an approved public URL is not yet available. Contact Anabon to confirm the current supported functions and access arrangement for the actual project.
CASE Station is separately described for desktop monitoring, playback and export. The catalog also describes a local discovery/configuration utility. None of those names establishes feature-for-feature equivalence with CASE Cloud.
Use CASE Connect handover guidance for customer access and the deployment-tool guide for local setup. Keep the proposal specific about which tool performs which job.
Plan an authorized remote service session
- Confirm the partner and customer have authorized access, its purpose and the maintenance window.
- Record the exact device/version, symptom and required change before connecting.
- Use the approved account and access method; avoid shared or unnecessary administrator access.
- Preserve relevant logs/settings before a change where supported and appropriate.
- Make only the agreed changes and verify their result, including required recording and access functions.
- Record who attended, what changed, the result and any action still needing a visit.
Anabon supports the installer, integrator or approved business account behind the scenes. The partner remains the customer’s service contact. Arrange third-party support access through that approved relationship rather than giving a customer an undocumented route to somebody else’s credentials.
Know when a site visit is still needed
A remote service depends on the recorder, network, power and required service being reachable. It cannot replace a failed cable, reconnect a plug or resolve every recovery situation. A camera that appears offline may have a power fault that no configuration session can fix.
Do not assume remote firmware updating or recovery is available just because settings can be opened. Use the firmware change procedure and confirm its supported remote/on-site steps before the window.
Leave a scope statement the next technician can use
Record the approved remote functions, eligible models/versions, account owner, revocation method, customer approval and service dependencies. Keep passwords and pairing tokens in the approved secure system, not in this statement.
Test removal of temporary access where supported. A login menu or a P2P label does not prove revocation across linked sessions. Keep the scope with the handover record and the recorder hardening baseline.
FAQ
Is CASE Cloud a cloud-recording subscription?
That is not the function established by the catalog. Request a separate written solution if off-site recording or VSaaS is required.
Does every CASE NVR support it?
The catalog description is not a complete eligibility list. Confirm the exact model, firmware and current service requirements.
Can it replace every service visit?
No. It may help with supported configuration tasks, but physical faults and unsupported recovery work still require the appropriate on-site process.
For a project scope, send the full SKU, firmware, required tasks and customer IT restrictions to Anabon technical support. Obtain approved software information through the Download Center.
References
Product descriptions were checked against the current CASE Catalog 2027 Q1. Confirm the exact model/revision and current software scope through the Anabon Download Center or technical support before a project commitment.
