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 should be atomic, catalog updates should be transactional, and failures should leave the last known-good backup readable.

Backups should be accessible without the app

The backup repository format should be documented and portable. If the GUI app fails, is removed, stops being maintained, or the subscription expires, a user should 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 should be able to read repositories created with older versions of the app. Migrations should 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 ensures that only the user has access to their 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 should be familiar to a Mac user: normal windows and menus, Finder-based restore browsing, and an App Store sandbox rather than a separate cross-platform runtime.