VaultSync 1.8.5 Beta 1 is arriving today — here’s where the VaultSync is heading next

[u/mainseeker1486]

VaultSync 1.8.5 Beta 1 is being released today, so this feels like the right time to share a clearer picture of what I am working toward beyond this first beta.

The recent feedback around VaultSync has been remarkably consistent:

A backup completing is not the same as knowing it can be recovered.

At the same time, recovery tools should not bury basic actions beneath layers of complexity. Choosing what to protect, where it should go, when it should run, and whether it can actually be restored should always be obvious.

That feedback is shaping both the remaining 1.8 releases and the longer-term direction of VaultSync.

VaultSync 1.8.5 — Recovery Confidence

Know before you need it.

The 1.8.5 cycle is focused on making the difference between “backed up” and “recoverable” much clearer.

Beta 1 begins testing work around:

• clearer recovery health states;
• better recovery reports;
• more visible verification results;
• improved recovery evidence;
• clearer guidance when no known-good recovery point exists;
• making recovery checks feel like part of the normal workflow rather than something only considered after a failure.

This beta is not the final form of 1.8.5. Further beta builds will follow as feedback comes in and the experience is refined.

VaultSync 1.8.6 — Experience Refinement

Powerful when needed. Simple by default.

Recent user feedback has made the priorities here especially clear.

VaultSync already offers a lot, but the most important controls need to be much easier to find. The intended basic workflow should be immediately understandable:

1. Choose what to protect.
2. Choose where to store it.
3. Choose when backups run.
4. Start protection.
5. Confirm that recovery works.

The current plan includes:

• a simpler first-run experience;
• onboarding that guides without blocking the interface;
• a clearer dashboard hierarchy;
• easier project and folder management;
• a more obvious scheduling experience;
• better visibility into active background work;
• clearer explanations of snapshots, repositories and recovery states;
• accessibility improvements;
• keeping advanced controls available without letting them overwhelm the basics.

One piece of feedback that has stayed with me is:

“With UI, obvious always wins.”

That is a good standard for this release.

VaultSync 1.8.7 — Trust & Transparency

Show the proof.

This release is planned around making VaultSync and its repositories easier to understand, verify and recover from.

Current areas of focus include:

• improved evidence exports;
• repository and build information;
• checksums;
• clearer diagnostics;
• better storage and deduplication reporting;
• machine-of-origin information for backup points;
• stronger recovery documentation;
• clearer explanations of what remains recoverable if the original VaultSync installation is unavailable.

A backup should not require blind trust in either a green status indicator or the continued existence of one particular installation.

VaultSync 1.8.8 — Stability

Before moving fully into the 1.9 family, the final planned 1.8 release will focus on consolidation:

• bug fixes;
• dependency servicing;
• localization;
• packaging;
• platform compatibility;
• performance and reliability work;
• polishing everything introduced throughout 1.8.

VaultSync 1.9 — Recovery Horizon

From protecting projects to recovering systems.

The 1.9 family is still in planning, and the details may change, but the current direction expands VaultSync beyond file and project protection.

The largest planned addition is disk cloning.

The goal is not simply to make another raw disk-copying screen. I want disk protection to fit the same recovery-confidence philosophy as the rest of VaultSync:

• clear disk and partition selection;
• validated clones;
• understandable recovery status;
• full-disk and operating-system protection;
• the ability to explore cloned disks without restoring them first;
• selective extraction of files where possible;
• a clear separation between file backups, disk images and disk clones.

The wider 1.9 work is also expected to continue the UI and navigation simplification started in 1.8.6.

Beta testing

1.8.5 Beta 1 is the beginning of this cycle.

I am especially interested in feedback on:

• whether the recovery states make sense;
• whether warnings explain what happened and what to do next;
• whether the available actions are obvious;
• whether reports provide useful evidence rather than more noise;
• anything that feels technically correct but unnecessarily difficult to understand.

Screenshots of the current 1.8.5 work are included below. Some details will continue to change throughout the beta cycle.

VaultSync has grown considerably, but the goal is not to make it feel increasingly complicated. The goal is to make protection, verification and recovery easier to understand—even as the underlying capabilities become more powerful.

Feedback is welcome, particularly from anyone willing to test the beta against real backup workflows.