OpenMES Alternative: When Free Open-Source MES Isn't Actually Free

Choosing an OpenMES alternative starts with an honest look at OpenMES itself: a free, self-hosted, open-source manufacturing execution system that many small manufacturers can run well. The right alternative, if you need one at all, depends on who will install, host, adapt and support the system once operators rely on it every shift.

The practical problem is rarely the licence fee. It is the gap between a capable codebase and a shop floor where every job, operation and delay is recorded reliably. This guide explains what OpenMES is, when it fits, and how the main alternative types compare on one shared hypothetical scenario, so you can judge fit, limitations, integrations and total cost side by side.

Shop floor tracking only works when it suits the people and machines on the floor. Illustrative photograph, not an OpsMavix project.

Image credit: Zoshua Colah, Unsplash License. No edits.

Key Takeaways

• OpenMES is a self-hosted, open-source MES with an AGPL-3.0 core and optional commercial licences, support and partners.
• It fits best when someone in the business can own hosting, backups, updates and floor support.
• The licence is free, but implementation, integration and ongoing administration still cost time or money.
• Alternatives include a supported OpenMES deployment, packaged shop floor software, a focused custom application or a full ERP.
• On a shared hypothetical scenario, three-year totals can be close, so fit and support model often decide.
• Pilot any option on real jobs, real devices and a dropped network connection before committing.

In this guide:

• 1. Understand What OpenMES Is
• 2. Know When OpenMES Fits Well
• 3. See Where Self-Hosted Effort Lands
• 4. Map the Alternative Types
• 5. Compare Total Cost on One Shared Scenario
• 6. Compare Fit Limitations and Integrations
• 7. Ask the Right Questions Before Choosing
• 8. Pilot on Real Jobs Before Rollout
• Frequently Asked Questions
• How OpsMavix Can Help

1. Understand What OpenMES Is

The project and its licence

The current OpenMES project is published on GitHub in the Mes-Open/OpenMes repository and on its own site, getopenmes.com. The README describes it as a “self-hosted, open-source MES” aimed at small and mid-sized manufacturers, with woodworking, metal fabrication, plastics and assembly shops named as targets.

The core is licensed under AGPL-3.0, and the README states that the modules folder uses the Academic Free License 3.0. It also says commercial licences are available for partners who cannot accept AGPL obligations, alongside OEM, hosted and support offerings. The project site credits Nice Code as the company behind it and lists an Enterprise tier without a published price.

Do not confuse it with an older OpenMES project on SourceForge, a Java and JBoss effort marked as “Planning” whose page was last updated in 2016. Search results mix the two.

What it does, according to its own documentation

As checked in October 2026, the README and project site describe:

• Work orders across production lines, batch production and reusable process templates
• Drag-and-drop Gantt scheduling with daily, weekly and monthly views
• Step-by-step operator guidance on touch screens, delivered as a progressive web app that the README says works offline with queued actions
• Issue reporting with Andon-style blocking of production for critical issues
• Role-based access for admin, supervisor and operator, plus audit logs
• A packaging module with EAN barcode scanning
• Machine data collection over MQTT, a documented REST API and CSV or Excel import from systems such as SAP, Odoo and Comarch
• OEE, downtime analysis and lot or serial traceability, which the project site lists alongside OPC UA and Modbus integration

It is built on Laravel and PostgreSQL and deploys with Docker Compose or install scripts. The README says “an old office PC is enough” to run it. A hosted “OpenMES Online” service is listed on the site as coming soon.

2. Know When OpenMES Fits Well

Good signs

OpenMES is a genuine option, not a straw man. It suits a business where several of these are true:

• Someone in-house is comfortable with Docker, Linux or Windows servers, PostgreSQL backups and application updates.
• The shop wants to keep production data on its own infrastructure.
• The workflow is close to what the product already models: work orders, lines, steps, issues and scanning.
• The team is willing to report bugs, follow the GitHub project and accept that open issues exist.
• Budget is tight, and staff time is genuinely available rather than assumed.

If you lack the technical skills but like the product, the project offers implementation partners and commercial support. That is a valid middle route and is costed separately in section 5.

Warning signs

