Platform

Reads. Signs. Delivers.

MOFF reads from your existing controllers, signs every value at the moment of capture, and delivers the same signed record to every system that needs it.

Cryptographic audit chain

Every value can be verified, independently

Every value is signed with ECDSA when it is read, batched per device per cycle. The signatures are chained with SHA-256: each block points at the one before it, so a value altered afterwards breaks the chain and the break is locatable. Not a policy, a proof.

E-signatures

Who did what, and exactly when

User actions inside MOFF are signed with identity, timestamp and source IP, and failed attempts are logged the same way. Combined with the signed process data, a setpoint change becomes provable rather than remembered. Designed against 21 CFR Part 11 and ALCOA+.

Six protocols read live today, four delivery paths out. See every system MOFF connects to →

Trend history

Pick tags, compare them over 1 hour to 30 days, export to CSV and save the views you return to. Built for inspection and comparison inside MOFF, not as a replacement for your historian.

Compliance export

One action produces a single bundle: the signed chain, the configuration, the data as CSV, and a standalone verifier your auditor runs on their own machine.

Roadmap

A verified data source for your own AI

The signed chain does not make a model interpret your process correctly. What it gives any AI or analytics system downstream is a source with proven lineage: every value traceable to its PLC, its capture time and the scaling formula applied, with proof nothing changed afterwards.