Download

Download Bandura for macOS, Windows and Linux.

The complete IDE: a visual graph and a code editor over one plain-text .aether file, offline, no account.

Free for personal and commercial use. No trial, paid seat or subscription.

v1.0.0-rc.9 · macOS · Windows · Linux

Older builds may still show a retired licence reminder; no payment is required. Terms of use.

Every platform, built on its own machine

Pick your system.

Direct downloads. No signup or payment. macOS first-launch instructions.

macOS

First launch: Unsigned early access: not Developer ID-signed or notarized by Apple. After opening Bandura once, use System Settings → Privacy & Security → Open Anyway. See the first-launch instructions on this page.

Windows

First launch: Unsigned until an OV certificate is bought, so SmartScreen shows a warning: More info → Run anyway. It installs per-user, so you don't need admin rights.

Linux

Every release on GitHub Older versions, exact file sizes, and the release notes as tagged

Files are served from GitHub Releases on a public, releases-only repository: the app's source is private, the downloads are not. Every asset is built in CI on the platform it targets, and older versions stay up permanently. What changed in v1.0.0-rc.9 is on the changelog, and if a security review has to clear this before it reaches a machine, that page is written for them.

What it needs

  • Windows: 10 or 11, 64-bit. Installs per-user, so no admin rights are needed.
  • Linux: a 64-bit desktop with glibc 2.28 or newer, which covers Ubuntu 20.04 and later, Debian 10 and later, and Fedora 32 and later. AppImage needs FUSE; the .deb does not.
  • macOS: macOS 12 Monterey or newer, Apple Silicon or Intel. These early-access builds are not notarized; see the first-launch instructions on this page.
  • No GPU requirement, and no network requirement at all once installed. Exact file sizes are listed on the release beside each asset.

Confirm it works

# 1. The app: open it, then "Explore examples" on the welcome screen.
#    A sample project opens, and one of its flows runs against a public API.

# 2. Or prove the engine works without opening anything, from any directory:
npx @bandura/cli --version
npx @bandura/cli run --help

# 3. Exit code 0 here confirms the CLI help command succeeded.
#    Next, run your own .aether flow to test the API.
echo $?

None of this needs an account, a key, or an API of your own. If step 2 prints a version, the engine that runs your flows in CI is on your machine and working.

Check what you downloaded

Windows and Linux installers have a SHA-512 published beside them, in latest.yml for Windows and latest-linux.yml for the AppImage and the .deb. The digests are base64 rather than hex, so the usual one-liner needs a second step:

# Linux or macOS: prints the base64 SHA-512
openssl dgst -sha512 -binary Bandura-1.0.0-rc.9-linux-x64.AppImage | openssl base64 -A

# Windows PowerShell. Resolve-Path first, because [IO.File] reads from the process
# directory rather than the one your prompt is showing.
$f = Resolve-Path .\Bandura-1.0.0-rc.9-win-x64.exe
[Convert]::ToBase64String([Security.Cryptography.SHA512]::Create().ComputeHash([IO.File]::ReadAllBytes($f)))

For macOS, download SHA512SUMS-mac.txt into the same folder as your DMG, then run shasum -a 512 -c SHA512SUMS-mac.txt --ignore-missing. An OK result confirms the file matches. The macOS checksums use hex encoding.

Match the output against the sha512 line for your file. This catches a corrupted or truncated download, which is what it is for. It is not a signature of ours: the manifest is hosted beside the file it describes, so it cannot prove the file was not replaced at the source. Signing is what proves that, and where signing stands is written down rather than implied.

macOS · unsigned early access

Opening Bandura on your Mac.

These builds are not Developer ID-signed or notarized by Apple. macOS will ask you to approve the first launch. Choose the Apple Silicon or Intel download that matches your Mac.

  1. Download the DMG, open it, and drag Bandura into Applications.
  2. Open Bandura from Applications once. Dismiss the warning if macOS blocks it.
  3. Open System Settings → Privacy & Security, scroll to Security, and select Open Anyway for Bandura.
  4. Confirm Open and authenticate if your Mac asks.

Only approve the copy you downloaded from the links on this page. A managed work Mac may not allow this exception. If macOS reports that the app is damaged or will harm your computer, stop and contact us.

Apple’s first-launch instructions. No date is set for a signed release.

Or skip the app entirely

The CLI is a single native binary.

Same engine as the desktop app, no Electron, no runtime to install. Built for CI and for people who'd rather stay in the terminal. It exits non-zero on failure and speaks JUnit and GitHub annotations.

On npm now

# The headless runner. Same engine, for terminals and CI
npm install -g @bandura/cli
bandura --version

Reads the same .aether files as the desktop app, from the same repo. See the CLI docs.

What you're agreeing to

  • Nothing is collected. Bandura collects nothing: no telemetry, no analytics, no crash reports, no account.
  • Two destinations, both switchable. Beyond running the requests your flows describe, the app reaches exactly two places on its own behalf: the AI provider whose key you supply, and GitHub. Once a day it asks our public releases list whether a newer version exists, so it can tell you, carrying no identifier, no licence key and nothing about your machine, and a single switch in Settings turns it off. If you then ask for the update, it fetches the installer from that same public release. Automatic downloads ship off. We receive nothing from either destination.
  • Free for personal and commercial use. No trial, paid seat or activation is required. Older builds may still show a dismissible reminder; the current terms also permit their free use.

Optional, and it changes nothing

Support Bandura if it helps you.

Support is optional and unlocks no extra features. Personal and commercial use are free either way.

Support on Patreon