Checked August 1, 2026. “No subscription” is not a complete security design. It can describe one permanent service state, but it does not prove direct alarm sensing, local warning, useful camera evidence, remote access, outage behavior, support, or safe ownership transfer.
This checklist compares exact installed jobs. For current examples, use Abode’s Smart Security Kit and plans, Reolink’s security-camera systems, and Eufy’s security range. Save the exact model, storage, service, firmware, account, support, warranty, reset, transfer, and permanent unpaid-state record. Do not transfer a feature between products or generations.
Start with the permanent no-subscription state
| Job | Exact record | Pass evidence |
|---|---|---|
| Detect an opening | Direct sensor, zone name, mode, delay, supervision, battery, tamper state, and history | Twenty cycles with no miss, duplicate, or wrong zone |
| Warn locally | Hub or siren, placement, audibility, duration, quiet rule, accessibility, and battery path | Approved local test heard in every intended area |
| Notify remotely | Internet or cellular route, app, recipient, delay, stale state, queued event, and service requirement | Normal and disconnected tests show honest state |
| Record evidence | Camera, view, power, network, storage, schedule, detection, recording start, clock, retention, playback, and export | Day and low-light clips open on a second device |
| Respond | Self-monitoring owner, unavailable-owner route, neighbor or keyholder, monitoring service if any, permit, and escalation rule | Tabletop incident completed without the primary phone |
| End every optional service | Local sensing, siren, app, alerts, camera recording, local playback, export, users, support, updates, transfer, reset, and deletion | Dated ended-service state is acceptable before purchase |
Keep alarm, camera, and smart-home evidence separate
A direct contact sensor can prove that its protected opening changed state. A motion sensor can report activity in its coverage area. A camera can record a lawful view. A lock can report or control one access point. A smart-home routine can combine states. None automatically proves the others.
Name every exterior door, accessible window, garage, gate, motion area, leak point, panic job, siren, keypad, camera view, responder, and unavailable-owner path. Use the zone-naming guide so the physical label, app, alarm history, camera, responder instruction, and exported file describe the same place.
Map the exact local-storage route
Record whether each camera writes to a removable card, base station, HomeBase, NVR, DVR, NAS, computer, phone, or optional cloud service. Write the exact compatible device, installed and usable capacity, camera count, resolution, frame rate, codec, event or continuous schedule, overwrite rule, protected-clip rule, oldest clip, drive-health warning, clock source, encryption statement, export format, player requirement, and replacement owner.
| Storage path | Do not assume | Test |
|---|---|---|
| Camera card | Removal resistance, capacity, health warnings, encryption, remote playback, or survival if the camera is stolen | Fill, overwrite, protect, remove, replace, export, and open elsewhere |
| Base or HomeBase | Every camera is compatible, all detections stay local, drive expansion is supported, or ended-service behavior is unchanged | Per-camera recording, internet loss, base power loss, storage warning, second admin, and export |
| NVR or DVR | Cross-brand compatibility, full resolution, audio, AI, deterrence, PoE budget, clock, or drive size | Per-channel record, cable failure, drive warning, protected clip, local display, and second-device export |
| NAS or computer | Supported protocol, license, account permissions, retention, update stability, UPS runtime, or simple incident export | Restart, storage full, share unavailable, credential change, restored recording, and export |
| Optional cloud | Local recording mirrors cloud history, features remain after cancellation, or deletion is immediate and complete | End service and record local, remote, retention, export, account, and deletion state |
The existing camera-without-subscription guide covers the camera shortlist. This page is broader: it tests the installed alarm, evidence, response, outage, service, and ownership record around that camera layer.
Test event evidence, not marketing labels
For every intended view, run ten ordinary day events and ten low-light events. Record first useful frame, event start, pre-event context, post-event context, timestamp, continuity, subject size, motion blur, illumination, classification if offered, audio state, alert delay, recording location, playback, protection, export, and miss.
Export one ordinary event and one incident-style sequence. Open both on a second device without relying on the primary phone. Confirm timestamps and continuity, then have the second administrator repeat the export. Preserve the original file. Record device, channel, date, time zone, export method, file name, hash if available, recipient, disclosure, and deletion rule.
Build the self-monitoring response path
A notification is not a response. Record who receives each direct zone, camera alert, trouble state, low battery, storage warning, internet loss, power loss, and device-offline event. Record what they can lawfully verify, who they contact, what they do when uncertain, and who acts if the primary person is asleep, driving, traveling, without service, or unavailable.
Use the no-contract systems guide when optional professional monitoring is part of the design. Keep monitoring eligibility, communications, verification, dispatch, permits, false-alarm rules, cancellation, and permanent no-plan behavior in a separate record.
Internet, power, storage, and device failures
| Failure | Record | Pass condition |
|---|---|---|
| Internet disconnected | Direct sensing, local warning, local camera recording, playback, remote alerts, app state, clocks, queued events, and restore time | Required local jobs continue or fail clearly |
| Router or access point unavailable | Hub, cameras, local storage, phone on LAN, stale state, DHCP, reconnect order, and duplicate devices | Each required device returns once with the correct name and state |
| Property power lost | Hub, siren, sensors, cameras, NVR, drive, router, switch, display, UPS loads, runtime, shutdown, and restart | Measured runtime and clean restoration meet the response plan |
| Storage full or unhealthy | Warning, overwrite, protected clips, replacement, rebuild, playback, export, and owner | Known-good evidence survives and opens elsewhere |
| One camera or sensor fails | Trouble visibility, blind area, compatible spare, replacement, reset, account release, and acceptance retest | Named owner restores the intended job |
| Primary phone unavailable | Second-admin alarm control, playback, export, contacts, recovery, and temporary-user removal | Incident path completes without the primary phone |
Map cameras, alarm hubs, storage, routers, switches, and administrator devices with the network segmentation guide. Keep network isolation from breaking local discovery, evidence export, updates, or recovery.
Users, privacy, and removed access
Use named identities. Record who can arm, disarm, silence, change zones, view live cameras, play recordings, export evidence, change retention, delete clips, add users, alter services, replace storage, update firmware, reset devices, or recover accounts. Remove one temporary user and prove old sessions, invitations, links, live view, recordings, downloads, settings, codes, and recovery methods fail.
Use the camera privacy guide for lawful views, neighboring-property boundaries, privacy masks, audio rules, indicators, retention, incident sharing, and deletion. Local storage is not automatically private, encrypted, healthy, backed up, or inaccessible to a former user.
Ownership and 36-month cost
Record who owns the hub, sensors, sirens, keypads, cameras, bases, recorder, drives, cards, cable, network equipment, UPS, display, accounts, subscriptions, exported files, installation map, warranties, support records, recovery methods, and deletion authority. Record resale, return, disposal, reset, transfer, and proof that the former owner has lost access.
Price the same security and evidence jobs over 36 months: equipment, additional direct sensors, cameras, storage media, replacement drives and cards, batteries, mounts, cable, PoE equipment, router or access-point work, UPS, installation, optional services, failed devices, tax, shipping, and owner time. A zero-dollar plan can still carry a high operating cost.
60-minute no-subscription security acceptance test
- Minutes 0-8: reconcile exact devices, direct zones, local warning, cameras, storage, network, power, users, services, owner, responder, support, and recovery methods.
- Minutes 8-20: trigger every direct zone twenty times. Save names, modes, delays, warning, history, remote events, response, misses, duplicates, low battery, and offline state.
- Minutes 20-32: run ten day and ten low-light camera events per intended view. Save recording start, context, clock, classification, playback, retention, export, privacy, and misses.
- Minutes 32-42: disconnect internet and run the approved power-loss path. Record local protection, recording, remote failures, stale state, UPS runtime, clocks, queued events, restart, and restoration.
- Minutes 42-50: run the maker-approved storage-health or capacity test. Protect a clip, verify overwrite, export evidence, and open it on a second device.
- Minutes 50-56: make the primary phone unavailable. Have the second administrator complete alarm control, response, playback, export, recovery, and temporary-user removal.
- Minutes 56-60: end optional services in the worksheet, total 36-month cost, and sign the permanent-state, ownership, reset, transfer, deletion, and acceptance records.
No-subscription home security evidence FAQ
Does no subscription mean every security feature is free forever?
No. Record the permanent unpaid state for the exact hub, sensors, siren, cameras, local storage, app, alerts, remote access, users, support, updates, transfer, reset, and deletion. Hardware, drives, batteries, network equipment, replacement devices, and owner time still cost money.
Is local camera storage the same as a home alarm?
No. Local footage can support evidence, but it does not by itself provide direct opening zones, local alarm warning, cellular communications, professional monitoring, or emergency response.
Can local recording continue without internet?
An exact powered camera-to-storage route may continue locally, but remote access, notifications, clock sync, classifications, account functions, and service-dependent features may stop. Disconnect internet during the return window and test recording, playback, export, stale state, queued events, and restoration.
What makes a security export useful?
The original event should have a clear timestamp, enough pre-event and post-event context, a known source device, a documented export method, an ordinary file name, and a format that opens on a second device without the primary account. Preserve the original and record who handled each copy.
