brewOS
What it does Pricing Is it for you Founding breweries Journal

English · Español · Português · Deutsch · Français

InstagramLinkedIn

Call it a pilot batch.

We're choosing twelve breweries to run BrewOS alongside us from the start. Small, watched closely, and we'll write down honestly how it went.

Applications close 30 November

The next year gets built in twelve breweries, not in my head.

I built the first version for one brewery. Mine. It is better than it was because that brewery kept finding things wrong with it.

One brewery's problems only get you so far, though. The next year of this needs the awkward cases — the thing that annoys you in week three, the way your cellar runs that I'd never have thought to try, the sentence on a screen that means something different in your brewery than it does in mine.

So we sit down four times in the first year, and not on a calendar — at the four points where there's actually something worth looking at.

  1. Once you're set upYour recipes are in and the targets set, before the first brew runs against them
  2. After the first beer shipsOne beer all the way through — brew day, cellar, packaging — and the first real numbers
  3. Once there's historyEnough batches that your own measured yields and stage times mean something
  4. After a planned seasonYou've run the planner against real orders and real tanks

They're working sessions about your production, with a brewmaster — not support calls about software. What we get out of them is finding out what BrewOS got wrong while you still remember being annoyed by it.

You wouldn't be testing it. You'd be shaping it.

What you get
  • Four working sessions with a brewmaster, across your first year — about your production, not about the software.
  • $49 a month, locked for as long as you stay.
  • Your setup done with you, not handed to you.
  • When something breaks, you're talking to the brewmaster who built it — not a support tier.
  • What you ask for goes to the front of the queue, where it fits.
  • Your records are yours. Ask for them any time and we'll get them to you — whether you're staying or leaving.
  • Your name on the site, if you want it there.
What we ask back
  • Turn up to the four, and say what isn't working.
  • Tell us what's wrong while it's still annoying you.
  • Let us write up honestly how it went, good and bad.

That's the arrangement. There's no contract longer than this page.

Why only twelve.

Setting a brewery up properly is real work — your tanks, your recipes, your units, your language, all set up the way you actually brew. We do every one of them by hand, and twelve is as many as we can do that way in a year.

Once twelve are in, we stop taking applications and get on with the work. We'll open again when we can give the next ones the same attention.

Two brewers talking over a bench, glasses in hand
What the third session looks at

By then, the numbers are your own.

After enough batches, every recipe shows what its brews actually did against it: gravity, attenuation, yield and the days each stage took. That’s where the conversation gets useful, and it’s why the sessions follow the brewery, not the calendar.

A brewmaster and a head brewer at a steel bench in the brewery, going through a notebook of brewing notes, two glasses of beer between them
A recipe's performance panel: original and final gravity, attenuation, ABV, brewhouse yield and days per stage across sixteen brews, each figure stating how many brews it is measured from
A recipe’s performance across its brews. Each figure says how many brews it’s measured from. Screen from a demo brewery.

Think you're one of them?

Tell us what you brew, how many tanks you've got, how often the brewhouse runs, and what you're using to keep track of it today. A paragraph is plenty. If a spreadsheet's still doing the job, we'll say so.

Write to [email protected]

We set up every brewery by hand. There's no signup button.

Read who it's for first