The industrial edge platform that runs any payload.
Run any containerized or VM payload on secure, edge-first industrial infrastructure. No cloud dependency. No vendor lock-in. EmberNET is a platform, not a single product: the operating system, the zero-trust network, the console and the apps, working as one from the Industrial PC on your machine to one screen for every site.
Industrial PC. Velasea industrial PCs, tested and validated for EmberNET, on x86-64 or ARM64. Rack it, power it, and it enrolls.
EmberRTOS. EmberNET’s own immutable OS, with a real-time kernel on a switch: 23 µs worst-case wake-up over a 24 hour soak.
EmberNET Endpoint. Enrolls the machine and carries its tunnels. Nothing at the plant listens for an inbound connection.
Orchestration. A small Kubernetes at every site, updated centrally, so an app restarts itself instead of waiting for a truck roll.
Apps. CODESYS, Ignition Edge, Node-RED, databases and monitoring, deployed from the App Store to the node you choose.
EmberFLUX. The zero-trust overlay. Access is by identity, connections go out on 443 only, and there are no open ports at the plant.
EmberCORE. One console for every site: role views, tenant scope, the App Store, operations and an exportable audit trail.
Your people. Operators, engineers and admins sign in with their own company accounts and see only their own sites.
Worst-case real-time latency on EmberRTOS, held through a 24 hour soak.
Wake-ups measured in that soak. Not one arrived later than 23 µs.
EmberCORE releases shipped between February and September 2026.
Austin to Cleveland: a CODESYS download to a virtual PLC, over EmberNET.
See everything. Deploy in days. Lock it down.
EmberNET sits at the edge, right on your floor, not in someone else’s cloud. It connects to your existing PLCs, HMIs and SCADA systems without disrupting running processes.
You get live operational visibility across every line and facility, AI-driven anomaly detection before failures hit production, and a zero-trust security layer with post-quantum encryption that keeps your network dark to the outside world.
No rip-and-replace. No months-long rollout. No exposed attack surface.
Everything a plant needs at the edge, built to work together.
Each part of EmberNET does one job well, and all of them share one identity, one network and one console. That is what lets a new site go live in days instead of months.
Industrial PCs
Velasea hardware, tested and validated for EmberNET, on x86-64 or ARM64. The box you order is the box that enrolls.
EmberRTOS
EmberNET’s own immutable edge OS, with a real-time kernel on a switch and auto-rollback patching.
EmberFLUX
Zero-trust networking and a maintenance tunnel. No exposed ports, no VPN configs, secure by default.
EmberCORE
One console for every site and every app: role views, tenant scope, the App Store and the audit trail.
App Store
CODESYS, Ignition Edge, Node-RED, databases and monitoring, deployed to the node you choose.
EmberForge
A web-based IDE for building applications on EmberNET, without leaving the browser.
Flare AI
A setup assistant for Ember infrastructure, built into the platform.
EmberOPS
ERP and MES for manufacturing operations, delivered as software on the platform.
A control loop is only as good as its worst wake-up.
EmberRTOS runs a real-time kernel when you switch it on. We measured it the way control engineers do: worst case, under load, for a full day. It stayed at 23 µs, four to nine times inside the 100 to 200 µs band an industrial control loop needs.
Worst-case wake-up latency, measured on a Raspberry Pi 5 (Cortex-A76)
Worst case, across every thread.
Wake-ups measured, and not one of them late by more than that.
Continuous, under load, with the board running from 30 °C up to about 60 °C.
Average, 1 µs on every thread Worst case
Measured with cyclictest: three SCHED_FIFO priority-99 threads, one per real-time core, with the stress
load pinned to the housekeeping core. That is the isolation working as designed, not an all-core stress test.
The 5 minute run gave 12 µs; the tail grew to 23 µs over 24 hours, which is exactly why the soak is the number
that counts.
Program a PLC in Cleveland from a desk in Austin.
Fireball Industries is a CODESYS partner, and CODESYS has approved us as a CODESYS Technology Partner, with the announcement to follow. The proof is already running: an engineer in Austin, Texas downloaded the PLC application from the CODESYS IDE to a virtual PLC on an Industrial PC in Cleveland, Ohio, over EmberNET. That project is deployed with the client today.
No VPN, no port forwarding and nothing exposed on the plant network. Your engineers work from wherever they are, and your controllers stay dark to everyone else.
A CODESYS download from Austin, Texas to a virtual PLC in Cleveland, Ohio
- 01 Build
The engineer builds the project in the CODESYS IDE in Austin. Zero errors.
- 02 Connect
The IDE reaches the Cleveland node at its EmberNET address. No VPN, and no inbound port opened at the plant.
- 03 Download
The PLC application goes down to the virtual PLC on the Industrial PC: CODESYS Control for Linux ARM64 SL.
- 04 Run
The application runs on the client’s floor, and the project is deployed there today.
An animation of what happened. The route, the software and the result are real; the map is schematic and the timing is not to scale. About 1,200 miles, and nothing on the plant network was exposed to get there.
Velasea industrial PCs, validated for EmberNET.
Velasea is EmberNET’s hardware partner. Every system in the Velasea collection for Fireball Industries is tested and validated for full compatibility with EmberNET, so the box you order is the box that enrolls.
EmberNET works with the platforms you already trust.
It runs on standard x86-64 and ARM64 industrial hardware.
Ready to transform your factory floor?
Get started with EmberNET today. Tell us what runs on your floor and an engineer will show you how EmberNET would run it.