> ## 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.

# Everything Bach can do

> Every Bach feature in one place, grouped by what you want to do: build, shape the window, change Windows, update, deploy and test, with a link to each page.

Bach is one `bach.toml` in and one `Setup.exe` out. This page lists everything it does, grouped by what you want to achieve, and links to the page that explains each part. If you only read one page after [the quickstart](/docs/quickstart.md), read this one.

## Build the installer

> [card] [One config file](/docs/reference/config/overview.md)
>
> Settings instead of code, an editor schema, and one sentence per mistake that names the setting at fault.

> [card] [Starter config](/docs/reference/cli/init.md)
>
> `bach init` fills a `bach.toml` in for Rust, Tauri, Electron, .NET, Godot, Unity and more.

> [card] [Coming from Inno Setup or NSIS](/docs/reference/cli/import.md)
>
> `bach import` writes a first `bach.toml` from a `.iss` or `.nsi` script and lists what it could not convert.

> [card] [Builds anywhere](/docs/guides/ci.md)
>
> `bach` runs on Windows, macOS and Linux, so installers can come out of any CI, with a ready GitHub Action.

## Shape the window

> [card] [14 styles and 10 layouts](/docs/guides/customize-the-window.md)
>
> Soft gradients, a terminal, game looks, a side panel, a banner. Or your own fonts, colours, corners, pictures and logo.

> [card] [19 languages, light and dark](/docs/reference/config/text.md)
>
> The window follows the Windows language and theme. Every text can be replaced, per language.

> [card] [Choices and components](/docs/guides/choices-and-components.md)
>
> Shortcuts, start with Windows, `PATH`, and optional components, even ones downloaded only when ticked.

> [card] [Keyboard and contrast](/docs/concepts/installer-window.md#using-the-keyboard)
>
> Everything reachable with Tab, Home and End. Windows contrast themes make edges and rings solid.

## Change Windows, carefully

> [card] [Requirements](/docs/guides/requirements.md)
>
> WebView2, .NET, the Visual C++ runtime, a file, a registry key or a Windows build, checked before installing.

> [card] [Integration](/docs/guides/integration.md)
>
> `myapp://` link schemes, file types and right-click entries that never take over another app's.

> [card] [Registry, variables, programs](/docs/reference/config/registry.md)
>
> Registry values, environment variables and packaged programs setup runs for you.

> [card] [Services and firewall](/docs/reference/config/services.md)
>
> Windows services and firewall rules for machine-wide installs, rolled back if an update fails.

> [card] [Per user or every user](/docs/guides/machine-wide-installs.md)
>
> Per user needs no administrator prompt. `scope = "machine"` asks Windows once.

> [card] [Replace an old installer](/docs/guides/migrate-from-another-installer.md)
>
> The first Bach install removes the old Inno Setup, NSIS or MSI install.

## Update and release

> [card] [Updates over older installs](/docs/guides/updates.md)
>
> All or nothing: files are unpacked first and swapped in together. Background updates from GitHub releases or any https feed.

> [card] [Smaller downloads](/docs/guides/updates.md#update-patches)
>
> Update patches carry only what changed, down to a binary delta inside a file.

> [card] [Safer rollouts](/docs/guides/updates.md#staged-rollouts)
>
> Signed feeds, staged rollouts, a beta channel and private updates for protected apps.

> [card] [One-click releases](/docs/guides/releasing.md)
>
> A GitHub workflow raises the version everywhere, builds, tags and publishes.

## Deploy

> [card] [Silent installs](/docs/guides/silent-installs.md)
>
> `Setup.exe /S` with `--dir`, `--with`, `--without` and `--log`. Inno Setup and NSIS switches are accepted too.

> [card] [MSI, winget, Chocolatey, Intune](/docs/guides/msi.md)
>
> A Windows Installer package for Group Policy and Intune, and package manifests for the package managers.

> [card] [Online installer, ARM64, profiles](/docs/reference/config/profiles.md)
>
> An installer that downloads the newest version, an ARM64 build next to x64, and a portable ZIP or a company version.

> [card] [Access keys](/docs/reference/config/access.md)
>
> A private app that asks for a key and encrypts its files with it.

## Check and test

> [card] [Look before you build](/docs/guides/preview-and-build.md)
>
> `bach preview` and `bach watch` open the real window and install nothing.

> [card] [Test on a clean Windows](/docs/reference/cli/test.md)
>
> `bach test` installs, starts and removes the app in Windows Sandbox, or on a CI runner with `--here`.

> [card] [Verify and compare](/docs/reference/cli/diff.md)
>
> `bach verify` checks a file for damage, `bach diff` shows what changed between two releases, also as a pull request comment.

> [card] [Signing and trust](/docs/guides/signing.md)
>
> Sign with any signer, reproducible builds, SBOMs and build attestations for Bach itself.

## 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.
* A setup file that is cut off is undone by the next run.
* The payload format changes only with a new format version and a clear error for the old one.

Read [the safety rules](/docs/concepts/safety.md) and [the threat model](/docs/concepts/threat-model.md) for the details.

## Not for everything

Bach does not build drivers, run install-time scripts or make a small stub: a setup file adds about 10 MB to your app. See [Why Bach, and when to use something else](/docs/why-bach.md).


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