u/LeonardoCiaccio

Quick release update on Vorn — local-first desktop backup where identical content is stored exactly once across every session, and each archive is self-describing (the index can be rebuilt by scanning the store, your data is never trapped). AGPL-3.0.

New in 1.0.3:

• Chunked storage for large files — files ≥ 10 MB get split into 4 MB pieces. Change one byte in a 5 GB video and only the affected chunks rewrite. Dedup happens at chunk level across every session and across compression variants.
• Proper Windows long-path support — \\?\ extended-length paths now work everywhere (OneDrive Enterprise, deep nesting, 75-char hash filenames). Took me two debug sessions to figure out that Electron's existsSync/accessSync silently fail on \\?\ while statSync works fine — fun afternoon.
• USB-root stores fixed — opening a store directly at D:\ was broken; now it just works.
• Sub-second cancellation everywhere — backup, scan, prune, restore all stop within a second even on huge sources or slow USB writes.
• Closed a class of silent-overwrite bugs that could replace historical session records on deep storeDir paths.

No accounts, no cloud, no telemetry. Pre-built binaries for Windows / macOS / Linux on the releases page.

If you have weird storage setups — NAS, network shares, deep paths, USBs that get yanked mid-write — I'd really like to hear how Vorn behaves on yours. The most useful feedback is the failure mode I haven't thought of yet.

→ https://github.com/LeonardoCiaccio/Vorn

A fast, ultra-secure, cross-platform desktop backup tool with content-addressable storage and automatic deduplication.

100% Free and Open-Source!
https://github.com/LeonardoCiaccio/Vorn

Hey r/software,

First post here, so I'll keep it short and get straight to the point: I'd love an honest critique of a project I've been building.

Vorn (Vault Of Redundant Nodes) is a cross-platform desktop backup app I wrote in Electron + Vue 3. The core idea is simple: instead of copying files blindly, every file is identified by its BLAKE3 hash and stored only once — even across multiple sessions and backup runs. Identical content takes zero extra space, no matter how many times you back it up.

A few things I'm proud of:

• Self-describing format: each .vorn container embeds its own metadata (hash, size, paths). If you lose Vorn's index database, you can still reconstruct everything by scanning the store. Your data is never trapped.
• Atomic writes + WAL: crashes don't corrupt your backup.
• Fully offline: no accounts, no telemetry, no cloud. Your data stays local.
• Resume interrupted runs: pick up exactly where you left off.
• Build it yourself from source — takes about 5 minutes on Windows, macOS, or Linux.

It's at v0.7.4, AGPL-3.0, source-only for now.

GitHub: https://github.com/LeonardoCiaccio/Vorn

What I'm genuinely looking for:

• Is the concept interesting or already well-covered by existing tools?
• Does the self-describing format idea make sense or is it overengineered?
• Anything that immediately reads as "this is the wrong approach"?

I can take harsh feedback — I'd rather hear it now than ship something flawed. Thanks.