Download

Get Maze.

The first release is on its way; until then, the links lead to GitHub Releases. Maze is pre-alpha: reading, writing, search, triage and agents work, but expect rough edges. Maze keeps all mail in your IMAP accounts, so another mail client keeps working alongside.

macOS

macOS 13 or later

A signed and notarized .dmg. Open it and drag Maze to Applications.

Apple Silicon Intel

Maze-<version>-macos-aarch64.dmg
Maze-<version>-macos-x86_64.dmg

Linux

preview

A tarball for x86_64 and aarch64 is built with every release. Linux gets less testing than macOS for now and shows mail in the reader view only (the original HTML engine is in the macOS builds); packaging (Flatpak) is coming.

x86_64 aarch64

tar --zstd -C ~/.local \
  -xf Maze-*-linux-x86_64.tar.zst
~/.local/mazemail.app/bin/mazemail

From source

Rust

The toolchain is pinned with mise. On macOS you also need the Xcode Command Line Tools.

git clone https://github.com/pmig/maze
cd maze && mise install
cargo run --release

A source build is a dev build with its own data directory and keychain item, and never updates itself.

Maze keeps itself current

Maze checks for updates every hour and after your Mac wakes, installs them in the background and shows Restart to update in the title bar. Every update is verified (a signed manifest, the SHA-256 of the download, and the same Apple team signature) and swapped in one step. If a new version keeps failing to start, Maze offers to roll back. Keep Maze in Applications so it can replace itself.

How updates work

No Homebrew, on purpose

The .dmg is the only way in, followed by the built-in updater. A package manager would fight the updater over the same app, so there is deliberately no Homebrew cask (ADR-010).

Requirements

macOS 13 Ventura or later, on Apple Silicon or Intel.
Linux: x86_64 or aarch64, with a running Secret Service (GNOME Keyring or KWallet), which holds Maze's storage key, and bubblewrap (bwrap) if you use agents.
An IMAP account (Gmail, Microsoft 365, iCloud, Fastmail and others are detected), or mail to import.
Gmail works with an app password; “Sign in with Google” and “Sign in with Microsoft” need your own OAuth client ID for now (Gmail, Microsoft).
Agents (optional): an account with the agent's provider (Claude, ChatGPT, Google, Cursor and others). Maze downloads the agent and the Node runtime it needs itself (Agents).

Verifying a download

Release builds are signed with a Developer ID and notarized by Apple. After installing, check the signature and the notarization:

spctl --assess --type execute -vv /Applications/Maze.app
codesign -dv /Applications/Maze.app
xcrun stapler validate /Applications/Maze.app

spctl should say accepted and source=Notarized Developer ID. GitHub shows the SHA-256 of every file on the release page; compare it with shasum -a 256 Maze-*.dmg. Builds that aren't notarized (CI artifacts) need a one-time Open Anyway in System Settings → Privacy & Security.