A Line subscription is justified from verified savings or avoided risk on one line: giveaway, energy per unit through the oven, downgrade from under- or over-bake, or escapes. We would rather you started with one line and one number than with a plant-wide programme nobody can baseline.
Illustrative scenario: Plant run · one bread line, flour-lot change at the silo · shared oven. Not a measured run.
Land on one workflow with a measured baseline. Expand by line, module, site and autonomy level. Outcome components available on yield, waste, giveaway and energy.
Dough, proof or bake control, or inspection AI, for one line. For bakeries validating ROI on the wedge.
The whole bakery: dose and mix, ferment and proof, makeup and deposit, bake and cool, defect and inspect, quality and shelf life, yield and takt, robotic handling, and the Bakesim twin.
Bakery groups standardising on Doughex across sites, with custom recipe, product and tolerance models.
A 15 to 20% discount for annual prepayment.
Enterprise agreements with usage ramps.
A share of measured yield, waste, giveaway or energy improvement on the highest-value workflows.
Per-batch, per-line or per-action metering above plan limits.
Modules are licensed per line on the Line tier and bundled on Plant and Enterprise.
| Capability | Line | Plant | Enterprise |
|---|---|---|---|
| Lines covered | 1 | All on site | All in group |
| Agent modules | 1 of 9 | All 9 | All 9 + custom models |
| Bakesim twin | Not included | Included | Custom twin domains |
| Plant-edge node | Included | Per line | Fleet managed |
| Guarded PLC writes | Scoped tags | All scoped tags | Group policy |
| Lot genealogy | Included | Included | Included + export |
| Autonomy levels | Observe, recommend, approve, bounded | Observe, recommend, approve, bounded | Observe, recommend, approve, bounded |
| Deployment | Plant edge + cloud | Plant edge + cloud | On-prem or private cloud |
| Outcome pricing | On request | Available | Standard |
| Indicative price | $13,000 / mo | $85,000 / mo | $600k – $8M ACV |
Every Doughex run is an ordered, inspectable sequence. This is run_scn_01, an illustrative scenario: Plant run · one bread line, flour-lot change at the silo · shared oven. Scenario complete · every stage inside spec · one human approval at the oven.
Plant Orchestrator · Pulled the product spec, the recipe, the HACCP plan with its bake kill-step and metal-detection control points, the allergen status of the line and the new flour lot's certificate from MES and the lab system; locked the target envelope for the run.
Plant Orchestrator · Simulated 24 candidate profiles across mix, proof, deposit and oven on the Bakesim as-baked twin for the new flour lot; ranked them on colour and moisture margin, weight margin, energy per unit and takt, and discarded every candidate that thinned the bake kill-step margin.
Dose-and-Mix · Adjusted hydration and mix energy for the new lot's absorption so dough temperature and development landed on target; dough state was handed to the proofer with its predicted rise curve.
Ferment-and-Proof · Predicted the rise curve from inline height, temperature, humidity and CO2, then trimmed proofer humidity and dwell so rise and volume landed on target instead of running fast on the fresher lot.
Makeup-and-Deposit · Fused checkweigher readings with dough state and divider feedback and trimmed the divider in real time so portion weight sat at the minimum safe margin above the declared weight, with the underweight guardrail armed.
Plant Orchestrator · The twin's lowest-energy candidate wanted a zone-three temperature outside the site's bounded envelope. Held for the shift process engineer, who approved the step with a tighter colour alarm.
Bake-and-Cool · Ran the oven against the twin's colour and moisture prediction; stepped zone temperatures and band speed toward the minimum-energy profile while predicted crust colour and crumb moisture stayed inside spec and the core-temperature kill step was verified on every reading.
Defect-and-Inspect · 12 camera streams at oven exit, cooler exit and packing at the plant edge: colour, shape, holes, cracks, foreign-body and seal checks on every unit; two pale-top rejects were attributed to a draught at zone one and the oven agent was notified.
Robot-and-Handling · Robotic depanning, tray transfers and packaging handling paced to the line, with rejected units diverted off the belt and the safe zone around each cell monitored.
Quality-and-Conformance · Lot released: flour lot, recipe, mix and proof setpoints, portion weights, oven profile, kill-step readings, inspection rejects and every human decision written to the genealogy and checked against spec and the HACCP plan.
Low-friction entry on a single mixing, proofing or baking line with a hard waste, giveaway or energy metric, or a paid pilot tied to it.
Adjacent agents in the same bakery, then the Plant tier, then multi-site enterprise agreements with plant-edge fleet management and custom models.
Per-batch, per-line or per-action metering above plan limits, and a share of measured yield, waste, giveaway or energy improvement on the highest-value workflows.
Floor pricing is protected; discounts are traded for term length and case studies. Expansion is the primary growth engine.
The pilot KPI is chosen so the plant can baseline it from its own checkweighers, meters and QA records before anything is connected.
| Wedge | Product | Number baselined | Source of the number |
|---|---|---|---|
| Depositing | Gramex | Giveaway in grams per unit; underweight rate | Checkweigher, MES |
| Oven | Ovenix | Energy per unit; colour and moisture variance; downgrades | Gas and electricity meters, QA checks |
| Proofing | Proofa | Rise variance; dense or collapsed product; waste | Inline height, QA records |
| Inspection | Vizra | Escape rate; downgrade; rejects by cause | QA and complaint records |
Doughex is recruiting three to five design partners for the first cohort. These are the bakery types the products were designed around and where each would start.
Proofing and the oven at the highest volume in the industry. Starting wedge: Proofa or Ovenix, with Vizra at oven exit.
Depositing weight and bake colour decide margin. Starting wedge: Gramex on the depositor, Ovenix on the band oven.
Depositing to weight and baking to moisture on high-value product. Starting wedge: Gramex, with Vizra on decoration and packing.
Proof, sheeting and a fast, hot bake. Starting wedge: Proofa and Ovenix together.
Weight, diameter and bake colour at very high rate. Starting wedge: Gramex, with Vizra on shape and colour.
Continuous bake and moisture windows under food-safety mandates. Starting wedge: Ovenix, with Vizra for foreign bodies.
Doughex writes to production equipment in a food plant. Every capability is scoped, every write is policy-checked, every output is cited, and every action is written to an append-only audit log the plant owns.
| Item | Scope | Status |
|---|---|---|
| SOC 2 Type I | Cloud control plane | QUEUED Roadmap, first 6 months |
| SOC 2 Type II | Cloud control plane | QUEUED Roadmap, 6 to 12 months |
| HACCP · FSMA · BRCGS · ISO 22000 · allergen | Grounding and record-keeping | RUNNING Design basis for retrieval and the audit log |
| Per-tenant isolation | Data, memory, models | RUNNING Design rule |
| On-prem deployment | Recipe-sensitive bakeries | RUNNING Design option |
Doughex supports your food-safety records. It is not a certification and it does not replace your HACCP plan.
The three people in an industrial bakery whose week changes when the line runs itself, and what each of them needs from Doughex.
Owns production rate, quality, waste, giveaway and yield, energy and food safety. Wants a bakery that holds spec at higher rate with fewer interventions, and a number that justifies the spend.
Owns recipes, dough development, proof and oven profiles, process windows and yield. Approves and corrects the agents in recommend mode; those corrections train the models.
Owns HACCP, FSMA, BRCGS, ISO 22000 and allergen conformance, foreign-body and defect conformance, and lot genealogy. Needs every action grounded, cited and written to an immutable record.
IT/OT and sustainability leads approve the deployment. There are no customer quotes on this site yet; design partners will speak for themselves when they choose to.
One policy model, one audit trail and one set of yield, waste, giveaway and energy benchmarks across every bakery in the group, with each site's recipes and tolerance models kept private to that site.
The questions plant directors, process engineers and quality managers ask in the first meeting.
Only at the autonomy level your plant has set, and only to an explicit allow-list of low-risk loops inside explicit limits. Every design partner starts in observe mode, where Doughex predicts and writes nothing. Recommend mode follows, where a process engineer approves each move. Bounded autonomy on oven, depositing and inspection loops comes after the food-safety and ROI gates agreed up front.
Critical control points are not optimisation variables. The bake kill step, metal detection and X-ray reject interlocks, allergen changeover and release decisions stay with your HACCP plan and your people. Doughex verifies readings, writes them to an immutable audit log and attaches them to the lot genealogy. It supports HACCP, FSMA, BRCGS, ISO 22000 and allergen records; it is not a certification and does not replace your plan.
Doughex sits above your existing automation as a supervisory layer. If it stops, the line keeps running on its current PLC and SCADA control and the interlocks it already has. A Doughex outage degrades the bakery to the way it runs today, not to a stop.
The first phase is observe mode on one line: Doughex reads your sensors, PLC history, QA checks and MES while you run the line as usual, and we measure its predictions against your own checkweigher, colour and moisture checks. Recommendations start when accuracy is proven against that baseline, and improve as plant-specific history and engineer corrections accumulate.
Recipes, product specs, tolerance models and customer specs are tenant-scoped and never used to train another customer's models. Retrieval is multi-tenant isolated and permission-aware. On-prem deployment is available for bakeries protecting sensitive recipes or private-label specs.
You are, the same as with any control strategy. That is why every write is policy-checked, bounded, logged and reversible, every output carries a citation to the recipe or procedure it relied on, and anything above your threshold waits for a named approver. The audit log records the request, the reasoning, the limits applied and the human decision.
As a design partner, on one line, with one hard metric: giveaway in grams per unit, energy per unit through the oven, downgrade and waste from under- or over-bake, or foreign-body and defect escapes. We instrument the line in observe mode, measure the baseline, move to recommend mode when accuracy is proven, and expand only when the number holds.
Full multi-module autonomy across the whole bakery, long-tail integrations beyond the design partners' stacks, and self-serve onboarding. The first release is one wedge workflow, its connectors, the agent loop with human checkpoints, the review console and the food-safety audit log.
Tell us the line and the number. We will tell you whether a pilot can baseline it.
↑↓ navigate↵ openesc close
