Prebuilt Binaries
The signed Wintty builds: what is published, how updates are delivered, and how to verify a build before you run it.
Note
No build has been published yet. This page describes how downloads will work so that it is accurate on the day the first release is cut, but there is nothing to download from it today.
Wintty is a Windows application, and the prebuilt builds are Windows builds. If you are on macOS or Linux, the project you want is Ghostty, which Wintty is a fork of.
Prebuilt builds are how the Sponsor and Pro tiers are delivered. There is no prebuilt OSS build. The OSS tier is the source tree, and the way to get it is to build it yourself.
Each tier is published as an installer, plus the packages its updater uses to move an existing installation forward.
| Artifact | What it is |
|---|---|
Setup.exe | The installer. This is what you download and run. |
| Update packages | Fetched by the application itself, not by you. |
.msi | Pro Enterprise only, for SCCM, Intune and Group Policy. |
Each tier is published on two channels. stable is the released
build. tip tracks development and is covered on the
tip builds page. Both are included at every
sponsoring level, so choosing one is a question of how much churn you
want and not of how much you paid.
Updates are applied in place by the application. You do not download a new installer for each version, and there is no separate updater to install. Updates are fetched only for the channels your account is entitled to, which is described in how access works.
Every published build is signed by Ship Digital Ltd using Azure Artifact Signing, and the signature carries a RFC 3161 timestamp.
The timestamp is the part worth understanding. A signature on its own stops verifying when the certificate that made it expires. A timestamped signature records that the signing happened while the certificate was valid, so a build stays verifiable long after that certificate is gone. A build you download today will still check out years from now.
Windows shows the publisher on the security prompt when you run the installer. Look for Ship Digital Ltd there before you click through.
You can also check it yourself, without running anything:
Get-AuthenticodeSignature .\Setup.exe | Format-List Status, SignerCertificate, TimeStamperCertificate
Status should be Valid, the signer certificate should name
Ship Digital Ltd, and there should be a timestamper certificate
rather than an empty field.
Warning
If a Wintty build does not show that publisher, it did not come from this project. Do not run it.
Builds are served from private storage and a request has to be authorized before a file is handed over. That is what sponsoring unlocks, and it is why there are no public download links on this site. See how access works for the mechanics.