Windows 10, 11 ( 4 MB )
“I built LOTM because I wanted a reference mastering
tool that could stand on its own two feet. Or ears.
Whatever mastering applications tend to stand on.”
Pardon me! This isn’t just another “backup”.
I built it because the world got weird. With AI in the loop, files explode. Dozens of edits in
seconds. Files created, rewritten, deleted like a machine gun. Most backup tools assume slow
changes. Careful edits with occasional regret, not “it’s raining files”.
And they also think backup is for a big disaster. Something where you roll everything back
after a forest fire.
But that’s not how it actually goes. Most of the time it’s not one big disaster. It’s a constant
stream of small ones.
“What did I called this thing yesterday?”
“That version from five minutes ago… that one worked.”
That’s the problem Unbroke is built to solve.
Unbroke is a safety net for your documents, code and files. Especially with AI-assisted chaos.
It snapshots your project automatically, dedups the storage, and lets you browse the past files
like Explorer instead of performing backup archaeology.
- The Cranky Man
(for Windows)
One-time purchase, no subscriptions, free updates. Download the trial version and test it today for free.
Inspired by Git, but not Git. Just like the author ™
Unbroke
Go back.
Unbroken
Browse your files through time
and restore the version before
things went wrong.
Timeline
Browse
Restore
See every change
over time
Explore snapshots
like a file explorer
Unbroke your project
in one click
Local first
Your data stays on
your drive
Fast & light
Minimal overhead
efficient code
Private
Did I say your files
are 100% yours?
Snapshot for the modern times
So what makes Unbroke different, apart from the weird spelling?
Other backup or snapshot tools fall into two extremes. Some
create monolithic backups that force all-or-nothing restores,
while others churn out too many snapshots from frequent save
giving me a headache.
And sure, tools like Git handle version control really well but
require planning and organization. You have to decide before of
time what's worth snapshotting and when.
I needed something in the middle: flexible enough for fully
automated backups, smart enough not to drown me in
unnecessary versions.
And also usable, so I am able to pick a single file from the pile
at any time.
History at your mouse-clicks
Taking snapshots is one thing. Making them usable is another.
“I have a backup blob somewhere, so I can probably restore everything if I mess up.” That’s not as
helpful as it sounds.
I don’t want to roll back half my project just to recover one file and then discover I also undid things
that were perfectly fine.
What I actually need is simple:
Pick a point in time, say, ten minutes ago, when everything worked and see exactly what existed
then. Like a file explorer. Just… earlier. Or like a time ma….
(Wait, that’s registered trademark of Apple Inc, so this is definitely not it. Never. Nobody said that!)
See what actually changed
Unbroke includes a built-in diff, so you don’t have to restore anything
just to see what changed.
Compare a snapshot to your current files, or to the previous snapshot
(if that’s what you want), and see exactly what happened, line by line.
Because most of the time, it’s not everything that broke.
Unbroke borrows some great ideas from Git: snapshots should store content
efficiently using a content-addressed object store. This means repeated
snapshots reference existing file content instead of duplicating it.
(I know, you were about to say the exact same thing to me. Don’t we both
sound so smart?)
Anyway: That makes backups efficient while keeping them 100% independent.
You can delete snapshots or merge them together without affecting each
other. It works, it’s time-tested and it makes sense.
But this is where the similarities end. The usage is almost anti-Git.
What It Borrows From Git
•
Unchanged file contents are stored once
•
Snapshots point to stored objects
•
Repeated backups stay compact
•
File history can be compared across snapshots
Where It Differs
•
No staging (whatever it means)
•
No commits to write
•
No merge conflicts
•
Automatic snapshots run in the background
•
Interface for humans
The result is a timeline backup system with Git-like storage efficiency but an easy user experience built around automatic protection and
easy recovery. (Say that fast three times)
About MediaChance
Products
Links
