// blog · · by Nathan Baldwin
// Pro shipped 2026-05-14 in v1.8.0. Ten days later — here's what the install base is actually doing, what got patched in week one, and what's next.
Pro shipped on Wednesday 2026-05-14 in v1.8.0. Auto-updates and Windows Authenticode signing followed the next day in v1.8.2. The launch post explained what Pro is. This one is the inverse: what Pro is doing on the install base, ten days in.
Five features shipped with Pro. Two of them are doing most of the work.
Bulk tuning is the gateway drug. This was the feature I expected to be popular and it is. The shape of the usage is what’s interesting: most multi-select calls fan out to 3-5 devices, not the 64 the API allows. People aren’t running data centers — they’re running benches with two to five Gammas and they wanted the four-second “select all → apply Balanced” loop. The 64-device ceiling is there for the one-in-a-hundred case; the median case lives in the single digits and that’s fine.
Discord alerts are doing the night shift. I built in a 30-minute cooldown per device + trigger pair because I assumed flapping. What I actually see is that most alert fires are real — VR temp crossing 65 °C, usually because someone tightened a tune and forgot to revisit fan curves. The cooldown matters less than the test button. People configure the webhook, fire the test, see the message land in their Discord channel, and then they trust it. The test button is the conversion event.
Auto-tune sweeps are the feature people ask the most questions about before running. The guardrails (hard abort + baseline restore at 65 °C or 5 % HW error) do most of that talking once they actually click “Start sweep.” The number of people who run a sweep, watch one observation window complete cleanly, then walk away from the desk is high. That was the point.
90-day history is what people open on day eight, not day one. The chart you want is the one that lets you A/B a tuning change across a real time window. You can’t have that conversation in week one — you can have it now.
In-place auto-updates are working. Boring victory. The whole point was that you stop remembering version numbers, and now you do.
A handful of small fixes that shipped quietly because nothing in them was a feature:
/pro.html that I will not enumerate.If you’re on v1.8.2 with auto-updates on, you have all of these. If you’re not, you will the next time you launch.
Quietly, this week: the first license key validated against the live server. You know who you are. Thank you. I wrote down the receipt timestamp and pinned it to the wall above the bench.
I’m not going to make a habit of milestone posts every time the counter ticks, but the first one is allowed to matter. If you’re using Pro and something is off — anything from a bug to a feature you wish worked differently — the contact form on the site or a reply on X gets to me directly. Pro buys you, among other things, a direct line.
Two things, in this order:
Email and Telegram alert channels. Discord covers most of the population that asked for alerts, but Email is the request I’ve heard the most since launch and Telegram is a strong second. Both go on the same trigger engine as Discord, so the work is mostly the channel adapter plus a config surface. Targeting the next minor.
Supra (BM1368) and Ultra (BM1366) support. This stays on the free-tier roadmap, not the Pro roadmap. Right now everything is calibrated for the BM1370 (Gamma). When the other chips land they ship for free; Pro users get the same.
If you’ve been waiting for multi-chip support before pulling the trigger on Pro, you still don’t need to — Pro and chip support are independent. And if you’re already on Pro: the auto-tune backoff logic and the Discord cooldown both got better because beta testers broke them first. That pattern continues. Tell me when something is wrong.
Free tier stays free, forever. Pro pays the bills. We keep building.
Buy Pro — $29/year · Download for Mac · Download for Windows