Skip to main content

App Store

The EmberNet App Store deploys industrial applications onto your edge nodes: PLC runtimes, SCADA gateways, flow engines, historians, rules engines, and monitoring. Every app is packaged by EmberNet, which installs it, labels for your organization, and connects to EmberCORE, so there is nothing to wire up by hand.

How it works​

  1. Open the App Store from EmberCORE. Admins and Engineers can deploy apps.
  2. Find the app. Search by name, description, category, or publisher, filter by category and publisher, and sort by name, category, or publisher. Your filter choices are remembered in your browser.
  3. Choose the node to run it on.
  4. Deploy. EmberNet installs the app on that node for your organization.

Running your apps​

Deployed apps appear in the App Store's Running Apps tab. What you can do with one depends on the app:

  • Apps with a web interface open inside EmberCORE, and can be popped out into their own browser tab. Apps with more than one interface offer a picker.
  • Apps without a web interface, such as brokers and PLC runtimes, offer a shell into the app instead.
  • Headless services, such as rules engines and exporters, show as running with nothing to open.

Apps deployed to a remote site are reached over Flux, so they open exactly as local apps do.

n8n, Sorba SDE, Grafana, ChirpStack, Home Assistant, and Portainer only work at their own app address, not through EmberCORE's built-in proxy. Their interfaces still open inside EmberCORE, from that address. If your EmberCORE deployment has no app subdomains, the App Store says so before you install any of them.

One instance per node, with exceptions​

Most apps run as a single instance per node. You can still put them on as many nodes as you like; you just cannot stack two copies on one node. These can be deployed more than once to the same node:

  • The CODESYS runtimes, Edge Gateway, and safety apps
  • Node-RED
  • HotLoop Flow
  • Ignition Edge

CODESYS Automation Server is one per cluster, because the vendor's software is built to run once. The App Store does not offer a second.

The catalog​

Each app has its own page with what it does, when to use it, and how it runs on EmberNet.

CategoryApps
Analytics and MLSORBA Cloud (not offered today), Sorba SDE
Automation and WorkflowHome Assistant, IPLUSMOBOT Cloudia, n8n, Node-RED
Business AppsHearth
Business RulesGoRules BRMS, GoRules Engine, GoRules ZEN Engine
CODESYSCODESYS: Automation Server, Control for Linux SL, Control for Raspberry Pi SL, Edge Gateway for Linux, Safe Time Provider for Linux, Virtual Control for Linux SL, and Virtual Safe Control SL
DatabasesGarage, InfluxDB, PostgreSQL, SQLite, TimescaleDB
EmberNet PlatformPortainer (Fireball only)
EmberRTOSMicroVM: Headless and Headless RT
HotLoopHotLoop Cascade, HotLoop Edge, HotLoop Edge Relay, HotLoop Flow, HotLoop for CODESYS, HotLoop Gateway, HotLoop IoT
IgnitionIgnition, Ignition Cloud, Ignition Edge
Industrial ConnectivityChirpStack, EmberBurn, FUXA
MessagingMosquitto
MonitoringAlertmanager, Grafana, Grafana Loki, Node Exporter, Prometheus, Telegraf
NetworkNetwork Probe

Your organization's catalog can be limited to a chosen set of apps, so you may see fewer than this.

AnvilMQ, in the EmberNet Platform category, is in the App Store for Fireball's platform role only. Fireball deploys and runs it as one broker per site, and tenants neither see it nor install it.

Portainer, in the EmberNet Platform category, is in the App Store for Fireball's Global Command role only. It has broad access to the site, so Fireball operates it, and tenants neither see it nor install it.

One app has a page but is not in the App Store today. SORBA Cloud has been withdrawn from the catalog. Sorba SDE is still available.

Next steps​