Introduction
The Everynet platform is designed to operate on a massive scale and separates Network Server (NS) functionality from Radio Access Network (RAN) management.
All platform features are fully extensible via API, as described on this site, and convenient management portals are available based on those APIs.
- The NS portal is available at: ns.eu.everynet.io
- The RAN portal is available at: ran.eu.everynet.io
where .eu. specifies a shared European instance. Other regions (e.g. us) and other private instances are available.
To be able to conveniently manage very high numbers of objects (devices, filters, connections, users, keys), the portals and underlying servers include extensive search and filter capabilities. Filters provide a powerful mechanism for routing data between sets of devices and connections to external application servers. By filtering tags, EUIs, gateways and message types, it is possible to establish complex relationships between devices and applications, even share data from one device to multiple applications.
The Everynet Network Server (NS) сontains two different interfaces: RESTful and WebSocket-based. These interfaces are designed for the following purposes:
- Server Managment API - RESTFul API for account management, device provisioning, server configuration, filter, keys, users provisioning, etc...
- Data Streaming API - WebSocket-based API to stream messages and debug data between the NS and the Application Server (AS).
- Adapters - Act as a bridge between the NS and 3rd party services like: MQTT, PubNub, HTTP, etc...
- Examples - Application Server (AS) examples implemented for different APIs.