About NereidAI¶
The name¶
"Nereid" is simply the mascot name we chose — it carries no hidden or particularly deep meaning. In Greek mythology, the Nereids are the spirits of the sea (海之精灵), daughters of Nereus. We liked the image, so we made it the project's mascot and the shared prefix for every product.
What the mascot stands for¶
Picture a spirit swimming through an ocean of data:
- navigating the sea of data — finding a path through the devices, models, and pipelines of an AIoT system;
- helping users find their way — turning a fragmented edge-to-cloud stack into one clear, closed loop;
- spotting the hidden reefs — vendor lock-in, mandatory cloud dependence, data leaving the customer perimeter, and models that never make it to the field.
The reefs are exactly what the platform is designed to steer around.
Our mission¶
Democratize AIoT by integrating edge and cloud workflows into one seamless closed loop — low-latency edge inference, privacy-preserving operations, and automated model monitoring, all in a single platform.
In practice that means a small team can keep turning its own business data into models that run on its own field devices: data never has to leave the customer's perimeter, there is no mandatory cloud, and no single silicon or edge vendor is baked into the platform.
How the family is named¶
Every product shares the Nereid prefix; the suffix says what it does:
| Name | The suffix suggests |
|---|---|
| NereidSphere | the sphere that holds the suite together — portal, gateway, glue |
| NereidIdentity | identity and access |
| NereidLink | linking devices into the platform |
| NereidForge | the forge where models are made |
| NereidHorizon | reaching the distant horizon of remote edge nodes |
| NereidEdge | the edge, on field gateways |
| NereidInference | running model inference on edge gateways |
The commercial industry solutions follow the same spirit — NereidFactory, NereidSentinel, NereidMedical. See Naming & abbreviations.
What we believe¶
- Private by design — fully air-gapped operation, no mandatory call-home.
- Open source, commercially supported — Apache-2.0 community edition; enterprise LTS and turnkey delivery under commercial terms.
- Loosely coupled products — every product stands alone; the suite layer only federates them. See Standalone by default.
- Vendor-neutral contracts — no hard dependency on one edge stack or one silicon vendor.