iFovea cloud VMS and AI video analytics platform logo

FAQS

Here is a compilation of the most commonly asked questions over IFOVEA and its operation or troubleshooting. If you still cannot find an answer to your question, our tech support line is open Monday-Friday, 8 AM-5 PM CST.

About IFOVEA Subscription Plans

No – we have a basic plan for recording without analytics if you have no desire for it.

Each subscription is only for one camera, so if you have 10 cameras, you will need to purchase 10 plans.

Each camera is able to have a different plan based on how many days you want to save recordings and whether you want analytics.

IFOVEA offers different plans based days of data storage. You can choose a minimum of 1 day and a maximum of 30 days.

The 1 Day and 30 Days plans will record with a maximum resolution of 2MP at 12 FPS. If you select the 7 Days plan, you will be able to choose a resolution of 2MP or 4MP at 15 FPS.

We offer customizable plans if you wish to record with a resolution higher than 4MP. Please contact [email protected] to hear about our options.

Higher resolution = more storage and bandwidth being used, so it will be more expensive to record with 4MP.

Object Detection & Tracking, People & Vehicle Counting, and Heat Maps

Yes – you can view our plans here.

IFOVEA offers both monthly and annual subscription plans so you can choose the plan that best suits you.

No, you can sign up for free here but a demo is recommended to present to your clients.

Our subscription plans are for end-users, but we offer a special deal for security integrators to sell IFOVEA to their clients under their own brand. If you’re interested in learning more about our dealers program, reach out to our sales team at [email protected]

Please submit a form here, and we will send you a link to demo the software. It will include live video as well as an analytics demo.

We offer technical support for both our end-users and integrators so that they can support their end-users. Integrators will be able to receive alerts about any cameras that go offline.

Unfortunately, ONVIF cameras can only have Pay As You Go plans with or without analytics. P&P cameras offer more plan choices which you can view here.

Cinematic enterprise physical security cloud surveillance visual for FAQ
AI search and investigation visual for FAQ

About iFovea Setup

iFovea uses Amazon Cloud Service AWS that promotes high security for your data.

You can add an unlimited number of cameras to iFovea as long as you purchase a subscription for it.

No – only an IP camera is needed to connect to the software.

Currently, iFovea only supports IP cameras.

Yes – you can connect your NVR to iFovea, and it will connect your cameras as well.

Yes – without a stable internet connection, the cameras will disconnect from the software and recordings will no longer be saved. However, the footage that has already been saved will stay.

A simple LAN will not be enough because these cameras will need to be able to reach the Internet in order to connect to iFovea.

Yes – you can download iFovea on both the App Store and the Play Store.

ifovea ios qr
iOS
ifovea android qr
Android

If your cameras are POE, then it is not necessary.

Yes – as long as you have the correct camera information needed to add it and the camera is online, you can add it from anywhere in the world.

For ONVIF and generic cameras port forwarding will be required, but for P&P cameras it is not necessary.

About IFOVEA Operation

There is no limit to the number of customers that you can have.

Yes – please fill out this form to request a demo of iFovea.

Yes – you can find various tutorial videos on our YouTube channel.

Object detection is a deep learning algorithm that involves detecting the location of objects in images and videos in real-time and classifying them. Object tracking is a technique that follows the movement of the detected objects.

Every person has unique features that differentiates them from others. Even though people may look similar, no face is exactly the same. Face Recognition is a method of identifying or verifying the identity of a person through their face.

Heat Maps is a visual technique that shows the frequency of motion detected. most cameras use motion detectors to determine moving objects, but IFOVEA’s Heat Maps are more accurate in determining animate and inanimate clusters using their object classification technology.

Yes – the full screen button can be found in the lower right corner. You can close out of full screen mode by hitting the ESC button on your keyboard.

Navigation is where you can organize multiple cameras into different groups. You can also select a specific group of cameras to view from this menu.

