Frappe Framework v15
The backend engine: DocTypes, workflows, REST API generation, permissions, and the scheduler. Kept at upstream version-15 and not forked. Framework changes in EmberOPS go through hooks, not patches.
Technical ยท Product stack
Built on a foundation you can verify.
EmberOPS runs on Frappe v15 and ERPNext v15, kept at their upstream names and pinned to stable, never a dev branch. No mystery dependencies. No proprietary runtime.
The foundation
Frappe v15 and ERPNext v15.
EmberOPS is built on two well-known open source projects.
ERPNext v15
The ERP core: Items, BOMs, Work Orders, Stock, Quality, Accounts, and Employees. Kept at upstream version-15 and treated as a private mirror, with patches only where 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.
- Shop-floor UI Ignition Perspective, React, Node-RED, or CODESYS WebVisu
- The contract Versioned REST API
- EmberOPS EHS, MES, and WMS modules, plus add-ons
- ERP core ERPNext v15, upstream version-15
- Backend engine Frappe Framework v15, upstream version-15
- Runtime Python, Node.js, and MariaDB
On the platform, EmberNET handles orchestration, updates, and version management.
Runtime requirements
What runs it
| Component | Version |
|---|---|
| Python | 3.10 to 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.
HMI layer
The shop-floor UI layer
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 and WMS API |
All HMI platforms connect to EmberOPS through the versioned REST API. An Ignition upgrade cannot break the MES, because the API boundary is the contract.
Deployment
How it deploys
Each site installs only the apps it needs. There is no monolithic install: modules and add-ons gate at install time.
Local test stack
EmberOPS ships with a Docker-based local bench test stack.
Production
Production deployments run on standard Frappe bench infrastructure.
On EmberNET
EmberNET handles orchestration, updates, and version management for customers on the platform.
Ready to build on it?
Request a demo or get access through the EmberNET App Store.