Skip to main content
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, read this one.

Build the installer

One config file

Settings instead of code, an editor schema, and one sentence per mistake that names the setting at fault.

Starter config

bach init fills a bach.toml in for Rust, Tauri, Electron, .NET, Godot, Unity and more.

Coming from Inno Setup or NSIS

bach import writes a first bach.toml from a .iss or .nsi script and lists what it could not convert.

Builds anywhere

bach runs on Windows, macOS and Linux, so installers can come out of any CI, with a ready GitHub Action.

Shape the window

14 styles and 10 layouts

Soft gradients, a terminal, game looks, a side panel, a banner. Or your own fonts, colours, corners, pictures and logo.

19 languages, light and dark

The window follows the Windows language and theme. Every text can be replaced, per language.

Choices and components

Shortcuts, start with Windows, PATH, and optional components, even ones downloaded only when ticked.

Keyboard and contrast

Everything reachable with Tab, Home and End. Windows contrast themes make edges and rings solid.

Change Windows, carefully

Requirements

WebView2, .NET, the Visual C++ runtime, a file, a registry key or a Windows build, checked before installing.

Integration

myapp:// link schemes, file types and right-click entries that never take over another app’s.

Registry, variables, programs

Registry values, environment variables and packaged programs setup runs for you.

Services and firewall

Windows services and firewall rules for machine-wide installs, rolled back if an update fails.

Per user or every user

Per user needs no administrator prompt. scope = "machine" asks Windows once.

Replace an old installer

The first Bach install removes the old Inno Setup, NSIS or MSI install.

Update and release

Updates over older installs

All or nothing: files are unpacked first and swapped in together. Background updates from GitHub releases or any https feed.

Smaller downloads

Update patches carry only what changed, down to a binary delta inside a file.

Safer rollouts

Signed feeds, staged rollouts, a beta channel and private updates for protected apps.

One-click releases

A GitHub workflow raises the version everywhere, builds, tags and publishes.

Deploy

Silent installs

Setup.exe /S with --dir, --with, --without and --log. Inno Setup and NSIS switches are accepted too.

MSI, winget, Chocolatey, Intune

A Windows Installer package for Group Policy and Intune, and package manifests for the package managers.

Online installer, ARM64, profiles

An installer that downloads the newest version, an ARM64 build next to x64, and a portable ZIP or a company version.

Access keys

A private app that asks for a key and encrypts its files with it.

Check and test

Look before you build

bach preview and bach watch open the real window and install nothing.

Test on a clean Windows

bach test installs, starts and removes the app in Windows Sandbox, or on a CI runner with --here.

Verify and compare

bach verify checks a file for damage, bach diff shows what changed between two releases, also as a pull request comment.

Signing and trust

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 and the threat model 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.