macbackup / personal utility
A backup you can inspect and recover.
macbackup runs locally on the owner's Mac. It selects files by explicit rules, transfers them with rclone to the owner's configured storage, and keeps previous copies in a separate history.
Two areas
Readable where useful. Encrypted where needed.
The destination follows the original Mac path, so a file can be found again without inventing a second folder scheme.
Files you can open
Selected documents remain readable in the owner's Google Drive account, including from a phone when the provider supports the file type.
Credentials stay encrypted
Private paths, such as SSH and rclone configuration, are encrypted locally with rclone crypt before upload. Git metadata is routed to this area by policy.
A deliberate workflow
Inspect. Run. Recover.
The selector is local. Cloud checks and transfers are separate operations. Excluding a path later stops future updates; removing copies already in current or history is an explicit step.
macbackup check macbackup preview --target google macbackup run --target google macbackup status macbackup versions ~/Documents/example.txt \ --target google
What the backup keeps
Current files and changed copies.
History is organized by run. Each history folder holds files replaced or removed during that run; it is not a complete snapshot of every folder.
Paths and rules
Plain, private and exclusion lists are combined with names that require exact inclusion, such as .env files.
Visible progress
Run shows byte and file progress, speed and active paths. Interrupted runs retain their last available partial counters.
Explicit choices
Versions, restore, verify and forget let the owner inspect copies and choose recovery or removal.
Google OAuth
Access to the owner's backup files.
The application uses Google OAuth with the drive.file scope to create, list, read, update and delete backup files authorized to it. Authorization happens in the browser; file transfers run directly between the Mac and the storage provider.
This website is informational. It does not sign in to the owner's account or host the backups.
How data is handled
The owner controls selection, encryption keys, retention and revocation. The public privacy page explains the Google access and the website.
Support: contact@kevinmuka.dev