Manufacturing Execution System

Burned into silicon. Impossible to lose.

Flint MES runs your production line end to end. Operators scan a barcode; stations flash the ESP32-S3, burn the serial into eFuse, capture the test log, and deliver every result to the backend exactly once — even through power loss, dropped networks, and reboots.

Exactly-once deliverySurvives power lossmacOS · Windows · Linux · Pi
Unit passportdelivered
SerialBRD-24A7-0001F3
MAC7C:DF:A1:9E:04:B2
Firmwaredevice-fw v2.4.1
eFuseserial burnedok
Testfunctional passpass
Uploadexactly oncedelivered
One record per unit — from scan to final test.
How a board ships

Scan once. The station does the rest.

Five steps run on the bench without an engineer watching. Each result is captured the moment it happens — before it can be lost.

  1. 01

    Scan

    An operator scans the barcode serial. From this moment it is the board’s identity.

  2. 02

    Flash

    The station flashes the assigned firmware bundle onto the ESP32-S3.

  3. 03

    Burn

    The serial is written into the chip’s eFuse — permanent, one-time, unforgeable.

  4. 04

    Test

    Functional test runs; the full UART/serial log is captured with the result.

  5. 05

    Upload

    The result lands in a local outbox and is delivered to the backend exactly once.

Power drops at step 3? The record is already on disk in the station’s outbox. On reboot it replays and finishes the upload — and because delivery is idempotent, the backend records it exactly once. Never zero, never twice.

Why Flint

Built for a floor that can’t afford to lose a unit.

The hard parts of hardware production — durability, traceability, and keeping a fleet of stations in sync — handled by default.

Durable by design

Nothing gets lost

Every flash and test result is written to an embedded SQLite outbox before anything else. Idempotent retries drain it when the network returns — so a station can lose power mid-flash and still deliver each record exactly once. Never zero, never twice.

Scan to ship

One serial, for life

A barcode scan drives the whole flow. The serial is burned into eFuse and becomes the board’s identity for good — one record per unit, traceable from PO date to final test, forever.

Fleet-managed

The whole floor, in step

Assign firmware bundles centrally from the web app. Stations sync config and firmware on a loop and report live online/offline status, so every bench runs the build you intend.

Unattended factory

Runs where your line runs

Stations run on macOS, Windows, Linux, and Raspberry Pi. The operator UI is bilingual — English and 中文 — so the line keeps moving with just a barcode and a screen.

The web app

Manage the line from one place.

Stationslive status
Runsin progress
Firmwarebundles
Test recordsper unit
SerialseFuse
Dashboardsrealtime
Runs where your line runs
English / 中文

One station app, cross-platform and bilingual, so the same build runs on every bench — attended or not.

macOSWindowsLinuxRaspberry PiESP32-S3 flash + eFuseExactly-once upload

Ready when your line is.

Sign in to manage stations, firmware, production runs, and every unit’s record.

Sign in to Flint