Events is used to show when an “event” took place, such as when a person, luggage, or car has been detected. You can filter events by type of object detected or by date and time.

Library is where your clips and/or timelapses will be shown.

The Map is used to show the location of all of your cameras. You can also select a camera or a group of cameras to view from the map.

Autoscan runs a sequence through the selected cameras. You drag the desired cameras into the Autoscan menu, choose the amount of time between each camera, and then start the sequence. You can choose to switch through single camera views or through groups of cameras.

The Thumbnail Grid is used for a more convenient view of events during various time intervals. You can choose to view XS, S, M, or L thumbnails.

A clip is a short video from Time A to Time B and is usually shown playing in real-time. A timelapse follows the same concept but with a much longer period of time between the two points and is usually shown being fast-forwarded.

Any clips or timelapses you create will be saved in the Library indefinitely and will also show on the app after creation.

Yes – you can create clips and download them to a specific location.

Each clip must be at least 30 seconds long.

Videos that are downloaded from IFOVEA will be mp4 format.

Events are triggered whenever there is motion detected. Then the software will further determine the type of event that is happening.

IFOVEA Cloud VMS FAQ

Answers to the most common questions about iFovea cloud VMS, AI video analytics, camera compatibility, pricing, migration, and compliance. Each answer links to the relevant detailed resource.

Cloud VMS Basics

iFovea is a cloud VMS (Video Management System) and AI video analytics platform that connects existing ONVIF-compatible IP security cameras to the cloud. It replaces on-premises NVR/DVR systems with cloud storage, remote access, role-based user management, and AI analytics — without requiring camera replacement in most cases. See the Cloud VMS Platform Guide for a full overview.

An NVR (Network Video Recorder) stores footage on a local hard drive at each location, provides access only from that location (or via unreliable port forwarding), has no AI analytics, and represents a single point of hardware failure. A cloud VMS stores footage in secure cloud infrastructure, provides browser and mobile access from anywhere with no VPN, includes AI analytics, and scales across multiple locations from one dashboard. See the full Cloud VMS vs. NVR comparison.

VSaaS stands for Video Surveillance as a Service — cloud-based video surveillance delivered as a monthly subscription rather than requiring upfront hardware purchases. iFovea is a VSaaS platform. The subscription covers cloud storage, the VMS software, AI analytics, and mobile access. See the VSaaS Platform Guide.

Yes. iFovea is designed for multi-site deployments. All locations, cameras, and AI events are managed from a single dashboard. There is no per-location software installation — adding a new location requires installing a Gateway device at that location and connecting cameras through it. See Multi-Site Cloud Surveillance Management.

Not in most cases. iFovea supports 500+ ONVIF-compatible IP camera models from Hikvision, Axis, Uniview, Hanwha, Milesight, Dahua, Vivotek, TVT, Tiandy, 2M Technology, and many others. If your cameras support ONVIF or RTSP streaming, they can connect to iFovea without replacement. Check the camera compatibility guide for your specific models.

The iFovea Gateway is a compact device that connects to your existing network switch (where cameras are already cabled) and bridges existing IP cameras to the iFovea cloud platform. It replaces the function of a local NVR server. Installation typically takes 1–4 hours per location. No new camera cabling is required for compatible cameras.

Camera Compatibility

iFovea supports any camera that uses ONVIF Profile S/G/T or RTSP streaming — the open protocols supported by virtually all commercial IP cameras manufactured since 2010. Confirmed compatible brands include Hikvision, Axis, Uniview, Hanwha, Milesight, Dahua, Vivotek, TVT, Tiandy, and 2M Technology. Check your specific model at the BYOC camera guide.

Check whether your camera’s specification sheet lists ONVIF Profile S, Profile G, or Profile T, or whether it lists an RTSP stream URL. Most commercial IP cameras installed in the past 10 years support ONVIF. You can also check the manufacturer’s website or the ONVIF conformant products database at onvif.org. If you’re unsure, submit a compatibility review request through the demo form.

