VaultSync Development diary

VaultSync 1.8 Roadmap— help shape the next release

VaultSync 1.7 (Sentinel) has been out for a few days now. There will most likely still be a few 1.7.x follow-up releases (fixes, small improvements, polish), but I’ve started planning ahead for 1.8. Before locking in the roadmap, I want to build this one with…

VaultSync 1.7 (Sentinel) has been out for a few days now.

There will most likely still be a few 1.7.x follow-up releases (fixes, small improvements, polish), but I’ve started planning ahead for 1.8.

Before locking in the roadmap, I want to build this one with the community.

If you’re using VaultSync (or just following the project), I’d really like your input:

What should VaultSync do better?

Anything is fair game:

  • Missing features
  • Pain points in your workflow
  • Things that feel clunky or unclear
  • Features from other tools you wish VaultSync had

Areas I’m currently exploring

Just to give some direction:

  • Transfer system improvements (resume support, smarter retries, better bandwidth handling)
  • UI / UX improvements (clearer states, less friction, better visibility into what’s happening)
  • Backup intelligence (smarter retention, insights, anomaly detection)
  • Automation & scheduling (more control, better reliability, edge cases)
  • Restore experience (making restores safer, clearer, and faster)
  • Performance (large vaults, NAS setups, cross-machine scenarios)

[link] [comments]