The homepage hero offers three platforms. macOS goes to /download, and Linux goes to the x86_64 AppImage, but the Windows link downloads openwork-win-arm64-0.18.65.exe, the ARM64 build. Most Windows PCs run x64 processors, and an ARM64 installer will not run on them. So the most common Windows visitor, clicking the most visible button on the site, gets a file that fails to install. The x64 installer already exists on /download; the homepage just does not link it. I checked the homepage twice on November 9, 2026 and found the same link both times.
First action
Swap the homepage Windows href to openwork-win-x64-0.18.65.exe.
How to measure it
Windows first launches per week
- Now
- –
- Target
- +30%
- By
- 30 days
Steps
Swap the link
Point the homepage Windows button at the x64 installer.
Founding Engineer 15 minutes
Detect the platform
Read OS and architecture in the browser; default to x64 on Windows when unsure.
Founding Engineer 1 day
Recommend one build
On /download, highlight the detected build and move the rest under "Other builds".
Design Engineer 2 days
Generate links from releases
Build homepage and /download links from the release manifest on every release.
Founding Engineer 1 day
Add a release check
Fail the release if the default Windows link is not the x64 file.
Founding Engineer 2 hours
Track installs
PostHog events for download by OS and architecture, and first launch.
CTO 1 day
Compare
Windows first launches per download, four weeks before and after.
Founder & CEO 4 weeks
Why it works
Today, change the homepage Windows link to the x64 installer. Then make the hero buttons architecture-aware: detect OS and architecture in the browser (Chromium browsers report architecture through User-Agent Client Hints), default to x64 when unsure, and add an "Other builds" link to /download. Give /download the same detection so it highlights one recommended build and tucks the others away. Finally, generate the homepage and /download links from the release manifest in the release workflow, so each weekly version updates them automatically and a check fails if the default Windows link points at an ARM64 file. Track download clicks and first launches by OS and architecture in PostHog, which the site already runs.
For a free desktop app, the download button is the top of the funnel. A failed install never shows up as an error in web analytics; it looks like a visitor who simply did not convert. With ten releases in five weeks, a hand-edited link will drift again unless the links are generated. Windows laptops are also where most IT-managed seats sit, so these are the users most likely to become Team and Enterprise seats.
Ready to use
ChecklistDownload button check
[ ] Homepage Windows button -> openwork-win-x64-<version>.exe
[ ] Homepage macOS button -> detected Apple Silicon or Intel .dmg
[ ] Homepage Linux button -> x86_64 AppImage (ARM64 offered when detected)
[ ] "Other builds" link -> /download
[ ] /download highlights one recommended build
[ ] Links generated from the release manifest
[ ] Release fails if the default Windows link is ARM64
[ ] PostHog: download_clicked {os, arch}, first_launch {os, arch}Risks and how to handle them
Detection is wrong on some browsers
Default to x64 and always show the other builds one click away.
Windows on ARM users get the x64 build
Offer ARM64 when the browser reports it; Windows on ARM can also run x64 apps under emulation.
Evidence
- Your websiteHomepage (checked twice on November 9, 2026): H1 "Sovereign AI for knowledge workers" and subhead "Your AI workspace. Without vendor lock-in."; the hero platform links read macOS (to /download), Windows and Linux, but the Windows link downloads "openwork-win-arm64-0.18.65.exe", the ARM64 build, while the Linux link is the x86_64 AppImage; badges "Backed by YCombinator", "SOC 2 Type II" and 24.5K GitHub stars; "Free & open source · No account required to start"; "Talk to sales" opens a Google Calendar booking page; no customer logos, testimonials or newsletter signup.Source
- Your websiteDownload page: separate Windows "x64 Installer" and "ARM64 Installer", macOS Apple Silicon and Intel builds and four Linux builds (v0.18.65); no automatic platform detection and no guidance on which build to choose beyond the label "Apple Silicon (M1+)".Source
- Your websiteChangelog: ten releases from October 3 to November 5, 2026 (v0.18.56 to v0.18.65), including one-prompt migration of Claude Cowork and Code setups (v0.18.57), self-hosted OpenWork Web and team tools on AWS (v0.18.58), OneDrive and SharePoint files (v0.18.62), importing Claude chats into workspaces (v0.18.63) and Mac computer use across apps (v0.18.65); no RSS feed or email subscription.Source