Understand, verify, and improve automation across vendors.

No change to your current structure.* Mekai reads from the systems already running the project and writes its results alongside them. Nothing has to be migrated, re-platformed or replaced before you get a result.

*Mekai does not replace your WCS, WES, WMS, FMS, MES, SCADA, historian, PLC programming environment or recorder, and it does not require your data to be moved into a new store.

The acceptance criteria or checks you already use, and recorded data from one project — exports, logs, capture files or bag files. Recorded data is enough to produce a full result.*

*Live connections are used only where the site permits them. Where they are not, everything runs from recorded files and exports.

One project, one criterion. You send the criteria and the recorded run, and you get back the computed result, the evidence behind it, and an explicit list of what could not be proven from the data supplied.

Robot controllers, ROS and ROS 2, MCAP and rosbag2, VDA 5050, MQTT, PLCs and OPC UA, drives, doors, lifts, conveyors and chargers, plus WCS, WES, WMS, FMS, MES, SCADA, historians, databases, APIs, files and manually recorded evidence.*

*These are representative inputs. Which of them are available on a given site depends on what that site exposes and what access it grants.

No. It is read-only by default. Observation and action are separate, the default action policy is deny, and any non-safety write would need an explicit capability, bounds, approval and an audit trail. Safety control is outside the product entirely.

The result says NOT VERIFIABLE and names what is missing. Mekai does not fill a gap with an assumption, an average or a model output. Coverage, gaps and provenance travel with every result.

Every result carries the formula version, the mapping version, the configuration it ran against, the evidence window, the exclusions and references to the source data. Someone else can re-run it and get the same number.

Yes. Checks, KPIs and reports are versioned functions with declared inputs, logic, outputs and tests. You can write them, change ours, or run both. In Mekai Open the calculations are open source, so nothing is hidden behind a licence.

Yes. Mekai Open runs entirely on your own infrastructure. Mekai Platform can be deployed privately, on-premises or air-gapped where the site or the customer requires it.

Vendor neutrality is how the data and function model is designed: the core event, asset and function model does not belong to one protocol or robot type.*

*It is a design goal, not a qualification claim. What works with a specific vendor depends on the sources that vendor exposes and the access the site grants.

Mekai Open is free. It is published under AGPL-3.0, runs on your infrastructure, and has no licence fee, seat count or sales call attached. Mekai Platform is quoted per deployment.*

*Scope, number of sites and the integrations required decide the quote. There is no public price list, and no figure on this site is an offer.

No. It removes the manual assembly work around them — collecting evidence, recomputing numbers, rebuilding packs. The engineering judgement, the approval and the signature stay with the people who hold that authority today.

No. Mekai organizes and reviews evidence and reports what the available data supports. It does not approve systems, issue certification, perform conformity assessment or act as a notified body. The engineer, assessor or authority who signs today still signs.

Often you would not, for the part you have already built. The question worth asking is what happens to it when the ground moves under it, because it usually moves in three ways.

• Standards keep changing. ISO 3691-4, ISO 13849 and IEC 60204-1 revise on their own schedule, and the EU machinery rules with them. A check written against last year's clause version does not fail loudly when the clause moves — it keeps passing and quietly stops meaning what it used to.
• Your site keeps changing: a swapped sensor, a firmware or controller update, a second vendor's robot added to the fleet, a re-layout, a WCS or FMS release, a changed parameter set. Each one can invalidate a mapping, a threshold or a test your in-house layer assumed was stable, and nothing tells you which.
• Your customer's reviewer still has to accept the number. An internal dashboard proves it to you. A result carrying its formula version, its window, its exclusions and its gaps proves it to them, without either side rebuilding it by hand.

Download Mekai Open and point it at your own recorded data. Nothing to sign, nothing to buy, no account. If it is useful, the conversation about the paid workspace can happen afterwards.