Blog
Notes from building an MES.
How Factorial works and why it works that way: traceability, change control, and software you can program, from the founders who build it.
- Company · Why we're building an MES again Why two engineers with eight years on MES software are building another one, and why now. Read →
- Build vs. buy · Building vs. buying an MES Both paths have real strengths and real costs. How we weigh them, where we fall short today, and why we think Factorial changes the equation. Read →
- Live data · Why Factorial is live by default Nobody on a factory floor should have to refresh a page to find out something went wrong. Why every screen updates on its own, and how. Read →
- Process · Why we wrote our documentation first Writing the docs before the code showed us how the product fits together, kept our agents honest, and told us where the gaps were. Read →
- Behind the scenes · How we make our videos Every video on our site is recorded by code, from the same realistic demo factory we develop against. Read →
- Projects · Traceability before bureaucracy Prototype builds need a record too. Projects let a team define the work while doing it, without waiting on a released procedure. Read →
- Change control · Changing work that's already on the floor Redlines give the floor a reviewed way to change one task without editing the procedure or erasing what came before. Read →
- Traceability · Inventory records that admit uncertainty When lots mix and batches split, Factorial says what it knows instead of inventing a clean answer. Read →
- Plugins · An MES your coding agents can program Plugins, a CLI, and a test loop built so the agent writing your integration can check its own work. Read →
Questions about anything here? Ask the founders who wrote it.