I have a fleet of Radxa Cubie A5E players that sit beside mmWave radar sensors in malls and hospitals. Each unit decides locally which 4K advertisement to show, but all content, rules, and performance data must flow through a central cloud service that can grow from a handful of screens to thousands without a rebuild. What I need built is the production-grade cloud layer and its companion web dashboard. Core platform requirements • Microservice-oriented or similarly modular architecture that can scale out horizontally as new venues come online. • Low-friction onboarding for additional edge devices (secure registration, token refresh, OTA update support). • Event pipeline that ingests real-time trigger data from devices, records impressions, and hands off the correct creative with sub-second latency. • High availability and fault tolerance baked in (container orchestration such as Kubernetes/EKS/GKE is acceptable; serverless patterns are fine if they still allow persistent WebSocket/MQTT connections). Dashboard must expose • Real-time analytics: impressions, dwell-time estimates, trigger frequency, device bandwidth usage. • Ad scheduling that lets a Content Manager upload 4K creatives, tag them to campaigns, and set time/day or rule-based playback windows. • Device health monitoring: online/offline status, CPU temp, storage, radar heartbeat, and remote reboot/update controls. User roles • Administrator – full system control, user management, deployment parameters. • Content Manager – campaign creation, creative upload, schedule edits, analytics read-only. Security & compliance JWT or OAuth2 authentication, TLS everywhere, audit log retention, and role-based access must be implemented from day one. GDPR-friendly data handling is expected; no personal data is captured, only anonymous counts. Preferred tech stack Open to Node.js/TypeScript, Go, or Python for the services; React or Vue for the dashboard; PostgreSQL or Timescale for structured data; Redis/Kafka for queues and pub-sub. Feel free to suggest an alternative if it maintains the scalability priority. Deliverables 1. Infrastructure-as-code templates (Terraform, Pulumi, or similar) that spin up the entire backend. 2. Source for all services, documented and unit-tested. 3. Responsive web dashboard matching the feature list. 4. API & schema documentation. 5. Deployment guide plus a brief hand-off session. Acceptance criteria will be a working demo with three simulated edge devices triggering ads, live metrics visible on the dashboard, and the ability to push a new campaign without downtime. If this aligns with your expertise in distributed systems, edge-to-cloud message flows, and rich admin UIs, let’s set up a short technical chat to confirm approach and timeline.