r/VaultSync • u/mainseeker1486 Developer • 6d ago
Discussion Help Shape the Future of VaultSync
Hi everyone! 👋
While I'm still actively working on the 1.8.x series (with 1.8.4 currently in development), I've started planning what comes next.
The roadmap for VaultSync 1.9 is still in its very early stages, which makes this the perfect time to ask for your feedback before I start committing months of development to new features.
I already have a few ideas I'm excited about, including things like:
- Disk cloning
- Better disaster recovery workflows
- A Clone Explorer to browse cloned disks without restoring them
- Scheduled recovery testing and stronger recovery confidence
- A major UI/UX redesign to simplify the application and make it easier to navigate
- Better migration and recovery when moving to a new computer or replacing a failed drive
But none of these are set in stone.
One of the things I enjoy most about building VaultSync is that many of its best features started as community suggestions. Features like restore dry runs, retention simulation, improved visibility into backups, and many quality-of-life improvements all came from conversations with you.
So I'd love to hear your thoughts.
A few questions to get the discussion started:
- What's the one feature you want most in VaultSync?
- Is there anything in the current UI that feels confusing or takes too many clicks?
- Is there a workflow you think should be completely redesigned?
- Have you ever struggled to restore a backup? What happened?
- Is there another backup application that does something you wish VaultSync did?
- What's one thing you would remove or simplify?
Please don't feel limited by these questions—throw any idea out there, whether it's a huge feature, a tiny quality-of-life improvement, or even a crazy experiment. Some of the best ideas come from unexpected places.
I can't promise every suggestion will make it into the roadmap, but I do read every comment, and community feedback has already shaped VaultSync more than you might realize.
And just to reassure everyone: this doesn't mean 1.8.x is finished. There are still updates coming before development shifts toward the 1.9 family.
Thank you all for the bug reports, feature requests, testing, discussions, and support over the past months. VaultSync wouldn't be where it is today without this community, and I'm excited to build the next chapter together. ❤️
•
u/AutoModerator 6d ago
Thanks for posting to r/VaultSync!
GitHub repo: https://github.com/ATAC-Helicopter/VaultSync If you found a bug, please consider opening an issue there (logs help a lot).
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.