Keeps a folder on your computer in sync with your Homebase cloud, on Windows, macOS and Linux. Like Dropbox, but the files live on your own Homebase.
- Install it from the latest release:
- Windows 10/11:
homebase-filesync.exe. It installs the package for your PC and keeps it up to date. - macOS 11+:
Homebase-Filesync-mac-aarch64.dmg(Apple Silicon) or…-mac-amd64.dmg(Intel); drag the app to Applications. It updates itself. - Ubuntu, Debian:
sudo apt install ./homebase-filesync_amd64.deb(or_arm64). Updates come withapt upgrade(the package adds its repository). - Fedora, openSUSE:
sudo dnf install ./homebase-filesync-*.x86_64.rpm(or.aarch64;sudo zypper installon openSUSE). Updates by hand, for now. - Other Linux, servers:
homebase-filesync-*-linux-amd64.tar.gz(or-aarch64), static programs. Updates by hand.
- Windows 10/11:
- Start Homebase Drive. Installing doesn't start it, and it has no window, only an icon:
- Windows: open Homebase Drive from the Start menu. Its icon is in the notification area at the right of the taskbar (behind the ^ arrow at first).
- macOS: open Homebase Filesync from Applications (the Mac app keeps that name). Its icon is in the menu bar.
- Linux: open Homebase Drive from the app menu (Activities on Ubuntu), or run
setsid homebase-filesyncin a terminal (from the tarball:setsid homebase-filesync-*/bin/homebase-filesync). Its icon is in the top bar or panel; GNOME needs the AppIndicator extension, which Ubuntu has.
- Choose Log in to Homebase… from that icon. Your browser opens so you can approve this
computer, and the folder
~/Homebasestarts syncing (or pick another). From then on it starts by itself when you log in.
From a terminal instead of steps 2 and 3: hbsync setup <your identity>.
After an update on Linux, the menu offers Restart to finish the update.
Your Homebase needs odin-core v0.1.962 or newer.
The tray icon shows how things stand by the colour of its dot: green up to date, cyan
syncing, grey paused, offline or not set up, magenta when something needs you. Its menu opens
the folder or your files online, lists what synced lately and any problems, reviews held
deletions, opens Recently deleted and Set up this computer (Documents, Pictures and the like, and your Desktop), and
pauses, resumes or syncs now. Quit asks whether to keep syncing in the background or stop
syncing too; stopped, syncing on this computer waits until you choose Start syncing in the
menu (or run hbsync start), also after you log in again. Your other computers keep syncing.
From a terminal, hbsync does the same:
hbsync status |
what it's doing now |
hbsync recent |
what synced lately |
hbsync sync, pause [--for 1h], resume |
sync now, pause (for a while), resume |
hbsync confirm-deletes, put-back |
let held deletions through, or put the files back |
hbsync deleted |
what's in Recently deleted |
hbsync restore <path> |
bring an item back from Recently deleted, on every computer |
hbsync empty-deleted [<path>] |
delete Recently deleted (or one item) for good |
hbsync add documents (pictures, …, desktop), remove … |
sync one of your own folders too, or stop (your Desktop gets a folder of its own, shown on your other computers) |
hbsync start, stop |
start or stop syncing (the daemon) |
hbsync log |
where the logs are |
hbsync --help and hbsync <command> --help say more. Every command and option:
docs/spec/daemon.md.
Good to know:
- Deleting many files at once waits for you. If you delete more than 50 files and more
than a quarter of the folder at once, or every file, the deletions are held until you confirm
them (the tray's Review deletions… or
hbsync confirm-deletes) or put the files back. A delete from another computer that would empty the whole folder here waits the same way. - Where deleted files go. What you delete waits in Recently deleted on your Homebase for 30
days, wherever you deleted it. On your computer, a file manager also puts it in the OS's
trash;
rmdoesn't. Your other computers delete their copy. - Emptying Recently deleted runs in the background, and on a big one it can take a while
(about 18 minutes for 22,000 items on one Homebase). It shrinks as it goes, and
hbsync statusand the tray's menu show how far it got.hbsync stopand quitting with Stop syncing too stop it after the batch in hand (250 files), waiting 15 s at most: the rest stays in Recently deleted for the next time. - Commands that ask (
empty-deleted,confirm-deletes,put-back) need--yeswhere nobody can answer, such as in a script. - Leave things out on one computer with gitignore-style rules in
.hbsync/ignorein the folder.
-
Written in Rust, from top to bottom. Three small native programs (about 10 MB each, with no runtime, no Electron and no Java): a tray app, a per-user daemon (
hbsyncd) that does the syncing, and a command line (hbsync). The Linux programs are fully static. -
Barely there. When idle, it waits on the OS's file events and on your Homebase's notification socket instead of polling, and writes nothing to disk.
Side by side on one six-year-old Linux desktop (Intel i7-8700K, October 2026), Homebase Drive 0.9 and Dropbox 274 each syncing the same folder: 127,000 files, 309 GB.
Homebase Drive Dropbox Encrypted before it leaves your computer Yes No Idle, overnight (8.4 hours) CPU 5 s 142 s Memory 31 MB 261 MB Threads 27 88 Written to disk 0 MB 34 MB Restart, nothing changed CPU 2 s 12 s Memory afterwards 33 MB 466 MB Written to disk 0 MB 21 MB Adding a folder of 5,204 files (4.8 GB) CPU 62 s 160 s Memory at its peak 50 MB 696 MB Written to disk 266 MB 698 MB Sent over the network 5.1 GB 5.4 GB Deleting that folder CPU 0.8 s 11.1 s Written to disk 11 MB 39 MB Idle, that's 27 times less CPU and 8 times less memory; while syncing, 14 times less memory and less than half the CPU and disk writes. A laptop's battery barely notices it.
On a Windows laptop (AMD Ryzen 9 6900HX, Windows 10, October 2026), Homebase Drive 0.9.1 and Dropbox 276 each syncing the same 127,000 files (288 GB). Memory is Task Manager's (the private working set); Dropbox there is eight processes and a service.
Homebase Drive Dropbox Idle (4.4 hours) CPU 7 s 68 s Memory 16 MB 617 MB Threads 23 299 Written to disk 0.2 MB 10 MB Restart, nothing changed Quiet after 3 s 117 s CPU 2.5 s 48 s Memory afterwards 16 MB 622 MB -
Every file is hashed in full with BLAKE3, one of the fastest cryptographic hashes there is, while the file is read. The hash goes along with each file and is checked on the way back: a file that doesn't match is refused and downloaded again. The hash also tells real edits from touched timestamps, so unchanged files are never uploaded twice.
-
Zero-knowledge encrypted at rest. Each file gets its own random AES key before it leaves your computer, and names, sizes and times are encrypted too. What lies on your Homebase's disk and in its backups is ciphertext. The server doesn't hold the key: only you and the devices you approved do. It unlocks a file's key for a moment, in memory, only while serving a request from one of them. It uses Homebase's own format, so your other Homebase apps can open the files. The cipher handles about 1 GB/s encrypting and 2.8 GB/s decrypting, more than any internet link. Dropbox, by default, encrypts files once they reach its servers, with keys Dropbox holds. With Homebase Drive, the files are encrypted before they leave your computer, and the keys stay with your own Homebase, not with a company. More: docs/spec/encryption.md.
Privacy, from each vendor's own terms (October 2026):
Homebase Drive Dropbox Google Drive OneDrive Encrypted before it leaves your computer ✅ Yes ❌ No1 ❌ No1 ❌ No Vendor holds the key to your files ✅ No2 ❌ Yes ❌ Yes ❌ Yes Vendor's terms say it scans your content ✅ No ❌ Yes3 ❌ Yes4 ❌ Yes5 Vendor's terms let it modify your content ✅ No ✅ No ❌ Yes4 ✅ No6 Vendor's terms let it remove your content ✅ No ❌ Yes3 ❌ Yes4 ❌ Yes5 Vendor's terms let it remove content it judges misleading ✅ No ✅ No7 ❌ Yes8 ⚠️ If intentionally deceptive9 -
Fast, even on a six-year-old desktop (Intel i7-8700K). With a test server on the same machine, it uploads 1 GiB at about 220 MB/s and downloads it at about 600 MB/s. An edit shows up on your other computer in about half a second. Big files are streamed in both directions in constant memory, and a broken transfer picks up where it stopped.
-
Careful with your data. Losing nothing is the first rule:
- When two computers edit the same file, both versions are kept as a conflict copy.
- A sync that would delete many files at once waits for you to confirm.
- Whatever you delete, on any of your computers, waits in Recently deleted on your
Homebase for 30 days. Restore it from the tray menu or with
hbsync restore, and it comes back on every computer, a folder with everything that was in it. - Files are swapped into place atomically, never half-written.
- The sync logic is a pure function, tested with property tests over hundreds of thousands of random multi-computer histories.
-
Made for each OS. It uses the NTFS change journal on Windows, FSEvents on macOS and inotify on Linux. It handles names each OS treats differently: case, Unicode forms, and characters Windows doesn't allow. Your folder gets its own icon and a place in the sidebar, on Windows at the top of Explorer's, beside OneDrive and Dropbox. Finder tags and their colours sync between Macs and with KDE on Linux. A Windows PC can't show them, but keeps them intact. Creation dates are kept too, even when an editor saves by replacing the file.
-
Yours to tune.
.hbsync/ignoretakes gitignore-style rules per computer, and well-known junk (.DS_Store,Thumbs.db, editor temp files) is left out on its own.hbsyncgives you status, recent changes, pause and resume, Recently deleted, and the logs from a terminal.
Developer notes are in CLAUDE.md and docs/. Start with docs/foundations.md and docs/roadmap.md. Releases: RELEASING.md.
cargo test --workspace
cargo run -p hbsync-trayInstallers and updates are made with Conveyor by Hydraulic, free for open-source projects.
The Homebase.id License: the GNU Affero General Public License v3 (LICENSE-GPL), the same as the other Homebase apps.
Footnotes
-
Only on business tiers: Dropbox's encrypted team folders (Business Plus and up, help) and Google's client-side encryption (Workspace Enterprise Plus and Education, help). ↩ ↩2
-
Your Homebase unlocks a file's key in memory only while serving a request from one of your devices; at rest, the server and its backups hold ciphertext only (docs/spec/encryption.md). ↩
-
Dropbox Terms: "Dropbox accesses, stores, and scans Your Stuff"; "We reserve the right to delete or disable content alleged to be infringing". ↩ ↩2
-
Google Terms: "automated systems and algorithms to analyze your content"; the license lets Google "modify your content, such as reformatting or translating it"; "we reserve the right to take down some or all of that content". ↩ ↩2 ↩3
-
Microsoft Services Agreement: "automated systems and humans to review content"; "we reserve the right to delete or disable access to Your Content". ↩ ↩2
-
Except content on Xbox services, which the agreement lets Microsoft modify. ↩
-
Dropbox Acceptable Use Policy: misleading content only where it breaks the law. ↩
-
Google Drive program policies, "Misleading Content": "Do not distribute content that deceives, misleads, or confuses users", covering civic processes, harmful conspiracy theories, harmful health practices and manipulated media; Google may restrict access to such content or remove it. (Restrict or remove: the policies don't say Google edits it.) ↩
-
Microsoft's Code of Conduct forbids "generating or sharing content that is intentionally deceptive"; content that breaks it may be blocked or removed. ↩