Product
An instrument for the history of your work.
AFTRIMGE is a desktop application for people whose work lives in files: design, illustration, photography, writing, anything saved over and over. It records that work as it happens, on your machine, and gives you a precise way back.
Recording
You choose a folder. AFTRIMGE watches it through the operating system, waits for each file to stop changing, and records the settled result as a version. It reconciles the folder when it opens, so changes made while it was closed are recorded too. Application scratch, lock and tooling files are ignored.
A file is an identity, not a path. When it is renamed or moved, its history follows it. When a move is recognised only because the content is identical, AFTRIMGE says it inferred the move rather than claiming to have seen it.
Storing
Each distinct piece of content is stored once, under the SHA-256 digest of its bytes, in an object store beside a SQLite index of projects, files, versions and events. Identical content shared by many versions costs the space of one.
Files larger than 256 MiB have their versions recorded without their bytes being kept. Everything lives in one folder on your disk that you can see, copy and back up.
Returning
Drag a playhead through recorded time and the project rebuilds as it was: files that did not exist yet disappear, names revert, images show their pixels from then. Replay watches the project build itself.
Any kept version can be exported, or restored as a copy, in place, or by deliberately forcing it over a file that changed since it was recorded. Every restore is verified and recorded as new history.
Keeping and letting go
Retention releases the stored bytes of old versions while keeping their record. Collection removes bytes nothing holds, and can be previewed. The storage ledger shows every piece of content, why it is still here, and what withdrawing a reason would expose.
Preservation lets you record that specific content must survive, independent of any other rule.
Trusting
Stored objects can be verified one at a time or the whole archive in one pass, by reading and hashing them, with results that keep missing, corrupt, unreadable and unchecked content distinct. A damaged object can be repaired only from a source verified to match.
Any relationship or preservation can be asked to explain itself: which records, which measurements, and whether it could still be reproduced today.
Investigating
For images AFTRIMGE never watched, image archaeology reads structure and metadata, measures pixels, and searches folders you nominate and your recorded history for likely sources: resized, cropped, recompressed, regraded or placed inside another image.
Every finding is a graded measurement. Only identical bytes make a finding a fact. There is no machine learning model in AFTRIMGE.
What it is not
- It is not a backup service. The archive lives on the same computer as your work. Copy it elsewhere if you need protection from losing the disk.
- It is not version control. There are no commits or branches; history is what happened.
- It is not connected to anything. There is no sync, no sharing and no cloud component.
- It does not yet offer, in its interface, restoring a whole project to a moment or preserving content outside a continuity route. The engine supports both.
- It does not update itself. A newer version is downloaded and installed by you.