Look harder at alternatives when nobody owns the server, when the floor runs night shifts with no technical cover, or when your process differs sharply from the product’s model. A heavily modified open-source system can become a custom application you maintain without the documentation a custom build would normally include.

For the wider question of whether you need an MES at all, read what a manufacturing execution system actually does.

3. See Where Self-Hosted Effort Lands

The work that remains when the licence is free

A free licence removes one cost line. It does not remove the work of running a production system:

Questions that expose the real effort

1. Who restores the database if the server disk fails on a Monday morning?
2. Who tests an update before operators see it?
3. Who maintains the link to accounting when either side changes?
4. Who documents local changes so the next person can support them?

If each answer names a person with time allocated, self-hosting is realistic. If the answer is “we will figure it out”, budget for a partner or consider another type.

4. Map the Alternative Types

Five approaches to shop floor tracking

Integration before replacement

Sometimes the right answer is not a new system. A connector between your accounting package and a simple floor capture screen may close the gap. Our guide to operational systems versus ERP covers that choice, and shop floor job tracking without an ERP shows the lightest version.

For published prices of packaged options such as Katana, MRPeasy and Fishbowl, see our manufacturing operations management software comparison. This post deliberately compares types rather than repeating vendor price lists.

Shared tablets are a common way to capture floor data, whichever system sits behind them. Illustrative photograph, not an OpsMavix project.

Image credit: ThisisEngineering, Unsplash License. No edits.

5. Compare Total Cost on One Shared Scenario

The hypothetical shop

Assume a hypothetical 30-person metal fabrication shop. It runs three work centres, has 12 operators sharing 6 floor tablets, and has 8 office or supervisor users who need logins. It wants live job status, time per operation and issue logging, with completed jobs passed to its accounting package. All figures below are hypothetical, exclude VAT and use an internal staff cost of £40 an hour. They are not quotes for any product.

Common to every option: 6 tablets at £300 each = £1,800.

Option A: self-hosted OpenMES, run in-house

• Licence: £0
• Server and backup drive: £1,500
• Tablets: £1,800
• Setup and configuration: 160 hours × £40 = £6,400
• Ongoing administration: 6 hours a month × £40 × 36 months = £8,640
• Off-site backup and remote access: £30 a month × 36 = £1,080
• Three-year total: £1,500 + £1,800 + £6,400 + £8,640 + £1,080 = £19,420

Option B: OpenMES with a paid implementation partner

• Licence: £0
• Partner implementation: £8,000
• Support contract: £250 a month × 36 = £9,000
• Hosting: £30 a month × 36 = £1,080
• Tablets: £1,800
• Internal time: 60 hours × £40 = £2,400
• Three-year total: £8,000 + £9,000 + £1,080 + £1,800 + £2,400 = £22,280

Option C: packaged cloud shop floor software

• Subscription: 8 paid users × £60 a month × 36 = £17,280
• Onboarding: £2,000
• Tablets: £1,800
• Internal configuration: 40 hours × £40 = £1,600
• Three-year total: £17,280 + £2,000 + £1,800 + £1,600 = £22,680

Option D: focused custom application

• Build: £15,000
• Hosting and support: £150 a month × 36 = £5,400
• Tablets: £1,800
• Internal time for requirements and testing: 40 hours × £40 = £1,600
• Three-year total: £15,000 + £5,400 + £1,800 + £1,600 = £23,800

What the numbers show

The spread between lowest and highest is £4,380, about 22.6% of option A (£4,380 ÷ £19,420). That is small relative to the uncertainty in each estimate. Now double option A’s ongoing administration to 12 hours a month: it rises by £8,640 to £28,060, the most expensive option in the table. The cheapest route on paper depends heavily on one assumption that is easy to underestimate.

A full ERP is left out of this table because it solves a broader problem than shop floor tracking. If finance, stock and purchasing also need replacing, compare it on that wider scope instead.

6. Compare Fit Limitations and Integrations

Side-by-side assessment

Read the limitations fairly

Every type has trade-offs. Packaged products bring tested features and documentation, and their vendors carry the maintenance. OpenMES gives you the code and control over hosting. A custom application fits closely but still needs maintenance and someone accountable for it. None is automatically cheaper or more flexible.

