Brewira is small and at the design stage. The roles below are the ones the first design-partner deployments need. They open as the cohort forms; there is no openings count to inflate.
Illustrative scenario: Plant run · one lager batch from brewhouse to can · brewhouse, cellar, filler, tunnel pasteurizer. Not a measured run.
Each role is written as a shape, not a job ad with a requisition number.
Own the camera pipeline: fill-level estimation, seam and cap, label OCR and foreign-body models, DeepStream and TensorRT on Jetson, Triton serving, and the latency budget that makes a reject decision useful at tens of thousands of containers an hour.
Build the connectors that read brewhouses, tanks, skids, fillers and pasteurizers and write guarded setpoints back, without ever touching an interlock or a PU profile. Own the allow-lists, rate limits and the audit record of every write.
Build Cuvera: GPU-accelerated simulation of fermentation kinetics, carbonation mass transfer, mixing and pasteurization heat, surrogates that run at the edge, and the calibration that keeps the twin honest against as-produced batches.
Translate between the plant and the platform: define what in-spec means per brand and package, review agent recommendations in assist mode, design the food-safety and ROI gates, and sit with design partners in the brewhouse and on the line.
Grounding, audit, human-in-the-loop and graduated control come before any write to a line.
A brewmaster's or quality manager's correction is a labeled training event, not a complaint.
One line and one number first. The plant and the group follow the number.
Pasteurization units, CIP release and batch release stay with the plant's HACCP plan and its people.
Recipes and supplier data never cross a customer boundary. On-prem is an option, not an exception.
Golden datasets and model-as-judge evaluations gate model and prompt changes in CI.
Every Brewira run is an ordered, inspectable sequence. This is run_scn_01, an illustrative scenario: Plant run · one lager batch from brewhouse to can · brewhouse, cellar, filler, tunnel pasteurizer. Scenario complete · batch inside spec · one human approval at the pasteurizer.
Plant Orchestrator · Pulled the recipe, the package spec, the HACCP plan with its pasteurization critical control point, the yeast lot record and the standing CIP window from the beverage MES and the lab system; locked the target envelope for the run.
Plant Orchestrator · Simulated 24 candidate brew, fermentation and carbonation plans on the Cuvera as-produced twin; ranked them on gravity margin, predicted finish time, CO2 target, PU margin, takt and CO2 and energy use, and discarded every candidate that thinned the pasteurization margin.
Brew-and-Blend · Held wort gravity to recipe from the inline gravity analyzer and the brewhouse PLC, trimming the blend and utilization setpoints inside the recipe window rather than correcting after a spot lab check.
Ferment-and-Yeast · Predicted the attenuation curve and finish time for the tank from inline gravity, dissolved oxygen and CO2, pH and temperature; held the temperature ramp and timed the crash inside the brewmaster-approved window; no stuck or runaway fermentation was flagged.
Filter-and-Carbonate · Fused inline CO2, dissolved oxygen, turbidity, temperature and pressure; held carbonation to the package target with the minimum CO2 and timed the filter backwash from the predicted loading instead of a fixed schedule.
Fill-and-Seal · Adjusted fill valves toward the target level inside the approved window using drift feedback from inspection, and ran seam checks on the seamer; the filler corrected upstream instead of rejecting downstream.
Defect-and-Inspect · 16 camera streams at the line edge: fill level, seam and cap, label and date code, foreign body and container checks on every can; three low-fill rejects were attributed to one filler valve and Fill-and-Seal corrected it.
Pasteurize-and-CIP · Held the tunnel pasteurizer on the validated PU profile at the lowest zone energy inside the envelope; every critical control point reading was written to the audit log against the HACCP plan and the CIP release checks were armed.
Plant Orchestrator · The lowest-energy candidate wanted to move the pasteurizer CIP into a window that overlapped the next brand's start. Held for the shift quality manager, who kept the validated PU profile untouched and approved the CIP move with a tighter release check.
Quality-and-Conformance · Batch released: gravity and attenuation curves, yeast lot, CO2 and clarity, fill and seal outcomes, inspection rejects, PU readings, CIP release and every human decision written to the batch genealogy and checked against spec.
Lines fill tens of thousands of containers an hour, so perception has to be local and fast. Brewira runs GPU inference at the line edge and keeps training, simulation and optimization in the cloud, in a private cloud or on-prem. Items marked planned are on the roadmap, not running.
8 to 24 camera feeds per line through DeepStream pipelines and TensorRT detectors, segmentation, OCR and fill-level models; Holoscan synchronizes cameras with gravity, CO2 and clarity analyzers and filler and pasteurizer telemetry. Design target: sub-100 ms reject decisions.
Vision, time-series, anomaly, process and food-safety reasoning models behind one orchestrator, with version routing by brand, package and line. Design target: 20 to 60 model versions per enterprise tenant.
Line vision, time-series forecasters, anomaly models and NeMo-based beverage reasoning fine-tuned from labeled batch outcomes, brewmaster corrections, lab results and release decisions. Design target: weekly retraining for wedge models, monthly for validated process models.
The Cuvera as-produced line twin: CUDA-accelerated fermentation, carbonation, mixing and pasteurization heat simulation run before the batch, for new SKU setup and batch planning when a trial is expensive.
Rare leaker, low-fill, overfill, cap-skew, seam, label-shift, condensation, glare and foreign-body scenarios generated with domain randomization and validated against real plant events before use.
Brew and fill schedules, changeovers, CIP cycles, water and energy allocation and takt balancing under line, tank, product and sanitation constraints, recomputed on the GPU when the plant is disrupted.
Image, time-series and batch-genealogy ETL for feature generation, quality correlation and cross-plant benchmarks on the GPU.
Pack, case and palletizing handling, with perception and motion policies built and validated in simulation before they move a pallet.
A plant does not go from manual to bounded control in one step. Brewira makes the stage explicit per loop, auditable and reversible at any time, and some decisions never leave the person.
| Stage | What the agent does | What the person does | When |
|---|---|---|---|
| Shadow | Predicts gravity, attenuation, carbonation, fill and seal faults, contamination and takt; writes nothing | Runs the plant as today; compares predictions to lab, QA and PLC outcomes | First phase with every design partner |
| Assist | Recommends bounded brew, fermentation, carbonation, fill and seal, pasteurization and CIP moves with the evidence | A brewmaster, process engineer or quality manager approves or rejects each one | After accuracy is proven against the baseline |
| Bounded | Writes low-risk filling, carbonation and inspection setpoints inside documented recipe, quality, food-safety, equipment and rollback limits | Approves anything above the limits; reviews the shift record | After the food-safety and ROI gates agreed up front |
| Exceptions | Escalates anything outside its envelope, CCP-adjacent moves and release decisions | Always decides these; the agent never does | Permanent |
The three people in a beverage plant whose week changes when the process runs itself, and what each of them needs from Brewira.
Owns production rate, quality, loss, giveaway and yield, water and energy, and food safety. Wants a plant that holds spec at higher rate with fewer interventions, and a number that justifies the spend.
Owns recipes, brewhouse and blend, fermentation and carbonation process windows and yield. Approves and corrects the agents in assist mode; those corrections train the models.
Owns product quality and safety under HACCP, FSMA, FSSC 22000 and BRCGS, contamination and fill and seal conformance, and batch 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.
Brewira 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 · FSSC 22000 · BRCGS | 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 producers | RUNNING Design option |
Brewira supports your food-safety records. It is not a certification and it does not replace your HACCP plan.
The questions plant directors, brewmasters and quality managers ask in the first meeting.
Only at the autonomy stage your plant has set, and only to an explicit allow-list of low-risk loops inside documented limits. Every design partner starts in shadow mode, where Brewira predicts and writes nothing. Assist mode follows, where a brewmaster or process engineer approves each recommendation. Bounded autonomy on filling, carbonation and inspection loops comes after the food-safety and ROI gates agreed up front.
Critical control points are not optimization variables. The pasteurization PU profile, the CIP release checks and the batch release decision stay with your HACCP plan and your people. Brewira verifies readings, writes them to an immutable audit log and attaches them to the batch genealogy. It is grounded in HACCP, FSMA, FSSC 22000 and BRCGS procedures; it is not a certification and does not replace your plan.
Brewira sits above your existing automation as a supervisory layer. If it stops, the plant keeps running on its current PLC and SCADA control and the interlocks it already has. A Brewira outage degrades the plant to the way it runs today, not to a stop.
The first phase is shadow mode on one line: Brewira reads your analyzers, PLC history, lab results and MES while you run the plant as usual, and we measure its predictions against your lab, QA and PLC outcomes. Recommendations start when accuracy is proven against that baseline, and improve as plant-specific history and brewmaster corrections accumulate.
Recipes, product specs, tolerance models and supplier data are tenant-scoped and never used to train another customer's models. Retrieval is multi-tenant isolated and permission-aware. Cross-plant learning, where a customer opts in, is federated and IP-isolated. On-prem deployment is available for producers protecting sensitive recipes.
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: fill giveaway and low-fill rejects, leaker and seal faults, attenuation variance and tank time, CO2 use and clarity rejects, or water and energy on pasteurization and CIP. We instrument the line in shadow mode, measure the baseline, move to assist mode when accuracy is proven, and expand only when the number holds.
Full multi-module autonomy across the whole plant, 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 assurance-grade food-safety audit log.
Send what you have built. A person reads it.
↑↓ navigate↵ openesc close
