Catch an out of spec batch before it ships
Every morning, WebRun opens Ekos, reads every QA and QC test entry logged for yesterday's batches, checks each reading against the spec range set for that recipe, logs any out of spec result to a running Google Sheet, and posts a Slack alert naming the batch and the exact reading so your head brewer can review it before it moves to packaging.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch an out of spec batch before it ships?
WebRun reads every QA and QC test entry logged in Ekos each morning, checks gravity, pH, IBU, and sensory readings against the spec range set for that recipe, logs any out of spec result to Google Sheets, and posts a same day Slack alert naming the batch and reading, so your head brewer reviews it before packaging.
- An out of spec batch gets flagged the same morning it is tested
- QC exceptions build a trend history automatically in Google Sheets
- Hold and release decisions stay with the head brewer, never automated
Built for craft breweries · head brewers · quality control managers · production managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.goekos.comin a real browser with your saved login - no setup, no API keys. -
1
Ekos - check yesterday's QC entries against spec
goekos.com How to Automate Ekos
WebRun opens Ekos to check yesterday's QC entries against spec. - Open Ekos and pull QA and QC test entries logged in the last 24 hours
- Compare each reading, gravity, pH, IBU, and sensory notes, against the spec range set for that recipe
- List any batch with a reading outside its spec range
Done when Every QC entry from the last 24 hours has been checked against its recipe spec.
-
2
Google Sheets - log out of spec results
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log out of spec results. - Open the QC exceptions Google Sheet
- Log each out of spec batch with the reading, the spec range, and how far off it fell
- Update the running count of exceptions by recipe for trend review
Done when Every out of spec result is logged with how far it deviated from spec.
-
3
Slack - alert the head brewer to review
slack.com How to Automate Slack
WebRun opens Slack to alert the head brewer to review. - Post a review alert to the head brewer or QC channel for each out of spec batch
- Name the batch, the recipe, the reading, and the spec range it missed
- Leave any hold or release decision for the head brewer to make
Done when The head brewer has a same day alert for every batch that tested outside spec.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it hold or release a batch on its own?
No. WebRun only flags a batch that tested outside spec and alerts your head brewer. The hold or release decision stays a human call.
What counts as out of spec?
Any gravity, pH, IBU, or sensory reading logged in Ekos that falls outside the spec range already set for that recipe. WebRun does not set or change spec ranges.
Does it only check the most recent batches?
It reviews every QC entry logged in Ekos in the prior 24 hours each morning, so nothing from the previous day's testing gets missed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.