Real-time telemetry & analytics
Edge preprocessing sends clean signals to the cloud for dashboard decisions.
Desmond Li
NEOX R&D core · Ph.D.-led algorithms
First-gen chip: architecture and core algorithms led by Dr. Li’s team.
Dr. Li leads NEOX chip, Mattock models, and media-agent R&D alongside NEOXGEO GEO delivery.
Browse NEOX TechNEOX Gen‑1 chip
Hardware as a service: wire machines to cloud operations
Built-in connectivity and remote control turn every machine into an observable, commandable node inside SaaS and CRM.
NEOX-chip · edge node
onlinetelemetry12.4k/s
latency12ms
oobarmed
Illustration: edge and cloud control planes handshake; actual behavior depends on your network and security posture.
Core capabilities
Chip powers hardware; cloud powers operations
Edge-to-cloud uplink and cloud-to-edge commands: telemetry, alerts, power, and OTA on one governed channel.
Remote command (power / reboot)
Hard reboot and power policies remotely—less onsite downtime.
Deep SaaS & CRM integration
Standard APIs map each device to a CRM node—customers and tickets in one loop.
Full lifecycle: ingest to remote ops
Console mockup; beams show data uplink and command return.
NEOX Chip
Hover the "Remote reboot" control—status LEDs animate
Device console
Device_ID: #001
Power Consumption
120W
Edge uplink latency (illustrative)
12ms
Run curve (illustrative)
Digital twin entry for every machine
Device, tablet/CRM console, and dedicated uplink—manage equipment from phone or laptop.
- Millisecond-class reporting; thresholds can trigger alerts.
- Cloud policies sync with tickets and workflows.
Operations one click away
Dashboards show online state, anomalies, and reboot needs—inside your SaaS workflow.
Low latency, hardware-grade authority
CRM/SaaS never talks to machines directly—commands go through the chip control plane; OOB keeps management when needed.
Physical layer (machine)
Sensors, power, motors, and on-site networking.
Control layer (NEOX Chip)
Command parsing, crypto, OOB, low-latency path, edge preprocessing.
Business layer (CRM / SaaS)
Assets, contracts, tickets, analytics—APIs turn devices into operable nodes.
From the floor to the cloud—and back
Ingest → cloud → SaaS/CRM decisions → remote control (power, reboot, OTA).
- 01
Collect & report
Sensors and state over an encrypted uplink.
- 02
Cloud analysis
Dashboards, thresholds, alerts, asset views.
- 03
Decisions & tickets
Rules trigger ops or automation.
- 04
Reverse control
Authorized reboot, power, OTA.
Technical highlights
Out-of-band (OOB) remote management
Separate management plane—ops even when the primary path fails.
Low-latency command path
Optimized control path from click to execution.
Hardware-rooted security
Root of trust close to metal—harder to forge commands.
Every device is an operable cloud node
From chip to link to dashboard—one story for engineering and sales.