I’m prototyping a web‑native roasting platform that wraps Artisan’s device drivers and exposes everything through an API.
* Runs locally or on your LAN
* view live curves on another device
* avoid losing a roast if your laptop crashes
* keep a dedicated “roast computer” plugged in
* optionally control the roaster from another device on the LAN
Basically, Artisan’s capabilities, but accessible from any browser and scriptable via API.
I’m curious whether this is something home roasters or small commercial roasters would actually adopt.
Does a web‑based workflow appeal to you?
Or is desktop Artisan already the perfect tool for your workflow?
What features would make this genuinely useful (or a waste of time)?
Does a more flexible roasting workflow + meaningful data discovery matter?
* Runs locally or on your LAN
* view live curves on another device
* avoid losing a roast if your laptop crashes
* keep a dedicated “roast computer” plugged in
* optionally control the roaster from another device on the LAN
Basically, Artisan’s capabilities, but accessible from any browser and scriptable via API.
I’m curious whether this is something home roasters or small commercial roasters would actually adopt.
Does a web‑based workflow appeal to you?
Or is desktop Artisan already the perfect tool for your workflow?
What features would make this genuinely useful (or a waste of time)?
Does a more flexible roasting workflow + meaningful data discovery matter?
