APOLLO BY OMETRA
Centralize content, campaigns, stations, fleet, WiFi, audience, and evidence in a modular architecture.
Connected modules
Execution points
Shared context
The problem
The challenge is not publishing one asset. It is coordinating assets, rules, devices, evidence, and audiences without multiplying manual handoffs, disconnected tools, and blind spots.
Assets and versions
Campaigns and rules
Distributed execution
Evidence and compliance
Audience and consent
APOLLO preserves context from the asset and schedule through audience and evidence.
One operating model
Modules govern rules, processes, and data. Components bring that logic to the desktop, player, and network.
Assets, metadata, and versions.
Campaigns, schedules, and rules.
Sites, nodes, and local execution.
Access, consent, and audience.
Evidence, incidents, and reports.
Suite architecture
The architecture separates central governance from local execution so APOLLO can be integrated in stages and coexist with existing infrastructure.
Core modules
PROTEUSAssets and transformations
IGNISCampaigns and rules
FLAREAudio and video stations
PULSEFleet, licenses, and telemetry
AERISWiFi and audience
LUMEEvidence and complianceOperational components
Proteus Drive
Extends PROTEUS
Ember
Operates with PULSE, IGNIS, and FLARE
Aeris Client
Extends AERIS
PROTEUS
Centralizes media assets, controls their lifecycle, and prepares each variant for the right channel.
IGNIS
Turns commercial and operational objectives into executable campaigns through calendars, priorities, and rules.
FLARE
Manages linear channels and continuity through schedules, blocks, live sources, and fallback rules.
PULSE
Governs sites, nodes, and licenses; distributes configuration and maintains visibility into fleet health.
AERIS
Governs access, consent, and interaction to turn sessions into usable knowledge.
LUME
Turns tasks, captures, and technical signals into reviewable evidence, manageable incidents, and auditable reports.
Execution close to operations
These components extend core modules; they are not presented or governed as independent products.
Desktop client
Synchronizes local folders, detects changes, and reports transfer status.
Extends PROTEUS
Local execution engine
Executes content and schedules, maintains cache, and reports telemetry.
Operates with PULSE, IGNIS, and FLARE
Clients and provisioners
Integrates gateways, applies access policies, and reports sessions.
Extends AERIS
Connected circuits
Each circuit preserves identity, organization, permissions, audit, and explicit integration contracts.
From the approved file to execution and evidence by site.
Governed asset, scheduled campaign, supervised execution, and consolidated evidence.
From the schedule to a continuous audio or video output with local continuity.
Central schedule, local operation, and a record of events and incidents.
From the gateway to the session, consent, and authorized activation.
Governed access, audience knowledge, and contextual communication rules.
Use scenarios
Illustrative scenarios; final scope depends on the agreed version, infrastructure, integration, and SOW.
Multi-site retail
A promotion is prepared, scheduled, distributed, and documented by location and time window.
Transport and mobility
Live information, segments, and fallback content coexist throughout the operating day.
WiFi in mobility
The portal applies consent and session rules; authorized interactions feed profiles and surveys.
AERIS compatibility
Aeris Client combines installable clients and provisioners to integrate with gateways and management platforms.
Compatibility is confirmed by model, firmware, topology, access mode, and homologation.
Architecture and trust
APOLLO integrates cloud and near-operation execution through APIs, events, and platform controls.
Tenant context and roles restrict access to the authorized scope.
Each action respects credentials, roles, and application permissions.
Changes, events, and sensitive actions remain traceable.
AERIS records applicable notices, purposes, and access events.
Only attributes required for the documented purpose are captured.
Validation exceptions in LUME remain subject to review.
Availability and scope are validated by version, integration, operational capacity, privacy, SLA, and SOW.
Next step
Request a demonstration to review the circuit that best fits your network, infrastructure, and operational objective.
