EmberNET
Sign in Request a demo
Platform EmberCOREEmberRTOSEmberRTOS DesktopEmberFLUXEmberForgeFlare AIEmberOPSRuns anything
Solutions Discrete manufacturingProcess manufacturingEnergy and utilitiesWater and wastewaterBuilding materials and heavy industryAgriculture and motorsportAI solutionsWhite papers
Technical DistributionLicensingProduct stackModulesAdd-onsAPI and integrations
Partners CODESYSVelasea hardwareOEMChannel partnerCertified integratorPlatform partner
Compliance
Pricing
Company About EmberNETApp StoreWeb StoreJournalContact
Sign in Request a demo
Technical ยท API and integrations

Connect anything. Replace nothing.

EmberOPS exposes versioned REST APIs across every module and integrates with the industrial protocols, EDI standards, e-commerce channels, and enterprise systems already in your stack.

Versioned REST API

A stable API boundary. HMI upgrades can't break it.

Every module exposes a versioned REST API. The contract is explicit: when you upgrade Ignition or swap your HMI platform, the MES and WMS don't move.

New versions (v2, v3) are additive. v1 clients don't break on a v2 deploy.

Your HMI talks to the versioned REST API, and the API talks to the EmberOPS modules. Upgrading the HMI never reaches past the API.
Your HMIIgnition, Node-RED, React, CODESYS WebVisu
Versioned REST APIThe contract. New versions are additive.
EmberOPS modulesEmber MES, Ember WMS, Ember EHS
API surface

Module API endpoints

ModuleAPI surface
Ember MES /api/method/mes_core.api.v1.*: about 26 endpoints covering production, downtime, labor, andon, traceability, SPC, documents, and settings
Ember WMS /api/method/wms_core.api.v1.*: inbound, outbound, inventory, task engine, dock, and the manufacturing bridge
Ember EHS The automatic REST API that Frappe generates for every DocType: incidents, permits, CAPA, audits, and training

View modules

Integrations

What EmberOPS connects to

Industrial protocols

OPC-UA. MQTT. Built for the floor.

Shop-floor hardware (PLCs, scanners, conveyors, and AMRs) connects to EmberOPS through Ignition Perspective or Node-RED. Both sit outside the API boundary and communicate over industrial protocols. EmberOPS doesn't embed a PLC driver; it gives Ignition and Node-RED a stable REST target to push to and pull from.

HMI and SCADA

Ignition. Node-RED. React.

EmberOPS ships screen templates for Ignition Perspective and React, and both consume the same versioned REST APIs. Ignition is its own product: you bring your license, and we provide the integration layer. Node-RED flow templates handle MQTT-to-REST bridging and event routing. CODESYS WebVisu connects via the versioned REST API.

E-commerce

Sell everywhere. Fulfill from one place.

The emberwms_channels sub-addon connects EmberOPS to e-commerce platforms. Orders flow in and fulfillment flows out, through the same WMS task engine as everything else. Supported: Shopify, Amazon (FBA and FBM), eBay, and WooCommerce.

Microsoft 365

M365: one add-on, full integration.

The emberops_graph_api add-on connects any EmberOPS site to M365 through a single Azure AD app registration: Azure AD and Entra ID SSO, Teams notifications from EHS incidents and MES andon alerts, Outlook calendar sync, SharePoint document storage, and Power BI data push.

Shipping

Multi-carrier shipping built into WMS.

Ember WMS includes rate shopping and label generation across multiple carriers via EasyPost, ShipEngine, and native carrier drivers. No third-party middleware required.

EDI

EDI via the WMS sub-addon

The emberwms_edi sub-addon handles EDI over VAN or AS2.

Transaction setDocument
X12 856 ASN
X12 940 Warehouse Shipping Order
X12 944 Warehouse Stock Transfer Receipt
X12 945 Warehouse Shipping Advice

See how it all comes together.

Request a demo to see the full integration stack in action.

Request a demo