Frequently Asked Questions
General
What is EmberNet?
The operating system of the modern factory: a complete, secure, multi-tenant solution for monitoring and automating industrial infrastructure, built to run at the edge. See Platform Overview.
Who makes EmberNet?
Fireball Industries, headquartered in Macedonia, Ohio.
How do I buy EmberNet?
Compare the plans on the pricing page, then request a demo or book a meeting with the EmberNet team. We size the rollout with you and get your first site running.
What industries does it serve?
Manufacturing, energy and utilities, water and wastewater, building automation, oil and gas, and any other operation that runs on industrial equipment.
Is it cloud-only?
No. EmberNet runs on hardware at your site. You can run it on your own premises, in a hybrid setup, or have us manage it for you.
Deployment
What hardware does it run on?
Standard x86_64 or ARM64 industrial hardware. Velasea is one validated vendor. See System Requirements.
What operating system does it need?
Edge nodes run EmberRTOS, Fireball Industries' own immutable Linux distribution. You don't install EmberNet onto an existing Linux distribution; the OS and platform are provisioned together.
Do I need three nodes?
For replicated storage, yes. Cinder keeps three copies of your data by default, and three copies on a two-node site can never be fully protected. Single-node deployments work fine for small sites, but understand that you have no replication.
Does it require internet access?
Edge nodes need outbound HTTPS for joining the fabric and cloud sync. The platform keeps operating locally through an outage and reconciles when the link returns.
Security
Does it require a VPN?
No. The zero-trust fabric removes the need for a site-to-site VPN. See Zero-Trust Networking.
Are any inbound firewall ports required?
None. All connections are outbound.
Is there an EmberCORE password?
No. Sign-in is delegated entirely to your identity provider through SSO, and your identity there determines your role and which tenants you can see. See SSO Integration.
How are certificates managed?
Issued, renewed, and revoked automatically by the platform.
Data
What protocols are supported?
SNMP, plus sixteen industrial protocols. Eleven are read natively: OPC UA, Modbus TCP, BACnet/IP, EtherNet/IP, S7comm, MQTT and Sparkplug B, MTConnect, FINS, MELSEC/SLMP, DNP3, and 3D printer APIs. Five more read through a gateway or controller: PROFINET, EtherCAT, HART, CANopen, and FANUC. See Connectivity.
How long is data retained?
Defaults are 7 days hot, 30 days warm, and 365 days cold. Hot retention scales with deployment size. See Configuration Reference.
Can I export data?
Yes, via CSV, the REST API, or streaming over MQTT and webhooks.
EmberCORE
What browsers are supported?
Chrome 90+, Firefox 85+, Edge 90+, and Safari 14+.
Can I build custom dashboards?
Not in the console itself. EmberCORE is an operations console rather than a charting tool: you choose which live metrics appear in the context strip and how each is drawn, but there is no drag-and-drop chart builder.
For custom time-series charting, deploy Grafana from the App Store. It opens inside the console and reads the same data.
Alerting
Can I write my own alert rules?
Not as a tenant. The alert conditions are built in, so baseline coverage needs no configuration to work. Alert rules are one platform-wide set that Fireball staff manage under Monitoring, then Alert rules. What you configure is where alerts go. See Alerts & Notifications.
Does it support SMS or PagerDuty?
SMS is not built in. Alerts reach you four ways: the bell in EmberCORE, email, a webhook, and phone alerts (Web Push for critical alerts, turned on per device). The webhook posts JSON, so it can feed PagerDuty, Slack, Teams, or any system that takes a JSON POST.
Support
How do I get help?
Where do I report issues?
Email the helpdesk at helpdesk@fireballz.ai. See EmberNet Support for what to include.