Back up what matters. Verify it. Know what you can recover.

VaultSync is MIT-licensed open-source software. Direct GitHub builds and the Microsoft Store edition are free and contain the same product features; the Store provides managed installation and updates.

• No subscription, recurring payment, required account, advertising-supported tier, or proprietary VaultSync storage service.
• Windows: Microsoft Store or direct x64 installer.
• macOS: Apple Silicon ARM64 and Intel x64 DMG builds.
• Linux: x64 AppImage; x64 and ARM64 DEB packages and tarballs.
• Direct Windows and macOS GitHub builds are currently unsigned and may trigger SmartScreen or Gatekeeper warnings.

VaultSync protects registered folders that are available through the filesystem. It can route projects automatically, use a preferred destination, or write to multiple destinations.

• Sources include project folders, workspaces, repositories, creative work, documents, and other selected folders.
• Presets cover Unity, Unreal Engine, Godot, GameMaker, .NET, Node.js, Python, Rust, Java, Go, Blender, video, music production, Docker, VS Code, and JetBrains workflows.
• Presets omit common generated, cache, build, or disposable files; review the selected rules and use No preset or custom rules when needed.
• Destinations include local folders, internal or external drives, removable storage, NAS devices, mounted network shares, SMB shares, pre-mounted NFS shares, and locally mounted or synchronized cloud-storage folders.
• SMB automatic mounting is supported on Windows and macOS with credential profiles. Pre-mounted NFS destinations work, but automatic NFS mounting is not supported on macOS.

Snapshots can be created independently and every backup records a fresh project snapshot so its restore point remains tied to the state that produced it.

• Track added, modified, deleted, and unchanged files with history, size changes, changed paths, labels, notes, tags, and protected or known-good markers.
• Run manual or scheduled backups per project or across all projects.
• Use full backups, incremental file-copy mode, plain folders, encrypted archives, single or multiple destinations, and timestamped restore points.
• Incremental means incremental file copying; it is not block-level imaging, synthetic-full, deduplicated, or necessarily chain-based incremental backup.
• Filesystem copy and sync use rsync on macOS/Linux and robocopy on Windows, so exact behavior can vary by OS, filesystem, destination, and selected mode.

Optional archive backups are assembled and encrypted locally before the finished artifact is transferred to its destination.

• Global and per-project encryption policies, OS credential-store integration where supported, session-only password handling, manual locking, and automatic lock timeout.
• Password-gated archive opening and restore, password changes, archive-format validation, and limits on excessive embedded key-derivation parameters.
• Passwords and secret key material are not intentionally exported through shared backup metadata.
• Encrypted and unencrypted backups are clearly distinguished. Snapshot Explorer cannot currently browse encrypted archives, though they remain restorable through the password-gated workflow.

VaultSync combines hash-based checks with recovery context, while making clear that verification is evidence—not a substitute for a real test restore.

• Per-project source-to-backup hash comparison, full verification, verification policies, CLI verification, integrity diagnostics, and destination-health context.
• Recovery workspace assessments for project readiness, coverage, destination health, and protected or known-good restore points.
• Ready and Needs Attention filters, per-project triage, restore-point review, and portable Markdown recovery reports.
• Guided isolated restore drills and restore-plan simulations help produce stronger recovery evidence without modifying the original source.

Backup and snapshot history is stored in a local SQLite database, with metadata designed to retain useful context when destinations or machines change.

• History records backup type, origin-machine context, protection and encryption state, non-secret encryption descriptors, and tombstones for removed projects, snapshots, and backups.
• Metadata synchronization shares history and backup visibility; it does not copy or replace the backup payload itself.
• Imported entries retain their origin-machine context.
• Per-project retention can keep the newest configured number of backups while Keep and protected-snapshot markers prevent automatic pruning.
• Retention simulation, orphan-snapshot cleanup, quota suggestions, and maintenance-window jobs expose cleanup effects before data is removed.

Snapshot Explorer can inspect supported backup contents without restoring a complete backup, while desktop and CLI restore paths cover full-project recovery.

• Browse folders and compatible archives, expand nested folders, search, select individual files, and preview supported text, source, and configuration files.
• Binary previews are rejected safely; text previews include line numbers, horizontal scrolling, and lightweight syntax coloring.
• Restore a complete project, a folder or compatible archive, an encrypted backup after password entry, or selected Explorer items.
• Restore-target safety checks confine paths to the intended target root, and a confirmation step explains the planned operation before it begins.
• Encrypted archive browsing is not supported in Snapshot Explorer v1.

The desktop application and .NET CLI expose day-to-day workflows as well as lower-level inspection and repair tools.

• Scheduling, per-project automation controls, bandwidth limits, quiet hours, maintenance windows, adaptive compression, tray state, notifications, and background operation.
• Destination checks, capacity planning, startup integrity scans, Doctor workflows, configuration recovery, metadata repair and conflict review, import, validation, maintenance, support export, and update diagnostics.
• Stable and optional Beta update channels use GitHub Releases, with configurable checks, full installers, and platform-specific patch archives.
• Patches only apply to explicitly supported base versions; unsupported or incompatible versions fall back to a full installer.
• CLI workflows include snapshot, backup, sync, verify, diff, watch, restore, diagnostics, and automation-oriented use.

VaultSync includes defensive engineering and automated analysis, but these measures are not a formal independent security audit.

• Support bundles are redacted; shared metadata omits secret encryption material; imported metadata is treated as read-only; metadata updates are atomic; SQLite integrity and lock contention are hardened.
• Not a full-disk imaging, bare-metal recovery, bootable-media, phone/tablet backup, enterprise endpoint-management, or centralized multi-user administration product.
• No hosted cloud backend, and direct cloud-provider API integrations are not the primary destination model.
• Network-share reliability depends on the operating system, network, and storage configuration; presets may exclude files intentionally and should be reviewed.
• Maintain multiple independent backup copies and test restores regularly.