EmberOPS runs on Frappe v15 and ERPNext v15, kept at their upstream names, pinned to stable, never a dev branch. No mystery dependencies. No proprietary runtime.
EmberOPS is built on two well-known open-source projects:
version-15. Not forked. Framework changes in EmberOPS go through hooks, not patches.version-15. Treated as a private mirror, patches only when hooks can't reach.Both are kept under their real upstream names so anyone reading the codebase can match it back to the public projects.
| Component | Version |
|---|---|
| Python | 3.10 – 3.12 |
| Node.js | 18+ |
| Database | MariaDB |
| Frappe Framework | v15 (version-15 branch, pinned) |
| ERPNext | v15 (version-15 branch, pinned) |
Versions are pinned to the stable version-15 branch, not develop. An Ignition upgrade or a Node.js patch on your network does not pull in untested upstream changes.
EmberOPS does not bundle an HMI platform. The shop floor is your choice. EmberOPS provides the integration layer and the templates.
| Platform | What's included | Notes |
|---|---|---|
| Ignition Perspective | 3 screen templates | Ignition license required separately |
| React | UI templates included | Built-in shop-floor and warehouse views |
| Node-RED | Flow templates | MQTT-to-REST bridging and event routing |
| CODESYS WebVisu | REST integration | Connects via the versioned MES/WMS API |
All HMI platforms connect to EmberOPS through the versioned REST API. An Ignition upgrade cannot break the MES, the API boundary is the contract.
EmberOPS ships with a Docker-based local bench test stack. Production deployments run on standard Frappe bench infrastructure. EmberNet handles orchestration, updates, and version management for customers on the platform.
Each site installs only the apps it needs. There is no monolithic install, modules and add-ons gate at install time.
See available modules →