Sigmastone

Notes · Engineering · 7 November 2026

Why we sign releases with hardware, not a cloud

The signing key for our software never leaves a token a person holds. What that costs us, and why we pay it.

Every installer and every binary we ship is signed, so that the operating system and the person installing it can check that it came from us and was not changed on the way. That signature is only as trustworthy as the place the private key lives.

The convenient answer in 2026 is a cloud signing service: upload the certificate, let a build job on someone else's machine sign whatever passes through it. It is fast, it is automated, and it removes a person from the release path.

We decided against it.

The key stays on a token

Our code signing certificate lives on a hardware token, a small device that performs the signing operation itself and never hands the private key to anything. The token stays with one person. It is not in a data centre, not in a build runner, and not in any account that can be phished.

A release is signed on a dedicated signing desk: a small desktop application that holds the token, listens on a narrow interface for files to sign, and signs them one at a time, on request, with a person present. Build servers prepare releases; they do not sign them.

What it costs

  • Time. A release waits for a person with the token. There is no fully unattended release pipeline, by design.
  • Software. We wrote and maintain the signing desk ourselves, rather than configuring a service.
  • Discipline. Backups, key ceremonies and renewals are our responsibility, not a vendor's.

Why we pay it

The failures that keep us up at night are not failed builds. They are quiet ones: a leaked credential used to sign malware with our name on it, a compromised runner slipping a modified binary into a release, a vendor incident that we only read about afterwards. A key that cannot leave a device in a known person's hand closes those doors in a way that no amount of cloud configuration does.

It also matches how we think about the rest of our products. Things that matter should be verifiable, and the chain of custody should be short enough to explain in a paragraph. This is that paragraph.

What you can check

Every published file carries a signature you can inspect with your operating system's tools, and the certificate names Sigmastone as the publisher. If a file we ship does not pass that check, do not run it, and tell us at contact@sigmastone.io.