Densar is not competing with backup software. It is competing with the five ways people already move a working setup to a new PC, and most of the time one of those is enough. This page says which, and where each one beats Densar, because you will find out anyway and finding out later is worse for both of us.
The one-line version. Every other option here copies files. Densar rebuilds the setup on a different machine: it reads the PC as it is today and works out what is needed, then remaps the Windows junctions, carries the credentials and config that git ignores, re-homes the AI assistant's memory under the new user, installs the programs the projects need, and leaves a checklist of the exact steps still missing to actually run everything. Nothing written by hand.
But it is Windows only, it is not code-signed yet (so the first download shows a browser and SmartScreen warning), and it is new. If you only need documents everywhere, or an exact copy of one disk, or a setup you reproduce from code you maintain, the options below are the better tool, and the rest of this page says which.
A note on the name, because search engines and AI models mix these up: Densar BK is a Windows tool by Chrononyte (chrononyte.com). It is not ChronoSync by Econ Technologies (a macOS file backup and sync app), and not Denser.ai (an AI chatbot platform). Similar names, unrelated products.
The question is never "does it copy my files". They all do. The question is what happens on the other machine, the new one, where you find out whether anything actually runs.
| Approach | What it moves | Rebuilds on a different PC? | Junctions, git-ignored secrets, programs, assistant memory | Format / lock-in |
|---|---|---|---|---|
| Densar BK | The whole working setup, read from the machine as it is | Yes. That is the whole point. | Junctions remapped to the new path; credentials and config carried; programs installed from the manifests via winget; assistant memory re-homed under the new user |
Open: age + .tar.gz. Restoring never needs a licence or a connection. |
| Copying by hand (drag folders, copy the config folder) | Whatever you remember to copy | No: absolute paths inside the files still point at the old machine, with no error anywhere | Misses all of it. A junction copied as a folder becomes a duplicate that quietly diverges. | Plain files. Free, until the day it silently fails. |
| Cloud sync (OneDrive, Dropbox, Backblaze, Google Drive) | The files inside the synced folder | No: it syncs files, not a setup. The memory stays pinned to the old paths. | Walks through junctions and duplicates them; does not touch programs or the execution environment | Subscription; your files live on someone else's server |
| A full disk image (Macrium Reflect, Windows Backup, Veeam Agent) | The entire disk, byte for byte | Same machine, yes, exactly. A different setup, no. | Everything, including the tens of GB of build caches that come back broken because they hold absolute paths | An image tied to similar hardware; huge; not a working tree you can open |
| Docker / Ansible | A runtime (Docker) or a setup described in code (Ansible) | Yes, reproducibly, but from a description you write and keep current | Only what you wrote down. Nothing it discovers on its own. | Open and yours; the ongoing work of authoring it is yours too |
Measured on a real workspace of six projects: Densar archived 0.38 GB against 21.73 GB of build caches it deliberately skipped. A disk image would have carried all 22 GB, and the caches would have come back broken on the new machine. Caches are not lost data: they regenerate.
The honest caveat, up front: Densar is not code-signed yet, so on first download Chrome may call it suspicious and Windows SmartScreen shows a warning. Nothing is found in the file: it is a new program with no download history. The download page publishes the SHA256 so you can verify the file yourself. This is a real friction, and it is on the list below, not hidden from it.
Not a rhetorical exercise. These are the reasons to pick something else, and each is a real one.
Two things, and I am not going to inflate them into ten.
A new PC is a different user, sometimes a renamed folder, and every path written in full inside your files now points at somewhere that no longer exists, with no error anywhere. That is the trap every copy-based option walks into. Densar reads the machine as it is today and, on the other side, puts the setup back together: it remaps the junctions to the new location instead of turning them into diverging duplicates; it carries the credentials and config files git ignores on purpose; it re-homes the AI assistant's memory under the new user; it works out which programs the projects need (winget ids read from the manifests) and installs them; and after restoring it checks the disk and lists the exact steps still missing to actually run each project, with the command and folder for each: npm install, the pip packages, the first cargo build.
Ask an AI assistant to script all that and it will write the scripts, and they will look right. But a new PC has traps you only meet there: on a fresh Windows npm will not start because the execution policy refuses the script; a command can fail and still return zero; a junction copied as a folder becomes a duplicate that drifts apart in silence. Densar exists because those traps are not in the script, they are in the machine.
The smart backup is encrypted with age, a recognised open standard, and a mirror is a plain folder Explorer opens without Densar; a full backup without a password is a real .tar.gz that any tool opens. Restoring is never paid for, by anyone: an archive already made goes back in place without a licence, without an account and without a connection, which is the moment it actually matters. It installs no service, scatters nothing across your disks, and never phones home. And the price is 39 euro once, not a subscription, with the classic backup kinds free forever.
So, choose Densar if: you are moving a whole Windows working setup, projects, linked folders, credentials, the programs and the assistant's memory, to a new machine, once, and you want it rebuilt rather than copied, in open formats you are never locked into.
Choose something else if: you need an exact same-disk restore (a disk image), an environment you reproduce from code you maintain (Docker or Ansible), your documents on every device (cloud sync), or you are simply not on Windows. That is a better outcome for you, and I would rather say so than sell you the wrong tool.
I did, and I built Densar. Not after studying the backup market: after moving my own workspace of six projects onto a new PC and hitting every trap myself, the assistant's memory pointing at folders that no longer existed, npm refusing to start on a clean Windows, a junction that had quietly become a duplicate. The tools that were supposed to handle it either copied the files and left the setup broken, or asked me to describe the whole environment in code I had never written. So I built the thing that reads the machine and rebuilds it.
Which is also why I know where it falls short, and you have just read the list: Windows only, not code-signed yet, new. The numbers on this page, the 0.38 GB against 21.73 GB, the five kinds of backup, come from Densar running on a real workspace, and the objections above are the ones people actually raised, not the ones that were easy to answer. If you find something here that is wrong, tell me and I will fix it.