A minimum of 2MP (1080p) is recommended for reliable AI analytics — people counting, object detection, and ALPR. Higher resolution (4MP) improves accuracy in dense scenes or at longer distances. Cameras below 1080p may connect to the platform for recording but may not support all AI analytics types reliably.

Yes. ONVIF-compatible PTZ cameras connect to iFovea and PTZ controls (pan, tilt, zoom) are available through both the web portal and the mobile app using touch or mouse controls. PTZ presets and patrols supported by the camera’s ONVIF profile are accessible through the platform.

Yes. iFovea’s open ONVIF architecture supports mixed camera inventories — multiple brands at the same location, or different brands across different locations — all managed from the same unified dashboard. This is one of the primary advantages over proprietary platforms that require all cameras to be the same brand.

Setup and Hardware

A typical location with 10–20 existing ONVIF-compatible cameras can be operational on iFovea in 2–4 hours of installation time. This covers Gateway installation, camera discovery, name configuration, retention policy setup, user access configuration, and AI analytics configuration. Locations with more cameras or complex network configurations may take longer.

The NVR can be decommissioned once the Gateway is operational and you have confirmed cloud footage access and retention. During the transition period, both systems can run in parallel. Many customers decommission the NVR immediately on the day of Gateway installation. The iFovea Gateway connects to the same PoE switch the NVR was connected to.

iFovea needs a reliable internet connection at each location for cloud recording. Recommended upload bandwidth is 0.5–1 Mbps per camera for continuous recording at standard quality. A 10-camera location needs 5–10 Mbps of upload capacity. For locations with limited bandwidth, hybrid cloud architecture records locally and uploads selectively, reducing bandwidth needs by 70–90%. Use the bandwidth calculator.

In hybrid cloud deployments with the iFovea Gateway, local recording continues during internet outages. No footage is lost. When connectivity is restored, footage recorded during the outage syncs to the cloud and becomes available in the portal’s timeline view. Full-cloud deployments without local edge storage will have recording gaps during outages.

No. The cloud video portal is fully browser-based — no desktop software, no browser plugins, no VPN. Access works from any modern browser on any device. Mobile access is through the iFovea iOS and Android app.

Bandwidth and Cloud Storage

A 2MP camera streaming continuously at standard quality uses approximately 0.5–1 Mbps of upload bandwidth. A 10-camera location needs 5–10 Mbps of dedicated upload capacity. A 40-camera warehouse needs 20–40 Mbps. Hybrid cloud architecture reduces this by 70–90% by recording locally and uploading only relevant clips. Use the bandwidth calculator to estimate your specific requirements.

Retention is configurable per camera, per location group, or per organization. iFovea plans support 14-day (Essential), 30-day (Professional AI), and up to 90-day (Enterprise) retention. Footage expires automatically at the configured period. Legal hold preserves specific footage beyond the standard retention window. Use the storage calculator to estimate storage needs and see the cloud video storage guide for compliance planning.

You do. Video footage recorded on your cameras is your organization’s data. iFovea does not claim ownership of customer footage or use it for any purpose beyond service delivery. Footage is exportable as standard MP4 files. Data ownership terms are specified in the subscription agreement.

Yes. Retention is configurable per camera, per camera group, or per location. High-priority cameras (registers, entrances, docks) can use 60-day retention while low-priority cameras (storage corridors, equipment rooms) use 14-day retention. Per-camera retention configuration optimizes storage costs. This is managed through the admin portal.

Footage is encrypted in transit using TLS and at rest using AES-256 encryption. Access requires authenticated credentials. The platform supports MFA for all accounts and granular role-based access controls that limit which users can see which cameras. Every access event is logged in a tamper-evident audit trail. See Cloud VMS Compliance and Security.

AI Analytics

