Spacedrive catalogs files without moving them
Spacedrive sits above Finder, Explorer, and ordinary Linux file managers. A file can remain on a laptop, NAS, external disk, or cloud volume while its metadata appears in one library. Offline devices stay in the catalog with their contents marked unavailable. Script adapters can also bring Gmail, Apple Notes, browser history, Obsidian, Slack, calendars, contacts, and GitHub into the same search surface. This is useful when the problem is remembering where data lives, rather than copying all of it into one new folder tree.
The scope is much larger than a desktop shell. Our 45.4 MB checkout contained 2,917 files and about 323,090 source lines. A Rust core handles SQLite data, BLAKE3 identities, jobs, search, encryption, and peer communication over Iroh and QUIC. Tauri supplies the desktop app, React Native covers mobile, and the monorepo also contains a web client, CLI, and headless server. Six CI workflow files were present, while our scan found no Dockerfile and no directory named tests.
What happened when we ran it
Our run at commit 6dfeccf used an unprivileged Debian container with 3 CPUs, 8 GB of RAM, Node 22, and no secrets. Installation failed with exit 1 after 76 seconds. The final log shows bun x only-allow bun, six dependencies being resolved, and a lockfile being saved. The preinstall script then printed a direct instruction to use bun install for this project. That is the measured outcome; the log does not show a Rust compiler error or a missing native library.
The failed install prevented any recorded build or test result. Spacedrive's README points contributors to just setup, which requires Rust 1.81 or newer, Bun 1.3 or newer, just, and Python 3.9 or newer. A separate open issue reports that this route still fails on a fresh Ubuntu machine because native packages are omitted and the first cargo xtask setup call cannot see an alias that the setup process creates. That issue is separate from our 76-second package-manager failure.
Content identity is the reason to accept the complexity
Paths are poor identities for files spread across several machines. Drive letters change, folders move, and identical bytes can sit under unrelated names. Spacedrive assigns BLAKE3 content identities and uses a universal SdPath across devices. That model supports redundancy checks and deduplication without assuming that every file is mounted or online. Cloud volumes for S3, Google Drive, Dropbox, OneDrive, Azure, and Google Cloud Storage appear beside local locations instead of becoming a separate browsing mode.
File operations are represented as actions that can be previewed and approved, then continued as durable jobs after an interruption. Metadata uses leaderless synchronization, while file bytes remain on their source devices until requested. The same 323,090-line codebase can pair with the separate Spacebot runtime and apply permissions by device, path, and operation. Optional screening can quarantine imported records before an agent searches them. The design is thoughtful, though each added surface creates another place where an alpha defect can affect real data.
The v2 alpha requires copied data and independent backups
Open issue 3056 reports that v2.0.0-alpha.2 deleted a nonempty folder named tmp at the root of a tracked Windows volume when Spacedrive started. The reporter says the behavior reproduced on multiple volumes and did not appear in daemon logs. We did not reproduce or test that claim in our sandbox. A file manager has a low tolerance for this class of report, so the sensible trial uses copied files on a disposable volume while the original remains outside Spacedrive's reach.
The alpha.2 release published on February 7, 2026 says many features do not work, calls macOS the most stable platform, and says FFmpeg is not bundled with Windows, Linux, or server builds. Its notes warn that thumbnails will not work on those targets. Another open report describes both macOS instances crashing during pairing and then appearing offline. GitHub listed 54 open issues and pull requests when fetched, so the queue is modest for a project this broad, but the unresolved items touch core daily behavior.
The current license restricts hosted competition for two years
Spacedrive uses FSL-1.1-ALv2 rather than an OSI-approved open-source license. It permits internal use, modification, redistribution, education, and research, while barring competing products and several managed service categories. Each released version converts to Apache 2.0 on its second anniversary. An August 2026 maintainer issue documents consent for surviving contributions made before the change from AGPL; seven of nine named contributors were checked off when we read it. A company planning redistribution or a hosted product should review the exact version and provenance record.
Development has resumed since the funding pause announced with stable release 0.4.3 in March 2025. The v2.0.0-alpha.2 prerelease arrived in February 2026, the measured commit was pushed on July 29, and issue discussion continued in August. The repository had 38,857 stars when fetched. Those are signs of attention, not proof that the alpha is safe for irreplaceable files. Spacedrive earns a trial when one searchable layer across devices and clouds is the requirement; TagSpaces, Nextcloud, or Syncthing is easier to justify for a narrower job.