The current state, first
Checked against the Orcyx source tree at c339cf993 on 2026-09-14. Installer availability was re-read from the release manifest at 2026-10-19T18:54:05.256Z. Where this page describes something the build does not do yet, it says so in place rather than describing the intention.
Two things are true about installing Orcyx today, and both are easier to read here than to discover halfway through:
- Windows x64 is the only platform with published installers. The versioned release manifest at https://downloads.orcyx.dev/orcyx/v0.2.21/release.json answered HTTP 200, version 0.2.21, two Windows x64 installers: EXE and MSI (2026-10-19T18:54:05.256Z). macOS and Linux builds are coming soon; the download page shows their buttons disabled until a build is published, rather than offering a link that 404s.
- The binaries are not signed by the operating system. Update packages ARE cryptographically signed - that part is live - but Windows Authenticode and Apple notarization are both waiting on certificate purchases, so a first launch shows an OS warning. What that warning looks like is below.
The download page renders the published build's real version, size and SHA-256 from the manifest. Check the SHA-256 you downloaded against the one the page shows. That check is the thing an unsigned binary makes more important, not less.
Windows
The Windows build ships as an EXE installer or an MSI package. The installers are not yet Authenticode-signed. When SmartScreen shows a blue panel for the EXE, its default button is the one that does not run the app.
- The panel reads "Windows protected your PC". Choose "More info", then "Run anyway".
- Verify the SHA-256 of the download against the one on the download page before you do that. This is the step that actually protects you; clicking through a warning without it is not a security decision.
- An OV certificate will still show this panel for a while after it is issued - SmartScreen reputation builds with downloads. An EV certificate clears it immediately.
Get-FileHash .\Orcyx-x64-setup.exe -Algorithm SHA256
macOS
The macOS build is coming soon; no disk image is published yet. It will ship as a universal disk image, and while it is unsigned and un-notarized, Gatekeeper refuses it with "Orcyx cannot be opened because the developer cannot be verified".
- Right-click (or Control-click) the app in Applications and choose Open, then confirm. The right-click route is what makes an UNSIGNED app openable.
- Do not expect that escape hatch to work for a signed-but-un-notarized build. Gatekeeper rejects those harder than unsigned ones, which is why the release pipeline refuses to build with a partial signing configuration at all - a half-configured signing setup produces a strictly worse artefact than no signing.
shasum -a 256 Orcyx-universal.dmg
Linux
Linux is on the roadmap and is not a supported install target before 1.0. Linux bundles carry no operating-system code signature in any case, so the signing work above does not apply to them.
Where builds come from
The download page is the one place builds are published. It reads the release manifest and shows each installer with its version, size and SHA-256; a platform with no published build keeps its button disabled. There is no source to build: Orcyx is proprietary and the repository is private.
If an installer reached you any other way, check its SHA-256 against the one on the download page before you run it.
Updates
Update packages are signed with a key whose public half is compiled into the app, and the app verifies that signature before applying an update. This is independent of operating-system code signing: it is what stops a tampered update, not what stops the first-launch warning.