> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Bach builds Windows installers from one bach.toml with the bach command: bach init, bach check, bach preview, bach build. Installs are per user and need no administrator rights by default. installer.scope = "machine" installs for every user after one Windows prompt. On Windows, run setup files with Start-Process -Wait -PassThru in PowerShell, and give signtool arguments that start with the word sign.

# Why Bach, and when to use something else

> How Bach compares with NSIS, Inno Setup and WiX, what it covers by design, and the cases where another installer builder is the better choice.

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](https://nsis.sourceforge.io), [Inno Setup](https://jrsoftware.org/isinfo.php) and [WiX](https://wixtoolset.org) 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

> [accordion] No script
>
> Everything is a setting in one TOML file with an [editor schema](/docs/reference/setup/editor-support.md). Every mistake is reported as one sentence naming the setting at fault.

> [accordion] No admin prompt, unless you want one
>
> 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.

> [accordion] Updates that cannot half-fail
>
> 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.

> [accordion] A window people can read
>
> 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.

> [accordion] Builds anywhere
>
> `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

> [!WARNING]
>
> 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](/docs/guides/msi.md). Update patches carry only what changed inside a file, as a binary delta. See [Update patches](/docs/guides/updates.md#update-patches).

## Next step

> [card] [Quickstart](/docs/quickstart.md)
>
> Try Bach on your own app in about five minutes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.