iFovea includes 10+ AI analytics types as part of the platform — not sold as separate add-on modules: ALPR (license plate recognition), face recognition, people counting and occupancy, loitering detection, fire and smoke detection, PPE compliance monitoring, object detection and classification, heat maps, AI forensic video search, and color and area search. See the full AI analytics platform overview.

AI forensic search lets you find specific footage across all cameras and all locations simultaneously by searching for object type (person, vehicle), color (blue jacket, red truck), behavioral pattern (running, loitering), license plate, or defined zone. A search that would take 2–4 hours of manual timeline review takes minutes. See AI Video Search for Surveillance.

No. AI analytics processes are run in the iFovea cloud — they do not require AI-capable cameras or edge processing hardware. Any ONVIF-compatible camera at 2MP (1080p) or higher resolution can be used for AI analytics. Camera angle, placement, and lighting affect accuracy but no specialized camera hardware is required.

Yes. Virtual zones are configured in the platform for each camera — defining entry zones, restricted areas, counting lines, and detection boundaries. Alerts fire when specific object classes (people, vehicles) enter or exit defined zones. Zone configuration and alert routing are managed through the admin portal.

Counting accuracy depends on camera placement, resolution, and scene density. Overhead or near-overhead camera angles deliver the highest accuracy by eliminating person-to-person occlusion. Side-view eye-level cameras are less accurate in dense scenes. For best results, iFovea’s deployment team provides camera placement guidance for people counting deployments. See People Counting Video Analytics.

Pricing and Plans

iFovea is priced per camera per month on a subscription basis. Plans include Essential (14-day retention), Professional AI (30-day retention + full AI analytics), and Enterprise (up to 90-day retention + advanced features). Volume pricing tiers reduce per-camera cost at 25+, 100+, and 500+ cameras. See the pricing page or use the cost calculator for a deployment-specific estimate.

Cloud storage is included in the per-camera subscription — it is not billed separately based on actual storage consumption. The subscription tier determines the available retention period. There are no variable storage fees or surprise overage charges. This makes budget planning predictable compared to platforms that bill storage usage separately.

Contact the iFovea team for current minimum terms and camera count requirements. Submit a demo request to discuss your specific deployment size and pricing options. Enterprise pricing for large multi-site deployments is available through the enterprise pricing page.

Yes. Use the cloud VMS cost calculator to model monthly costs by camera count, retention period, and feature tier. Use the bandwidth calculator to estimate upload requirements, and the storage calculator to estimate retention storage needs.

Migration and Switching Platforms

Verkada uses proprietary cameras that don’t support ONVIF — they cannot be reused with iFovea. Migrating from Verkada requires replacing Verkada cameras with ONVIF-compatible alternatives. The migration benefit is eliminating Verkada’s per-camera hardware lock-in ($500–$2,000+ per camera) on future purchases. See the full Verkada migration guide and iFovea vs. Verkada comparison.

Yes. Most cameras in Milestone deployments are standard ONVIF cameras that can connect directly to iFovea. The migration replaces the Milestone server and license with the iFovea cloud platform. Cameras typically don’t need to be replaced. See the Milestone migration guide.

Yes. Genetec deployments typically use ONVIF-compatible cameras from Axis, Hanwha, Bosch, and other manufacturers that connect directly to iFovea. The migration eliminates Genetec’s on-premises server infrastructure. See the Genetec migration guide and Genetec alternative page.

A single location with 10–20 cameras typically takes 2–4 hours to go live. At chain scale, a phased rollout of 5–10 locations per week allows validation of each deployment before scaling. A 40-location network can realistically complete a full rollout in 90–120 days. Use the multi-site migration checklist for planning and the migration checklist for per-location steps.

In most cases, yes — if cameras are IP cameras that support ONVIF or RTSP. Analog cameras connected to a DVR via coaxial cable cannot connect to iFovea directly; they would need to be replaced with IP cameras. Check the existing camera compatibility guide for your specific situation. See also replacing legacy DVR and NVR systems.

Security, Compliance, and Governance

