Skip to main content

System Requirements

What an EmberNet edge node needs, and how to size a deployment.

Operating system​

Edge nodes run EmberRTOS, Fireball Industries' own immutable Linux distribution. It is not a supported configuration to install the platform onto an arbitrary Linux distribution; the OS and the platform are provisioned together.

EmberRTOS 0.1.11 comes in three editions that share one base and differ in kernel and screen:

EditionKernelRuns onUse it for
EmberRTOS Headless RTReal-timex86_64, Raspberry Pi 4 and 5Deterministic control loops with a bounded latency requirement
EmberRTOS HeadlessGeneral-purposex86_64, Raspberry Pi 4 and 5Everything that isn't hard real-time
EmberRTOS DesktopGeneral-purposex86_64Operator stations with a local screen

The real-time kernel is an edition choice, not a separate product: Headless RT boots it by default and keeps the general-purpose kernel beside it. The Raspberry Pi images are described on EmberRTOS on the Raspberry Pi, including which boot media work on which board.

Hardware​

Minimum, single node​

ComponentRequirement
CPU4 cores, x86_64 or ARM64
RAM8 GB
Storage128 GB SSD
Network1 Gbps Ethernet
ComponentRequirement
CPU8 or more cores, x86_64
RAM16 to 32 GB
Storage256 GB or more, NVMe
Network1 to 10 Gbps Ethernet, bonded where available
Nodes3 or more for replicated storage

Three nodes is not an arbitrary recommendation. Cinder keeps three copies of your data by default, and three copies on a two-node site can never be fully protected. See Storage.

Storage disks​

Give the platform a separate data disk from the OS disk. Capacity is expanded by attaching another data disk, never by growing the OS disk, and a node provisioned with a single disk is painful to expand later.

Validated platforms​

EmberNet runs on standard x86_64 and ARM64 industrial hardware. Validated vendors include Velasea (Iron Link series). Any hardware meeting the specifications above is supported.

For real-time workloads, validate the specific hardware rather than trusting the class. Measured worst-case latency varies more with firmware and chipset than with core count. EmberRTOS Headless RT covers what to measure.

Network​

RequirementDetail
Outbound HTTPSPort 443, for joining the fabric and cloud sync
DNSAbility to resolve public names
NTPTime synchronization, required for secure connections
Inbound portsNone
info

EmberNet requires no inbound firewall ports. Every connection is established outbound through the zero-trust mesh. See Zero-Trust Networking.

NTP is easy to overlook and produces confusing failures when it's wrong. A node with a badly drifted clock fails secure connections, which surfaces as enrollment or connectivity errors rather than as a time problem.

Browsers​

EmberCORE runs in Chrome 90+, Firefox 85+, Edge 90+, and Safari 14+. There is no client to install.

Sizing​

DeploymentDevicesShapeHot retention
Small1 to 50Single node, 8 GB RAM, 4 cores, 128 GB7 days
Medium50 to 5003 nodes, 16 GB RAM, 8 cores, 256 GB each30 days
Large500+5 or more nodes, 32 GB RAM, 16 cores, 512 GB+ each90 days

Hot retention is the number that moves with deployment size, because it is bound by local disk. Warm and cold retention are platform defaults and do not scale per node. See Configuration Reference.

Large deployments benefit from dedicating nodes to storage rather than mixing storage and compute on every node.

Next steps​