Why VaultSync exists
VaultSync started out of frustration.
Most backup tools I tried had one or more of these problems:
- transfers slowing down or stalling on network mounts
- very little visibility into folder growth or changes
- automatic jobs that failed silently
- restore / cleanup actions that felt opaque or risky
I wanted a tool that showed exactly what was happening — and why.
Core philosophy
Transparency over automation
- what is being scanned
- what is being copied
- what changed
- what will be deleted or restored
No hidden behavior.
Reliability on real-world NAS setups
- go offline
- stall
- behave inconsistently
VaultSync is built with this reality in mind.
Safety first
- No destructive actions without visibility
- No silent cleanup
- No guessing what will be touched
If something can go wrong, the user should see it coming
Open-source by default
- behavior can be verified
- issues can be understood
- trust is earned, not assumed
High-level roadmap (evolving)
[1.4.0] Per-project destination selection when multiple destinations are configured. [1.4.0] Faster snapshot scanning on large projects (skip unchanged folders, cache heuristics). [1.4.0] Dry-run backups (estimate size/time before starting). [1.5.0] Backup encryption and password-protected backups. [1.5.0] Backup bandwidth limits and quiet hours (avoid congesting networks). [1.5.0] Snapshot diff summaries (top changed folders/files, size deltas). [1.6.0] Richer restore flows (selective restore, dry-run previews, conflict prompts). [1.6.0] Restore point browser with compare and timeline view. [1.6.0] Smarter storage usage reporting (per-project deltas, last-change summaries). [1.6.0] Custom preset editor for filters and ignore rules. [1.6.0] Backup health timeline (success rate, last failure reason, trend chart). [1.6.0] Exportable config bundle for easy migration and support. [1.7.0] Project tagging and bulk actions (pause, backup, snapshot by tag). [1.7.0] Per-destination retry policy with backoff and user-facing status summary. [1.7.0] Destination quotas and cleanup suggestions (per-target caps). [1.7.0] Team workflows: shared vaults, access control, audit trails. [1.x.0] Multi-destination health scoring and auto-failover. [1.x.0] Cloud backup targets (S3-compatible, Backblaze, etc.) with encryption options. [1.x.0] Advanced automation hooks (webhooks, scripts on backup/restore events). [1.x.0] CLI parity with UI features. [1.x.0] Per-project verification toggle (always verify, verify on schedule, or manual). [1.x.0] App signing for trusted distribution. [1.x.0] Background integrity audits with alerts.
How to influence the project
- report bugs (logs/screenshots help a lot)
- open feature requests
- discuss real backup workflows
- test new releases and give honest feedback