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 a packaged chart that EmberNet installs, labels for your organization, and connects to EmberCORE, so there is nothing to wire up by hand.
How it works
- Open the App Store from EmberCORE. Admins and Engineers can deploy apps.
- 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.
- Choose the node to run it on.
- Deploy. EmberNet installs the app on that node for your organization.
Some apps are listed with Contact Sales instead of Deploy. Those are Fireball products that you buy by talking to us; see Fireball products.
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 port 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 charts
- Node-RED
- HotLoop Flow
- Ignition Edge
CODESYS Automation Server is one per cluster, because the vendor's software owns fixed namespaces. 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.
| Category | Apps |
|---|---|
| CODESYS | CODESYS: Control for Linux SL, Control for Raspberry Pi SL, Virtual Control for Linux SL, Edge Gateway for Linux, Virtual Safe Control SL, Safe Time Provider for Linux, and Automation Server |
| Ignition | Ignition, Ignition Edge |
| HotLoop | HotLoop Gateway, HotLoop Edge Relay, HotLoop Flow |
| Automation and Workflow | Node-RED, n8n, Home Assistant |
| Business Rules | GoRules BRMS, GoRules Engine, GoRules Zen Engine |
| Databases | InfluxDB, TimescaleDB, PostgreSQL, SQLite |
| Messaging | Mosquitto |
| Monitoring | Prometheus, Alert Manager, Node Exporter, Grafana, Grafana Loki, Telegraf |
| Analytics and ML | Sorba SDE |
| Industrial Connectivity | EmberBurn, ChirpStack |
| Network | Network Probe |
Your organization's catalog can be limited to a chosen set of apps, so you may see fewer than this.
AnvilMQ and Ignition Cloud are not App Store apps. Fireball deploys and runs them as platform services.
Portainer, in the EmberNet Platform category, is in the App Store for Fireball's Global Command role only. It runs with cluster-admin rights, so Fireball operates it, and tenants neither see it nor install it.
Fireball products
These Fireball products are listed in the App Store with a Contact Sales button. They are not self-service installs; Fireball sets them up with you.
| Product | Category | What it is |
|---|---|---|
| IRON Suite | Business Apps | CRM, marketing automation, live chat, and forms behind one shell |
| War Horse | Situational Awareness | Situational awareness: a server and native clients that sign every CoT event |
| Skald | Business Apps | A blog and social publishing desk: write once, publish to the blog and every channel |