Check the fit before you connect.

No. New accounts use email and password. Legacy internal usernames remain for compatibility, but you do not need to remember one.

Supported sources include RTSP and supported HTTP MJPEG, MP4 and playlist inputs, plus documented supported transports. Exact codec, authentication and device behaviour matter. Run a decoded-video test for your exact model. We do not promise every camera or proprietary phone app.

No. Discovery, profile resolution and video decoding are separate checks. Verify the exact device/firmware and stream. CamBackup does not claim ONVIF product certification.

Yes. A compatible local feed can use the outbound LAN gateway on supported Windows x64 or Linux ARM64/AMD64 hardware. Camera credentials remain on the gateway device. Check the Gateway page for packages and requirements.

Gateway 0.2 has optional local recording, off by default. Enable it before an outage and keep the camera, gateway service and disk running. Local clips contain unmasked source video and audio, have their own storage/retention limits, and are not uploaded later. Cloud recording still needs connectivity; neither copy is guaranteed gap-free.

Not automatically. There is an integration framework, but each proprietary app/device needs a model-specific adapter, permission and real hardware validation.

Creating an account and testing camera compatibility are free. Ongoing cloud recording needs a plan for each camera. If your account includes a recording trial, its access and end date are shown in the app. Compare plans on Pricing or contact us for help.

Power and Business. An account needs at least one active confirmed subscription on one of those tiers. Staff roles, account trials and similarly named legacy plans do not grant developer access. Normal interactive app use remains available on other plans.

Power and Business on the exact camera being shared. A higher-tier plan on another camera does not make every camera eligible for public sharing.

New developer-token requests, MCP and automation triggers fail when the account no longer qualifies. Public playback checks the exact camera’s eligibility. You can still list/revoke credentials, disable shares and view owned saved footage under its normal retention rules.

Compare the per-camera plans on Pricing, then contact us with your camera count and recording needs. We will confirm your subscription options, total price and payment steps before you commit. A pending or failed payment does not activate a plan.

No. Retention is a ceiling and storage/output limits also apply. Actual scene bitrate, audio and saved media affect capacity. Check the plan allowance and observed usage together.

Yes, fixed opaque source-area masks apply before new cloud output is stored or distributed. Stop acquisition before editing and verify fresh output. They do not change old footage, local gateway previews or local recordings.

Yes, capture-policy audio controls apply to new output within the source/plan capability. Muting the browser player does not remove a stored audio track; verify a new exported file.

No. Optional analysis samples recorded footage and can miss or misinterpret faces. It is not continuous identity verification. Identity-related processing can bring additional privacy obligations; do not assume it is appropriate for staff, customers or public spaces. Keep it off unless you have established a lawful, necessary purpose for your situation.

Yes, eligible accounts can use an expiring camera-scoped key or a suitably scoped personal token. Stable external IDs prevent duplicate retries. Duration 0 creates a bookmark; 1–3600 requests future capture, not pre-roll.

No. Camera availability, entitlement and worker completion still matter. Check confirmed segments and the resulting timeline. An existing recording window is not extended by a trigger.

Public widgets intentionally allow anyone holding the active share link to watch without signing in. Viewers can copy it. Never embed account credentials. Disable or rotate the share to stop future access through the old link.

Yes. Authorised media is served through CamBackup endpoints, including byte ranges. Never publish a private playback capability just because its domain is CamBackup.

Yes. When enrolled, the account must pass its second factor after those primary sign-in methods too. Password reset does not disable MFA. Save recovery codes independently.

Not currently. Use a client with private Bearer headers or the documented stdio bridge. Google account login is not an MCP OAuth authorization server.

The dashboard is an installable web app for supported mobile and desktop browsers, with optional push notifications. It does not cache private footage for offline playback. Cloud recording depends on the camera connection, not on leaving the dashboard open. Gateway local recording is a separate option on the device at your site.

No zero-loss guarantee is made. Durable jobs and worker recovery help resume eligible work, but interrupted source/network/power can leave gaps. Verify actual recovered segments.

Use the support guides or Contact page. Send the camera model, time/timezone, safe error text and steps tried. Never send passwords, OTPs, recovery codes, camera URLs with credentials, or private playback links in a public message.

No. CamBackup makes a new off-site recording from a compatible live camera feed or recorder channel. You can keep an NVR recording alongside it, but CamBackup does not import its archive or upload missing footage after an outage. Test the exact channel before choosing a plan.

Not always. For a cloud-reachable camera, start with its network address and let the connection assistant try supported profiles. You can also supply a known stream URL or select brand/model details. For private LAN cameras, the gateway offers local discovery. Finding a profile still requires a successful decoded-video test.