Philosophy

Built for backups you can trust

A backup app has one job above all: give you your files back. Azivault starts there, with three rules: never touch the originals, keep old repositories readable, and encrypt before writing to storage.

Never corrupt files

The app must never modify source files. Backup writes must be atomic, catalog updates must be transactional, and failures must leave the last known-good backup readable.

Backups must remain accessible without the app

The backup repository format must be documented and portable. If the GUI app fails, is removed, stops being maintained, or paid automation access ends, you must still be able to recover data with documentation and the azi CLI.

Never break existing backups

New features must preserve the ability to read old repositories. The app and CLI must be able to read repositories created with older versions of the app. Migrations must be non-destructive.

Files are encrypted locally

All files are encrypted on the user's device before being stored in the backup repository, whether a local folder or remote location. This helps prevent anyone without the recovery material from accessing the data: file names and contents are encrypted.

macOS native

Azivault is a Swift and SwiftUI app, not a web interface wrapped for the desktop. It uses macOS features such as Keychain, File Provider, and sandboxed background helpers directly. There are no third-party app frameworks or libraries. The result must feel familiar on a Mac: normal windows and menus, Finder-based restore browsing, and an App Store sandbox rather than a separate cross-platform runtime.