Fortivia · Camera comparison
Fortivia Security Cam
vs Fortivia IPCam
Compare native phone monitoring with browser viewing and compatible IP camera connections. Find the setup that fits how you want to watch.
Prepared: November 4, 2026. Covers the iOS and Android projects in this workspace. Features below describe source capabilities; availability in a published app depends on its build, permissions, access plan, and deployed services.
Main difference
Fortivia Security Cam is the camera half of the Fortivia Security Cam and Fortivia Camera Viewer solution. Use Cam on a spare phone and Viewer on an everyday phone for live viewing, two-way communication, motion alerts, and event review.
Fortivia IPCam emphasizes browser viewing and compatible IP camera/player connections. Use IPCam on the camera phone and share its generated viewing link with trusted people. A browser viewer does not require installation of the Fortivia Camera Viewer companion.
Both can reuse spare smartphones, store footage locally, and support more than continuous recording. IPCam also contains motion recording and scheduling, so those features alone do not distinguish the products.
Feature comparison
On a small screen, scroll the table horizontally to see every column.
| Area | Fortivia Security Cam | Fortivia IPCam |
|---|---|---|
| Camera platforms | iOS and Android | iOS and Android |
| Primary viewing experience | Fortivia Camera Viewer app on iOS or Android | Hosted browser viewer, supported local browser/stream paths, and compatible players |
| Typical setup | Install Cam on a spare phone, Viewer on an everyday phone, then scan/import Setup Info | Start IPCam and open/share its generated viewing link or use a supported local stream URL |
| Cross-platform use | iOS and Android Cam/Viewer combinations | Browser viewing across compatible phones/computers; local protocol compatibility varies by client |
| Multiple viewers | Multiple authorized Viewer devices | Concurrent browser viewers and supported local clients, subject to resource/access limits |
| Live video | Yes, through the native companion workflow | Yes, through browser and supported local stream workflows |
| Two-way speech | A core Cam/Viewer workflow | Audio support depends on the browser/player and connection path; do not promise identical two-way speech across all clients |
| Motion recording | Present in source, with object-aware processing and configuration | Motion processing and recording are also present in source |
| Motion schedules | Present in source | Present in source |
| Alerts and event review | Native Viewer notification/event workflow is central | Do not assume browser push alerts and event controls match the native Viewer workflow |
| Recording storage | Primarily on the Cam device; Viewer can receive/download copies | Primarily on the IPCam device; viewer/player/export copies may also exist |
| Browse, delete, and share recordings | Camera video browser and supported Viewer event tools | Camera video browser and sharing tools |
| Recording settings | Duration, resolution, storage management, timestamps, camera and screen behavior | Similar camera recording/display controls |
| Browser link sharing | Not the primary product workflow | A primary product workflow |
| VLC and similar players | Not the primary companion workflow | Supported stream URLs can be used by compatible players; a hosted WebRTC page URL is not an RTSP stream URL |
| ONVIF role | The companion Viewer can discover/view compatible ONVIF cameras | Optional local ONVIF server functions expose the phone to compatible clients; iOS distribution entitlement status needs confirmation |
| Remote access | Depends on network/service availability and eligible camera access | Hosted remote access also depends on pairing and current entitlement |
| Local access | Subject to the app's local connection and access rules | Local browser/player/ONVIF paths are subject to reachability, configuration, compatibility, and local access rules |
| Billing | Camera-side trial/subscription/local-only handling exists in source | Separate IPCam trial/subscription/local-only handling exists in source |
Which app fits which use
Choose Fortivia Security Cam with Fortivia Camera Viewer when the daily workflow centers on receiving motion alerts on a phone, opening event recordings, controlling camera motion settings remotely, and speaking through the camera.
Choose Fortivia IPCam when the daily workflow centers on opening a live view in a browser, sharing access with trusted viewers, or integrating a reachable phone camera with compatible local players or ONVIF clients.
Examples:
- Monitor a room from an everyday phone and open motion alerts: Cam plus Viewer.
- Open a camera view from a desktop browser without installing the companion app: IPCam.
- Talk through a camera from the supported native phone workflow: Cam plus Viewer.
- Connect a spare phone to a compatible local IP camera client: IPCam, after confirming the protocol and platform support.
Neither app should be described as guaranteeing continuous unattended capture, unlimited viewers, or universal camera/player compatibility. Device resources, operating system camera restrictions, power, storage, network conditions, and access settings affect operation.
Setup and access credentials
For Cam, install both apps, start the camera workflow, and add it in Viewer by scanning or importing its Setup Info. Current source implements reusable camera enrollment credentials and separate authorizations for individual Viewers. The shared service must support and enable that behavior.
For IPCam, start the camera and open the generated viewing link on another device. Current source keeps the hosted viewer URL stable across ordinary trial/license changes. The page still checks eligibility before remote access; a stable URL after expiry does not grant a paid feature.
Both products can generate QR content that changes when connection metadata or credentials change. Stable credentials do not imply identical QR content after a rename, network change, password change, or camera identity replacement.
Keep QR codes and links private. The IPCam hosted URL can contain encoded authentication information; encoding is not encryption. Sharing an enrollment credential can let another person authorize a Viewer. Deleting one local app entry does not revoke every copy of a shared link or delete footage saved by another viewer.
Privacy and storage
Both products capture video/audio and generate identifiers, connection metadata, and license/access records. Remote pairing, signaling, push delivery where used, and relay services can process data even when recordings are stored locally. Local storage is not equivalent to an app having no server-side data processing.
WebRTC uses encrypted media transport. Local HTTP, RTSP, MJPEG, and ONVIF paths may provide different protection and should be used on trusted networks. Exported recordings, device backups, and recipient copies need separate handling when deleting content.
Platform and release distinctions
On a small screen, scroll the table horizontally to see every column.
| App | iOS app minimum | Android minimum | Application identity |
|---|---|---|---|
| Fortivia Security Cam | 15.6 | API 24 / Android 7.0 | Both: server.cam.fortivia |
| Fortivia Camera Viewer | 15.6 | API 23 / Android 6.0 | Both: client.viewer.fortivia |
| Fortivia IPCam | 15.6 | API 23 / Android 6.0 | Both: server.ipcam.fortivia |
These are app-target source settings. The Android projects target SDK 36. No signed release artifact was inspected. Higher iOS project/test-target settings should not be mistaken for the app target's minimum.
IPCam iOS source sets ONVIFFeature.isAvailable to true and requests multicast capability, while comments still describe entitlement approval as pending. Confirm distribution provisioning and actual device behavior before promising ONVIF discovery in a store listing.
Camera trial lengths, prices, quotas, and store products must be finalized against the deployed service and store setup. In particular, IPCam Android's 28-day trial constant is labeled temporary testing configuration in source. This comparison does not establish production commercial terms or cross-platform purchase transfer rights.
Source basis and document references
- Cam and Viewer overview
- Reusable Cam setup QR
- Persistent Viewer pairing
- Stable IPCam QR
- IPCam hosted license access
- IPCam iOS camera controller
- IPCam iOS ONVIF implementation and capability flag
- Android Viewer manifest
- Release document index
Source/document review only. No build, regression testing, runtime check, deployment, or publication was performed for this comparison.
Need help choosing?
Tell Fortivia about your camera setup and how you want to watch.