For the criteria that decide adoption on the floor, see how to choose a production tracking system.

7. Ask the Right Questions Before Choosing

Questions for any option

1. Show a job moving through three operations, including a pause and a rejected part.
2. Show what happens when the network drops mid-operation and returns.
3. Show how an operator logs in on a shared tablet.
4. Show how completed work reaches accounting, and how a failed transfer is fixed.
5. Show how we export all our data if we leave.
6. Name who supports the floor at 6am on a Monday.

Extra questions for OpenMES

• Which version will we run, and how are updates released and tested?
• Which features are in the AGPL core, and which need a commercial licence or partner work?
• If we modify the code, have we read the licence conditions or taken advice?
• Is the integration we need already supported, or will someone build it?

Extra questions for packaged and custom options

• How does price change as operators or sites are added?
• Which requirements are standard, configurable, or need development?
• What is the support response for a stopped floor, in writing?

8. Pilot on Real Jobs Before Rollout

Choose a representative pilot

Run one work centre for two to four weeks with real jobs, real operators and the tablets they will use. Include a rush order, a rework and at least one deliberate network outage. Compare the system’s job times with supervisor notes for the same jobs.

Pilot acceptance checklist

1. Operators can start, pause and finish an operation in a few taps.
2. Every job shows its current stage without walking the floor.
3. Setup time is recorded separately from run time.
4. Issues raised on the floor reach a named supervisor.
5. Offline entries are kept without duplicates after reconnection.
6. Completed jobs reach accounting or a reconciled export.
7. A database backup has been restored successfully at least once.
8. Someone other than the installer can support the system.

If the pilot passes, expand by work centre. If it keeps producing spreadsheets alongside the system, record where they appear; those workarounds are the real requirements. Our guide to building a production tracker you can trust covers what good data looks like, and factory management software build versus buy covers the wider decision.

Frequently Asked Questions

What is OpenMES?

OpenMES is a self-hosted, open-source manufacturing execution system for small and mid-sized manufacturers. Its repository and site describe work orders, scheduling, operator guidance, issue reporting, traceability and machine data collection, built on Laravel and PostgreSQL.

Is OpenMES free?

The core is free to use under AGPL-3.0, and the site says there are no licence fees for it. Hosting, setup, integration and support still take time or money, and the project offers an Enterprise tier and commercial support at unpublished prices.

Does OpenMES work offline?

The README says the operator interface is a progressive web app that works offline and queues actions. Test it on your own network, with your own devices, before relying on it.

What is the best OpenMES alternative?

It depends on the gap. If you lack technical staff, a partner-supported OpenMES deployment is the closest alternative. If your process matches a mainstream product, packaged software may fit. If your process is distinctive, a focused custom application may suit better.

Is packaged software cheaper than open-source MES?

Not necessarily. In our hypothetical scenario, the three-year totals were within £4,380 of each other, and doubling internal admin time made self-hosting the most expensive option. Model your own hours honestly.

Do I need an MES or simpler shop floor tracking?

Many smaller shops need live job status, time per operation and issue logging rather than full MES scope. Start with the decisions you cannot make today, then choose the smallest system that supports them. Our shop floor tracking software guide covers the core features.

What does the AGPL licence mean for my business?

AGPL-3.0 is a copyleft licence with conditions that matter if you modify and share or serve the software. Read the licence or take advice before modifying the code. The project states that commercial licences exist for those who cannot accept AGPL obligations.

Can OpsMavix build a production tracking system?

Yes. OpsMavix can build focused applications or a full custom ERP, and can configure or integrate suitable existing tools where those approaches fit the requirements.

How OpsMavix Can Help

OpsMavix can review how jobs, times and issues move through your floor today, then help you decide whether OpenMES, packaged software, an integration or a custom system fits best.

That may mean building a manufacturing production tracking system, connecting floor capture to inventory automation or giving managers a project operations dashboard across jobs.

Contact OpsMavix with one recent late or overrunning job, the records behind it and the handoff that creates the most rework. We can use that evidence to define requirements and a practical pilot.