Download Legato
Version 0.3.94 · September 24, 2026Free, no account, no key. Linux and Android are on the way.
- Signed with our own certificate soonWindows shows our name where it would otherwise say “Unknown publisher”.
- Signed and notarised by AppleIt opens with a double click. macOS raises no “unidentified developer” wall.
What happens on the first launch
You are downloading a browser from us directly, not from a store, so both systems will say something the first time. Here is exactly what, and which button to press.
On Windows
The installer puts the browser in your own user folder and never asks for an administrator password.
Windows shows a blue window headed “Windows protected your PC”, and the only button on it says “Don’t run”. Do not stop there. Press the link “More info” first, and the second button appears, “Run anyway”. That is the one you need.
Where that window names the publisher it will say “Unknown publisher”, and that is expected right now: our signing certificate has been bought and is going through the certificate authority’s identity checks. Until it is issued there is nothing to sign the file with. The Mac build is already signed and notarised by Apple; Windows is the one still waiting.
So the name is not what tells you this file is ours. The number below does. It is the checksum of the exact file we published: run the command, compare, and you have checked the file itself rather than a label on it.
On a Mac
The image opens with Legato on the left and a shortcut to Applications on the right: drag the first onto the second, and that is the install.
The first time you start it, macOS asks once whether to open an app downloaded from the Internet. The buttons are “Open” and “Cancel”, and “Open” is the default one, so Return presses it. The question is asked once and never comes back.
There are two files, one per processor, and the wrong one will not start at all. If you do not know which Mac you have: Apple menu, “About This Mac”. The line says either “Apple M…” or “Intel”. With VoiceOver, that window reads out on its own.
Check that the file is the one we published
The number below belongs to that exact file. Run the command, and compare what it prints with what is written here: if they match, nothing was changed on the way to you.
On Windows · File: Qiksy-Legato-Setup-0.3.94.exe · Size: 180 MB
SHA-256: 173b4a58f0d28a8938518a84741febdb0b2fe3eb04ace8d04bcc433a3b75fb8e
Check it with: certutil -hashfile "%USERPROFILE%\Downloads\Qiksy-Legato-Setup-0.3.94.exe" SHA256
On a Mac · Apple Silicon · File: Qiksy-Legato-0.3.94-arm64.dmg · Size: 191 MB
SHA-256: b6b5e9fdca06c41fd61cb674b1f00cf99a4b445ff3f616148a49f17093a1d208
Check it with: shasum -a 256 ~/Downloads/'Qiksy-Legato-0.3.94-arm64.dmg'
On a Mac · Intel · File: Qiksy-Legato-0.3.94-x64.dmg · Size: 205 MB
SHA-256: c7dd1b228ef1e6e9255200340fcfdc7198d82ada5ba77158518573a16da0402b
Check it with: shasum -a 256 ~/Downloads/'Qiksy-Legato-0.3.94-x64.dmg'
Accessibility where the developer never built it
A Chromium browser with a repair engine. The engine may only ADD semantics, and only from a closed whitelist: the site’s markup is never rewritten, and the page never changes visually.
- 1operation the engine can perform: set an attribute
- 12attributes it may set; nothing else passes the validator
- 24ARIA roles it may assign; composite widgets are out of scope
- 25interface languages, following the system language
what one repair actually looks like
- op: set-attr · selector: "button.icon-cart" · attr: aria-label · value: "Basket, 3 items"
- Applied: the button now has a name. The structure of the page is unchanged.
- aria-hidden is not on the whitelist and will not be: hiding content from a reader can do more harm than doing nothing at all.
- Anything the validator does not recognise is dropped in silence. Wrong ARIA is worse than missing ARIA.
The rule-based repairs run offline, on the person’s own computer. AI repair, when it is asked for, sends the structure of that one page and nothing else.