Sheet W — Download
One installer.
No account. No sales call.
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
W-01 — Pricing
The whole table
$0
/ for now / per anything
No seats, no trial, no upgrade prompt yet. It watches builds. Charging for that felt rude, and also we have not decided how much to charge.
Download for WindowsW-02 — Windows will now panic
“Isn't commonly downloaded.” Correct. We're not Fortnite.
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. Run it from source instead — see below — or ask IT nicely, which never works but is good for your soul.
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 verifying over trusting? The source is right there, the installer is a plain per-user setup, and nothing here needs admin rights. Read it, build it, and be smug about it.
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 with repo, plus read:org for organisation discovery.
- 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 — Other options
Run it from source instead
For people who would rather read the code than trust an installer, which is a defensible position and also slower.
git clone https://github.com/meddlingidiot/Greenlight.git cd Greenlight dotnet run --project DevWatch # Settings -> add connection -> paste PAT -> Test -> Save dotnet test # optional, like all good ideas
Config: %AppData%\DevWatch\ · Tokens: Credential Manager · Excuses: standup
W-06 — 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.