About Coilware

We don't think the protocols are the problem.

The thesis

Industrial software
stopped evolving in the 2000s.

The protocols are fine. The tools around them are not.

We're working engineers. The small utilities we reach for every day - Modbus scanners, serial sniffers, register pokers - look and feel like they did fifteen years ago. They work. They're also clunky, ugly, and well below the standard of any other professional software in 2026.

Coilware exists to fix that.

The standards work. The workflows work. What's missing is craft in the tools themselves. No cloud account, no new methodology, no 90-minute onboarding - just better versions of the utilities engineers already use, built to the standard the rest of our software stack hit a decade ago.

Modbus first, because everyone has it. Then outwards, guided by what the engineers using the tools actually ask for.

Principles

How we work.

01

One price, perpetual

You buy the software. You own the licence. No subscription renewals, no SaaS lock-in, no ‘cloud edition’ upsell. If we close tomorrow, your software keeps working.

02

Open formats

Configs and captures use open, documented formats. Nothing about your work should be hostage to a binary blob we own.

03

Long roadmap, short release cadence

We ship every two weeks. Public changelog. Public roadmap. If you've reported a bug, you'll see it land or you'll hear why it didn't.

Roadmap

What's next, honestly.

Last updated · 19 May 2026
Now
building
Coilware Modbus beta
Closed beta opens June 2026. Twenty engineers, free perpetual licences, honest feedback on real work.
Late 2026
designing
Coilware Modbus v1.0
Public launch. RTU and ASCII transports stable alongside TCP, with the beta's findings folded in.
Beyond
designing
More protocols, in time
Modbus is where we start, not where we stop. The next protocol we tackle will be the one beta testers ask for most.