Comparison

Azivault vs Time Machine.

Time Machine is the built-in Mac backup baseline. Azivault is for Mac users who need portable encrypted repositories, S3-compatible storage, Finder restore browsing, and app-independent recovery.

Last reviewed: May 29, 2026

Product scope

Time Machine is Apple's built-in macOS backup system. It backs up Mac user data to supported destinations such as directly attached USB or Thunderbolt storage, NAS devices that support Time Machine over SMB, and some legacy Apple network backup devices.

Azivault is a native macOS backup app whose repository format is a first-class product surface. It backs up selected folders to folder or S3-compatible destinations, exposes restore browsing through Finder, and includes the azi CLI for app-independent verification, search, restore, export, and S3-compatible hydration.

Default baseline vs. specialist tool

Time Machine is the default. It is already installed, already integrated with macOS settings, and already understood by Apple Support, Migration Assistant, and many Mac users. That makes it the first answer for basic backup hygiene.

Azivault is a specialist tool. Its value begins where Time Machine's default model is too narrow: user-selected repositories, S3-compatible storage, encrypted path/name metadata, documented repository semantics, app-independent recovery commands, and no app-operated telemetry or relay service.

Backup scope

Time Machine is broad. Apple says it backs up files on the Mac that were not part of the macOS installation, such as apps, music, photos, and documents. It is designed for whole-Mac user recovery rather than one folder at a time.

Azivault is plan-oriented. Users select source directories and destinations. This is more explicit and less magical. It is better for controlled backup sets and repository portability, but it is not the same as "back up my whole Mac and later migrate everything."

Storage destinations

Time Machine supports local disks and network destinations that meet Apple's requirements. Apple currently describes APFS or APFS Encrypted disks as the preferred format for a Time Machine backup disk, and network Time Machine over SMB is supported when the network server supports the required behavior.

Azivault supports folder and S3-compatible destinations. That makes it a better fit for object storage, provider choice, and offsite cloud backup without relying on a Mac-specific network Time Machine target. It also keeps the same repository object format across folder and S3-compatible storage.

Restore experience

Time Machine's restore UX is excellent for ordinary Mac users. It can restore individual files from the Time Machine interface, recover previous document versions through app or Finder flows, restore or migrate a Mac with Migration Assistant, and use local snapshots for recent previous versions when the backup disk is not attached.

Azivault's restore UX is different: browse backup snapshots in Finder through a read-only File Provider domain, restore through the app, use azi restore for one file, use azi export for a whole completed run, or hydrate S3-compatible storage into a local repository and then verify/export.

Encryption and metadata privacy

Time Machine can encrypt backup disks, and Apple recommends encryption as the best way to keep backups secure. Time Machine encryption protects the backup disk.

Azivault treats encryption as mandatory for supported repositories. File blobs are compressed and encrypted, file and directory names are encrypted in catalog rows and checkpoints, and plaintext absolute source or destination paths are not stored in portable repository metadata. Azivault encryption is part of the repository format and recovery contract.

Repository portability

Time Machine is Apple-native and Apple-owned. That is a strength while macOS support is available: integration is deep and maintenance is Apple's responsibility. But Apple does not present Time Machine as a public, app-independent repository format with a documented third-party restore CLI.

Azivault's portability is explicit. The repository format is documented, compatibility gates are defined, and azi is expected to restore/export without the GUI app. This matters when backups should remain recoverable even if the app fails, disappears, or stops being maintained.

Retention and cleanup

Apple describes Time Machine as automatically making hourly backups for the past 24 hours, daily backups for the past month, and weekly backups for previous months, with storage managed as the backup disk fills. That is exactly what most users want.

Azivault exposes completed catalog runs as restore/export points and treats destructive cleanup as a separate, audited feature. That is safer from a repository-design perspective, but it requires product-level retention UX. Time Machine is better for users who want retention to be automatic and invisible.

Local snapshots

