download

get veil

One free download, no account, no email gate. Linux is real today. Windows is planned — shown honestly, not offered.

detected checking your system…
not right? pick manually:
linux supported
.AppImage · x86_64

Runs on any distro with FUSE — no package manager needed to launch it, though veil detects yours to write correct fix commands. Read-only checks, nothing changes without you running a specific fix.

download for linux what it does on linux →
windows planned
single .exe · not yet built

There is no windows build. This is not a disabled button dressed up as a feature — it's an honest "not yet." See the platform page for exactly what will and won't work once it ships.

what it will do on windows →

verify the download

check the checksum before you run anything

A checksum confirms the file you downloaded is byte-for-byte what was published — not that the publisher is trustworthy, just that nothing altered it in transit or on a mirror. Compare it yourself; don't take our word that it matches.

b6da4619d85f5a19337c11d8f56518d59f76210c52ccf6026a5ab7caab5d621a
  1. compute the hash locally

    Linux/macOS: sha256sum veil-0.2.1-x86_64.AppImage. Windows (once a build exists): certutil -hashfile veil.exe SHA256.

  2. compare, character by character

    The output must match the checksum above exactly. If it doesn't, don't run the file — re-download from the original release link, not a mirror.

what happens when you open it

the plain, unglamorous reality per OS

linux

AppImage, no signature dialog

  • most distros don't gate unsigned binaries the way Windows does — you chmod +x it and it runs.
  • some desktop environments show a "trust this executable?" prompt the first time — that's your file manager, not veil, asking.
  • no code-signing certificate exists for this build. Verify the checksum instead of trusting a signature that isn't there.
windows

expect SmartScreen, once it ships

  • a solo developer's .exe has no reputation with Microsoft's SmartScreen — expect an "unrecognized app" warning even on a legitimate, unmodified build.
  • a paid EV code-signing certificate is the only way to skip that warning, and it costs real money yearly for no functional benefit — that trade isn't made yet.
  • clicking through the warning after verifying the checksum yourself is a reasonable choice; clicking through it blind is not.