Platform Architecture
How EmberNet is put together, from the equipment on the floor up to the console.
The layers
EmberCORE
EmberCORE is the console and the API behind it. It keeps the record of every organization, its users and roles, its sites and devices, and its apps. It reads your equipment, watches your network gear, and delivers alerts by bell, email, phone push, and webhook.
Edge runtime
Edge nodes run your App Store apps and the platform services next to the equipment, restart what fails, and keep a site's workloads running on its own hardware. Small sites run a single node, and larger ones run several so workloads survive losing a machine.
Nodes can run EmberRTOS, Fireball's own immutable operating system, which updates as a whole and rolls back if an update fails. The immutability is the point. An edge node sitting in a plant for three years with nobody logging into it should be in a known state, and a failed update should roll back rather than leave a half-configured host that nobody can diagnose remotely.
Storage on edge nodes is provided by Cinder, which keeps copies on other nodes where a site has more than one.
Data path
- Collectors in EmberCORE read devices in the protocols they already speak, over Flux when the device has a Flux service. They are read only and touch nothing they were not configured to read.
- Edge apps such as HotLoop, Ignition Edge, and Node-RED process data next to the equipment, and keep working on site.
- Messaging runs through AnvilMQ, the platform's MQTT broker, with each organization kept to its own data.
- Time-series storage keeps the history.
Storage tiers
| Tier | Location | Retention | What it's for |
|---|---|---|---|
| Hot | Edge node | 7 days | Live dashboards, alerting |
| Warm | Edge cluster | 30 days | Historical analysis, trending |
| Cold | Cloud storage | 365 days | Compliance, long-term analytics |
These are the defaults. Hot retention is the tier that scales with deployment size; see System Requirements. Changing them is covered in Configuration Reference.
Networking
The fabric uses two layers for two different jobs.
Flux is the primary transport. Access is granted between cryptographic identities rather than between addresses, it uses outbound HTTPS only so it survives restrictive networks, and it carries remote app interfaces back to your browser.
ArcNet is the encrypted network underneath it, giving nodes plain IP reachability to each other. Its traffic rides Flux.
Both share the same properties:
- No exposed ports. Nodes dial out; nothing dials in.
- Mutually authenticated. Both ends prove who they are.
- Identity-based. Access follows identity, not IP, so there is no flat network to scan.
- Automatic. Nodes join on enrollment and reconnect through outages and address changes on their own.
Protocols
EmberCORE's collectors read OPC UA, Modbus TCP and RTU over TCP, S7comm, EtherNet/IP, MTConnect, FINS, MELSEC/SLMP, BACnet/IP, DNP3, and 3D printer APIs, and read PROFINET, EtherCAT, HART, CANopen, and FANUC equipment through the controllers and gateways in front of them. Network equipment is polled over SNMP v2c and v3. See Device Connectivity.
EmberBurn republishes tag data across a further set, including Sparkplug B and Kafka.
Deployment models
| Model | How nodes join | Typical customer |
|---|---|---|
| Fireball-managed | Nodes join a cluster Fireball manages | Standard deployments |
| External | The customer's own cluster connects to the platform | Enterprises running their own infrastructure |
The external model is covered in External Tenants.
Availability
- Failover. On a multi-node site, workloads move to healthy nodes.
- Replication. On a multi-node site, Cinder keeps copies of your data on different nodes, which is why three nodes is the recommended minimum.
- Working through outages. Apps on edge nodes keep running when the site loses its connection, and apps built for it, such as Ignition Edge with store and forward, catch up when the link returns.
- Alerts on the platform itself. A site that stops answering, or storage that is at risk, raises an alert instead of going quiet.
Next steps
- Multi-Tenancy: how tenant isolation works
- System Requirements: hardware and OS prerequisites
- Zero-Trust Networking: the security model in depth