The control room for your deployment.
Monitor the entire system, connect any protocol through Bridges and set up new connections in minutes — everything you need to take PixelCore from pilot to production.
Everything under one console
System overview
Service health, storage footprint and live throughput — the whole platform's state on one screen.
Device management
Provision the fleet in bulk, inspect any signal's history, and stand up new connections in minutes.
Integration bridges
MQTT, LoRaWAN/LNS, TCP/IP and HTTP in one place, with per-connection throughput, uptime and payload templates.
One console, from health check to hands-on
Watch the whole system, connect any protocol, drill into a single signal, and onboard a new endpoint — here it is, exactly as an operator sees it.
See the entire platform in one clear view
Keep every critical component in sight: dispatcher, media server, device drivers and bridges. A single dashboard gives you instant insight into service health, storage retention and live throughput.
- Service health and last-seen status
- Storage footprint, retention and inventory
- Live throughput trends (day over day)
Provision and control every device
Onboard sensors, gateways and controllers in bulk, then assign the appropriate driver for each device type. Maintain fleet health with centralized monitoring: view live status, last-seen timestamps and battery levels in one place.
- Bulk onboarding with auto-assigned drivers
- Live status, last-seen and battery health
- Remote configuration, reboots and over-the-air updates
Connect any protocol with Bridges
Each bridge links PixelCore to an external protocol including MQTT, LoRaWAN/LNS and HTTP. Manage connections, credentials and endpoints, monitor live IN/OUT throughput and uptime, and shape payloads with message templates.
- MQTT, LoRaWAN and HTTP bridges
- Per-connection throughput and uptime
- Message templates for payload transforms
Each bridge module connects PixelAdmin to an external protocol. Within each bridge you can manage connections (credentials & endpoints) and message templates (payload transformations).