iFovea uses granular role-based access controls (RBAC) configurable at the user, role, camera group, and location level. Users only see cameras their role grants access to. Every access event — footage view, AI search, export, configuration change — is logged in an immutable audit trail. MFA is supported for all accounts. Manage through the admin portal.

Yes. Specific footage can be flagged for legal hold, preserving it beyond the standard retention period until the hold is explicitly released by an authorized administrator. All legal hold actions are logged in the audit trail. Footage exports include timestamp metadata for chain-of-custody documentation. See compliance and security capabilities.

Footage is exported as standard MP4 files with full timestamp metadata, and every export event is logged in the audit trail creating a chain-of-custody record. Consult legal counsel about specific evidentiary requirements in your jurisdiction. iFovea’s export and audit logging capabilities are designed to support evidentiary use.

iFovea’s cloud storage infrastructure uses enterprise cloud data centers. Organizations with specific data residency requirements should discuss geographic storage location with the iFovea team during the deployment assessment. Contact via the demo form.

NDAA, Hikvision, and Chinese Camera Restrictions

For federal agencies and federal contractors: purchase and use is prohibited under NDAA Section 889. The FCC also stopped authorizing new Hikvision and Dahua equipment in 2022 and in October 2025 voted to begin revoking previously granted authorizations. For private commercial businesses with no federal relationships: no current federal mandate requires removal of existing equipment. See the full explanation at Hikvision and Dahua Restrictions: What Businesses Should Know.

No. iFovea does not make restricted hardware NDAA compliant. Connecting Hikvision or Dahua cameras to any cloud VMS platform does not change their regulatory classification. Federal contractors must replace covered cameras with NDAA-compliant hardware. See the NDAA compliance migration guide.

For private commercial businesses not subject to NDAA compliance requirements: possibly yes, if existing cameras support ONVIF. This addresses the NVR’s operational limitations (no remote access, no AI, hardware failure risk) without camera replacement cost. It does not resolve any compliance obligations. See Hikvision and Dahua NVR Replacement With Cloud VMS.

NDAA Section 889 Part B requires federal contractors to conduct a “reasonable inquiry” into their use of covered equipment, certify compliance in SAM.gov, and report discoveries within one business day. The compliance deadline is December 2026. Covered cameras must be removed. iFovea can provide cloud VMS for the NDAA-compliant replacement cameras. Consult legal counsel for specific guidance. See the NDAA compliance migration guide.

NDAA-compliant manufacturers include Axis, Hanwha, Bosch, Vivotek, Uniview, and Milesight — all ONVIF-compatible and supported by iFovea. See the camera compatibility guide for specific models and the cost comparison guide for migration budget planning.

Integrators and Resellers

Yes. iFovea offers a VSaaS reseller program for security integrators. Resellers purchase at wholesale pricing and set their own retail rates. A white-label VMS option is available for integrators who want to deliver the platform under their own brand. See the VSaaS reseller program guide and cloud VMS for integrators guide.

Yes. The admin portal supports multi-tenant management — integrators can view and manage all customer accounts from a single interface with isolated customer data environments. Customers can be given their own sub-administrator access without seeing other customers’ data or integrator-level settings.

Yes. The VSaaS billing module provides per-customer subscription tracking, camera count management, usage visibility, and recurring revenue reporting for integrators operating a managed cloud surveillance service.

iFovea supports existing Hikvision, Dahua, and other ONVIF camera systems for private commercial customers not subject to NDAA compliance requirements. The Gateway installation replaces the NVR and delivers cloud access, AI analytics, and recurring revenue for your practice. For customers with federal contracting or compliance requirements, recommend full NDAA-compliant camera replacement with iFovea cloud VMS. See the integrator cloud upgrade guide.

Didn't find your answer?

Request a demo and speak with the iFovea team directly — we can answer questions specific to your camera inventory, location count, compliance situation, and deployment requirements.

Request a Cloud VMS Demo