Neyos Server

NEYOS servers handle the reception, decoding, storage and distribution of messages from field devices.

---

Architecture

The NEYOS infrastructure relies on a redundant cloud deployment within European data centers. All services (processing, database, message queues) are continuously monitored and scaled for load management. Production, pre-production and test environments are isolated.

Availability and redundancy

The target annual availability is 99.9%. Each critical service is replicated across multiple availability zones. Data is synchronized in real-time and automatically fails over in case of hardware incident. Backups are daily and validated through restoration.

In case of network unavailability, trackers retain their messages in internal memory and then retransmit them once the service is operational again. The server preserves the chronological order of insertion.

Historization and retention

Each message is recorded with UTC timestamp and unique identifier. Data is retained for 2 months by default, then archived or deleted according to the customer's policy.

Security

Flows are encrypted and validated at the application level before processing. Access is restricted to authorized sources and authenticated by API key. All interactions are logged and timestamped. Hosting is located in the European Union.

Performance

The architecture is optimized for real-time processing:

average latency < 1 s in cellular transmission,
simultaneous processing of several thousand messages per second,
continuous load monitoring.

Maintenance and supervision

Supervision is continuous, deployments are performed without service interruption. Each update is automatically validated after deployment. Alerts are processed in real-time and service recovery is automated.

Integration in the NEYOS ecosystem

The servers are the convergence point between trackers deployed in the field and software interfaces. They receive messages from partner networks, validate them, then transmit them:

to the NEYOS platform for simple availability,
or to the API / Webhooks for integration into external systems.

Message traceability is maintained throughout the process.