Time Machine local snapshots are a major advantage. Even when the external backup disk is unavailable, APFS local snapshots can recover recent previous file versions. Apple's current guide says local snapshots are created hourly and saved for up to 24 hours or until space is needed.

Azivault does not replace that system feature. It uses stable source handling and cataloged backup runs, but it is not a systemwide APFS local snapshot manager for recent file-version recovery.

Cloud-only files

Time Machine's behavior around cloud-provider placeholders is not a product-level policy surface in the same way Azivault's is. Apple support guidance for Time Machine troubleshooting can advise waiting for sync or excluding sync folders, but Time Machine does not expose a per-plan policy like "report, skip, or materialize changed cloud-only files."

Azivault makes this explicit. Its cloud-only file policy defaults to reporting errors, can skip placeholders by user choice, or can download changed files from the live source path and re-evict them after backup. It also avoids treating unavailable cloud-only bytes as deletion.

Business model

Time Machine has no separate app price and no subscription. It is part of macOS. The user pays only for storage hardware or a compatible network destination.

Azivault uses App Store subscriptions for backup access. New backup runs require active access, but restore remains available regardless of billing state. That is a meaningful promise, but Time Machine is still simpler: there is no backup-app billing layer.

When to choose Time Machine

• You want the simplest reliable backup for a Mac.
• You want built-in macOS support with no extra app subscription.
• You want whole-Mac user-data backup and Migration Assistant restore.
• You have a local external disk or compatible NAS.
• You want automatic retention and do not need explicit repository semantics.
• You are setting up backup for a non-technical user.
• You need recent local snapshots for accidental changes or deletions even when the backup disk is not attached.

When to choose Azivault

• You need S3-compatible or provider-controlled offsite storage.
• You want a documented repository and app-independent CLI recovery.
• You want mandatory repository encryption and encrypted file/directory names.
• You want backup snapshots browsable through Finder as a read-only restore domain.
• You want selected-folder backup plans rather than whole-Mac backup behavior.
• You want restore access to remain available even when backup billing is inactive.
• You want explicit cloud-only-file handling.

FAQs

Is Azivault a Time Machine replacement?

Not for most users. Time Machine is the built-in Mac backup baseline and is better for whole-Mac user-data restore and Migration Assistant. Azivault is better for portable encrypted repositories, S3-compatible storage, and CLI recovery.

Should I use Time Machine or Azivault?

Use Time Machine first unless you have a specific need Time Machine does not cover. Use Azivault when you need offsite S3-compatible backup, documented repository recovery, or stronger repository-level encryption/privacy semantics.

Should I use both?

Yes, for important data. Time Machine and Azivault protect against different failure modes. Time Machine is excellent for local Mac recovery. Azivault is better for portable, provider-controlled, app-independent recovery.

Does Time Machine back up everything?

No. Apple's current documentation says Time Machine backs up files not part of the macOS installation, such as apps, music, photos, and documents, and that it does not back up system files or apps installed during macOS installation.

Does Azivault restore a whole Mac like Migration Assistant?

No. Azivault is not a full Mac migration system. It restores selected backup contents from Azivault repositories. Time Machine plus Migration Assistant is the better whole-Mac setup path.

Which has better encryption?

They protect at different layers. Time Machine can encrypt the backup disk. Azivault makes encryption mandatory for supported repositories and encrypts file/directory names in repository metadata.

Which is better for cloud backup?

Azivault. Time Machine can use supported network destinations, but it is not an S3-compatible or object-storage backup tool. Azivault is designed for folder and S3-compatible destinations.

Which is easier to restore from?

For ordinary local Mac restore, Time Machine. For app-independent repository restore/export from a documented format, Azivault.

Can Azivault read Time Machine backups?

No. Azivault and Time Machine use different backup formats. Azivault should not read or write Time Machine backup data unless a deliberate import/export feature is designed and tested.

Does Time Machine have a CLI?

macOS includes tmutil for Time Machine administration, but Apple does not position it as a portable backup-format restore/export contract. Azivault's azi CLI is specifically part of the app-independent recovery model.