Architecture

Architecture for cameras, community, and IoT

Horus@Fidumtec is organized as a service architecture: cameras remain at each site, users consume viewing from the mobile app, and the cloud environment coordinates identities, permissions, notifications, scenarios, and integrations.

Each Horus instance represents an autonomous environment. Relationships between devices, users, groups, calendars, permissions, and automations exist inside that instance, guaranteeing operational independence and logical security between different installations or customers.

1. Cameras and sites

• Cameras are onboarded through standards such as ONVIF.
• One user can operate owned cameras and views shared by third parties.
• The platform avoids depending on each manufacturer's proprietary cloud.

2. Cloud environment

• Manages users, groups, cameras, permissions, and communities.
• Defines 24/7 access windows or temporary permissions with start and end dates.
• Coordinates specific notifications for linked users.
• Maintains personalized dashboards according to each user's permissions.
• Provides the foundation for ISP and IoT specializations.

3. Sensors, actions, and AI

• Integrates selected IoT sensors to complement camera information.
• Executes remote physical actions through IoT devices.
• Processes video images with inference engines to generate events and user information.
• Enables rules based on events, logical conditions, sensor states, schedules, calendars, and user presence.

4. Specializations

The same architecture can support different commercial scopes: camera communities, ISP services, infrastructure monitoring, and IoT integrations. Horus works as the base platform, while Fidumtec articulates specialized offerings on top of it.