Batchmaker family · classic interface
Batchmaker Studio · Classic
The recipe workbench as a lean web interface: recipes, raw materials, glass chemistry, cost and batch tickets in one tool without live operations.
- Responsibility
- Product architecture, frontend and calculation engine.
- Technology
- Node.js · Express · SQLite · Web Components · Vite
- Status
- Live · recipe workbench
- Positioning
- The quick workbench. No shift operation, no silos – but recipe work that has to be done in minutes.
Situation
Situation
Not every recipe question needs the full operation. If you want to check an oxide calculation, print a batch ticket or compare a recipe version, you do not open a plant for it.
The cut is therefore: raw materials, oxides, redox, batch size, cost, versions – and nothing else. No shifts, no live bookings, no silos.
Decisions
Decisions
- 01
Its own server and its own SQLite file. The workbench does not hang off the operations product and cannot overwrite anything there.
- 02
The sign-in is part of the product, not an afterthought: visible fields, password toggle, an error message on the field and a note on the instance you are working on.
- 03
Every delivery has its own domain and its own version domain with a frozen state.
- 04
No unverifiable efficiency claims. The product is the workbench, not a substitute for operations.
What you can inspect
A look at the application.
What you can inspect
The flow as a model.
01
Recipes
Version, compare, import and export, bound to raw materials and cost.
02
Materials
Master data from which oxide and batch size are later calculated.
03
Chemistry
Oxides, redox and physics in traceable calculations.
04
Tickets
Draft, scale, preview, print-ready output.
What remains
What remains
A tool does not have to model the neighbouring processes to be reliable. It only has to delimit cleanly what it cannot do.
30-min analysis · free