Sheet W — Download
One installer.
One free account. No sales call.
Register, grab the Windows installer, paste a token, pick what to watch. If you are not up and running inside two minutes, the slow part was choosing which pipelines matter.
Windows 10 (1903+) / 11 · x64 · stable channel · installs per user · v0.0.1
Windows will now panic
What is actually happening
The moment the installer lands, Microsoft Defender SmartScreen will hold it at arm's length like a suspicious sandwich. It has not detected malware. It has detected unpopularity. SmartScreen's threat model is essentially a popularity contest: download counts, plus a code-signing certificate expensive enough to prove we have investors. We have neither. Hence “Publisher: Unknown”, which is technically true and emotionally devastating.
In Edge or Chrome downloads
The file shows a shield and “isn't commonly downloaded”. Open the ··· menu next to it and choose Keep. Delete is the default, because Windows would prefer you keep waiting for the build.
If the big scary panel appears
“Make sure you trust … before you open it.” Click Delete's little arrow, then Keep anyway. Yes, they hid the button you want inside the button you don't.
SmartScreen on first run
A blue “Windows protected your PC” dialog with one visible button. Click More info, then Run anyway. The information was there the whole time; it was simply embarrassed.
Corporate laptop, locked down
If IT has removed Keep entirely, do not fight the machine. Ask IT nicely, which never works but is good for your soul, or get them to allow the installer by name.
Why we haven't “just signed it”
An EV code-signing certificate costs a few hundred dollars a year and buys reputation, not safety. A signed installer that ruins your afternoon is still ruining your afternoon; it just has a name on it. Reputation also has to be earned by download volume, so the warning fades once enough of you ignore it. You are, in a very real sense, the antivirus.
Prefer caution over trust? The installer is a plain per-user setup that writes to your own profile and asks for no admin rights, so the worst it can do is clutter one account. Sandbox it, watch what it touches, and uninstall it in a click if you don't like it.
W-01 — The account
Yes, there's a sign-up now. No, we won't sell you.
The installer sits behind a free account: an email address, a password, and one click on a confirmation link. That is the entire form. It exists so we know how many people are actually running this and can reach you if a release goes wrong — not so a sales team can call you, because there is no sales team.
What we ask for
An email and a password. No company name, no team size, no phone number, no “how did you hear about us”. The account also gets you into the community forum eventually.
Product updates are a checkbox
Tick Subscribe to product updates on the registration form and you will hear when something ships. Leave it unticked and you will only ever get account mail — confirmation and password resets. It is off by default.
We never share your data with anyone
Not sold, not rented, not handed to a data broker, not passed to a partner, not fed to an ad network. Your email lives in our database and is used for the two things above. That is the whole policy, and it fits in a sentence on purpose.
The complete list of what we hold: your email address, your password as a hash, whether you ticked the updates box, and one line per download recording which installer you took and when. No IP address, no browser fingerprint, no analytics script on this page. Delete your account and the download history goes with it.
W-02 — Pricing
What it costs
$3
/ per person, per month · 2 machines
Or $30 a year, which is 2 months free. A seat is a person rather than a machine — it covers 2, your desktop and your laptop — one key covers your whole team, and open source projects pay nothing. The pricing sheet has the awkward questions answered.
Buy GreenlightThe installer is free either way — you only need an account
W-03 — Commissioning sequence
Three steps, one of them optional
- 01
Install
Run the setup. Greenlight installs for the current user and starts minimised in the tray. Grey icon, because it does not know anything yet.
- 02
Connect
Settings → add a connection. Organisation URL or GitHub owner, plus a Personal Access Token. Test, save, and it discovers what your token can see.
- 03
Pick your scope
Choose the projects, repos and pipelines that deserve your attention. Everything else stays out of the light.
W-04 — Requirements
What it expects of you
- Windows 10 (1903 or later) or Windows 11, x64.
- An Azure DevOps PAT with Code (read), Build (read), Identity/Profile (read).
- A GitHub PAT — fine-grained with Pull requests (read) and Actions (read), or classic with repo.
- Optional: a Velleman K8055 board and a three-lamp stoplight, for the full experience.
Updates
Greenlight updates itself in the background on the stable channel. No nag banner, no restart-now modal in the middle of a review.
Recent releases added GitHub as a second provider, custom sounds on build events, per-connection scope management, and a restart control for lamp plugins that lose their board.
W-05 — Something went sideways?
Two pages that cover it
Setup guide
Tokens, scopes, notifications, the plugin folder, and the settings JSON.
Support & FAQ
Everything people actually ask, answered tersely.