Coffee
Roast control that drives the machine, a recording that never misses a roast, and analysis that reads the way a roaster does — built for the coffee industry, on hardware you own.
Why coffee
A roastery's knowledge lives in its roasts — in curves, phases and the rate of rise at each bean temperature — and most of it is lost to spreadsheets, USB sticks and memory. We build two halves that close that gap: a control appliance on the roaster itself, and a cloud console for the whole roastery.
On the roaster: roast control
A native Linux appliance boots straight into a console that drives the roaster — the Yoshan 1.5 kg is the first supported machine — records every roast whether or not the network is up, and can follow a reference profile adaptively.
- Records from the moment it connects. The journal is append-only and fsynced per record; a power cut can cost at most a torn final line. A roast nobody pressed record on is still recorded.
- Follows a reference roast. It replays the reference's recorded fire and corrects on the rate of rise it measures, so a cold drum runs late and still traverses the same curve. Arming, igniting and dropping stay with the person.
- Learns your machine. One button fits a thermal model from the roasts already on the box, and refuses to write a model the data does not support.
- Safety first, measured not assumed. A supervisor watches the machine and cuts the gas; every path that reduces heat works from every state; the automatic follower gets no privilege a person lacks.
- Runs offline. Paired to the cloud it reports; unpaired, it keeps roasting and recording.
In the cloud: roast analysis and the roastery
Every roast's full trace arrives as an immutable file in your own drive, and a console shows the roastery as it happens.
- The curve reads like a roaster reads. Bean temperature and rate of rise on twin axes, fire and fan as a band below, milestone marks, drying/maillard/development phases, and a crosshair that reads out in the legend.
- Live during the roast. Lines arrive as the box records them; the session view follows the roast in progress and switches to the stored trace when it lands.
- Scores the batch. "How did that go?" compares the roast against its profile at matched bean temperature — a roast that runs late is not marked wrong for being late.
- Production records. Every batch from charge to drop, with readings — weight, Agtron, moisture, density, cupping notes — and the shop calls it owes, in one place.
- Your data is yours. The journal file is the truth, byte for byte, kept in your own Hoq drive.
Where this is heading
Blending and production planning, recipes, packaging and labels, cupping and inventory — the platform is built toward the whole roastery, and we build it with roasters, against real machines.
Next step
Tell us about your roastery — what you roast on, what you measure today, and what you wish it did. We'll take it from there.