Skip to main content
Bach covers the common case, an app that installs for one user (or for every user, with one setting), with settings instead of code. Tools like NSIS, Inno Setup and WiX can build almost any installer, and ask you to learn a scripting language or an XML schema to do it. This page explains the trade-off.

What Bach gives you

Everything is a setting in one TOML file with an editor schema. Every mistake is reported as one sentence naming the setting at fault.
Apps install per user into %LOCALAPPDATA%\Programs and only write to the user’s own folders and HKCU. For every user of a computer, installer.scope = "machine" installs into Program Files after one Windows prompt.
A newer setup file updates an install in place. Files are unpacked first and swapped in together, and if one is locked, everything is put back. Files the new version no longer ships are removed.
19 languages built in, following the Windows display language. Light and dark mode, and Windows contrast themes. Every text replaceable. Every choice reachable with Tab.
bach runs on Windows, macOS and Linux, so installers can come out of any CI. Setup files need no .NET and no Visual C++ runtime, because the C runtime is linked in.

Product principles

  • Simple for the developer. One small config file with sensible defaults. No script language, no compiler, nothing to learn first.
  • Calm for the end user. One window, few choices, honest progress, readable errors with “Try again”, light and dark mode. No administrator prompt unless the app asks for one.
  • Safe by construction. Packaged paths cannot leave the install folder. The uninstaller removes only what it installed, and deletes data only when the user asks, and only inside the user’s profile.
  • Updates just work. A newer setup file over an install updates it in place.
  • Stable format. Setup files in the wild keep working. The payload format changes only with a new format version and a clear error for the old one.

Use something else when

Bach is not the right tool if you need any of the following.
  • Drivers built in.
  • Custom install-time scripts.
  • A small stub. A Bach setup file adds about 10 MB to your app.
For Group Policy, Configuration Manager and Intune, bach build --msi also writes a Windows Installer package. See Windows Installer packages. Update patches carry only what changed inside a file, as a binary delta. See Update patches.

Next step

Quickstart

Try Bach on your own app in about five minutes.