Spacedrive 2.0 before beta: an indexed, self-hosted filesystem you can only run as alpha or nightly today
GitHub describes it as Spacedrive is an open source cross-platform file explorer, powered by a virtual distributed filesystem written in Rust.. The repository metadata lists Rust as its primary language. The metadata lists the NOASSERTION license. This article stays within the project description and details documented in the GitHub repository README.
At a glance
- What is it?
- Spacedrive is an Apache-2.0 Rust project that indexes folders, drives, NAS datasets, other nodes and cloud buckets into one private filesystem with previews of every change. Its data model is not committed until the 2.0 beta planned for November 15, 2026, so the current alpha tags and unsigned nightly builds are for people willing to keep backups and rebuild libraries.
- Who is it for?
- Spacedrive suits people who keep data across several drives, a NAS and a cloud bucket and want one searchable index they host themselves, with previews before any copy or cleanup runs. It does not suit anyone who needs a stable library format today: until the 2.0 beta ships, only alpha tags and an unsigned nightly exist, and the project tells you to back up any library you point them at.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Rust, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- spacedriveapp/spacedrive39,523 ★ · +752
| Repository | 2026-08-13 | 2026-11-15 |
|---|---|---|
| spacedriveapp/spacedrive | 38.8k | 39.5k |
752 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Only alpha tags and an unsigned nightly exist before the 2.0 beta
The releases page holds v2.0.0-alpha.1 from 2025-12-26, v2.0.0-alpha.2 from 2026-02-07, and a rolling nightly last cut on 2026-10-08. The project has announced a Spacedrive 2.0 Beta for November 15, 2026, and the beta is the first release that commits to the data model and to preserving your library as it changes. Before that date nothing makes that promise. The nightly ships CLI and daemon builds that are unsigned, move with every push to main, and can break; the project asks you to keep backups of any library you point them at. The repository itself is busy, with the last push on 2026-10-31, so the nightly you download this week may differ from the one a colleague installed last week.
Each source keeps a portable store that outlives the drive
A source in Spacedrive can be a folder, a whole drive, a NAS dataset, another Spacedrive node, a cloud bucket or an external service, and all of them share one record shape and one set of operations. Each source carries a portable store with two kinds of knowledge. The first is a generation that can be refreshed whenever the origin is reachable. The second is durable assertions that cannot be rebuilt from the files alone. That split is why a disconnected drive stays searchable, and why moving a source to another machine can carry its metadata along. Watchers keep names, sizes, timestamps and content state current, so opening a folder does not trigger a rescan. Records survive moves, and BLAKE3 content identities link copies of the same bytes across sources and devices.
Duplicates are removed only after full-byte verification
Duplicate detection works in two stages. Sampled hashes find candidate matches quickly, but a file is treated as a copy only after full-byte verification confirms equality, never on a sampled hash alone. That means reading every byte of each candidate before cleanup, but it removes the failure mode where two different files share a sampled fingerprint and one gets deleted. The index also knows how many copies of a piece of content exist across your whole library, so a cleanup can warn that specific files are the last copy anywhere. Unreadable records are preserved with their error rather than dropped, and drives that are offline, archived, lost or retired stay in the inventory.
Every file operation is validated and previewed by the daemon first
Spacedrive treats copies, merges and deletions as the main everyday risk to your data. Before any operation that changes files runs, it answers two questions. Validation decides whether it may run and how, checking permissions, capacity, safety rules and the exact strategy; that check is enforced by the daemon, not by the dialog. Preview projects the result from the index without touching a file, and serves the same listings as the live filesystem, so you can walk the outcome folder by folder. Because the index answers for offline storage, you can plan a merge onto a drive sitting in a drawer. At dispatch the daemon validates again against the live filesystem and reports any divergence from the plan.
Paired nodes, revocable shares and OS mounts replace a hosted account
There is no hosted account, no vendor control plane and no telemetry. Instead you pair Spacedrive nodes. A live node serves queries, snapshots, byte ranges, jobs and logs for the sources it is authorised to expose, while other nodes may cache projections and content without claiming authority over the source. You can share a source or a subtree with another person, device or agent without merging libraries; the host sets what the recipient can see and do, and the grant stays visible and revocable. Any source can be mounted into macOS, Windows or Linux, with files streamed on demand through one byte plane. The trade-off of skipping a vendor service is that availability depends on your own nodes being reachable.
A source build expects Bun, a pinned Rust toolchain and optional codecs
The JavaScript side refuses other package managers: package.json runs npx only-allow bun on preinstall, pins packageManager to [email protected], and requires Bun 1.3.0 or newer with Node >=18.18 <19 or >=20.1. On the Rust side the workspace declares rust-version 1.95, needed by gpui, while rust-toolchain.toml pins 1.97.1. The justfile setup target runs:
bun install
cargo xtask setupThe setup-native-deps variant swaps the second line for this, which also fetches a prebuilt codec bundle of FFmpeg, libheif and Pdfium:
cargo xtask setup --native-depsThe default development workflow runs the sd-daemon binary in one terminal and the desktop app in another; a headless sd-server binary serves a web UI with no desktop app at all.
cargo build does not produce the desktop app
The Cargo workspace splits members from default-members. A plain cargo build compiles the server, the CLI, core, its benchmarks, the crates and xtask. It leaves out the Tauri desktop app, because Tauri needs the frontend built first, and apps/native, a gpui tree built on Spacedrive's own fork of Zed's gpui. Each has its own entry point:
cd apps/tauri && bun run tauri:devcargo run --release -p sd-nativeThe build-apps target compiles sd-native beside the desktop binary, but a failure only prints a warning, because sd-native can lag behind core. When that happens, Apps > Photos in the desktop menu keeps running whatever previous build exists, if any. A contributor who sees an old Photos app after pulling main should check that warning before filing a bug. The older desktop, cloud and mobile crates are commented out of the workspace, and the mobile app is driven through separate just targets for iOS and Android.
Editorial conclusion
Spacedrive suits people who keep data across several drives, a NAS and a cloud bucket and want one searchable index they host themselves, with previews before any copy or cleanup runs. It does not suit anyone who needs a stable library format today: until the 2.0 beta ships, only alpha tags and an unsigned nightly exist, and the project tells you to back up any library you point them at. Before installing, check the releases page for the beta and confirm whether you need the desktop app or only the CLI and daemon.
Frequently asked questions
What is Spacedrive?
Spacedrive is an open source, cross-platform file explorer built on a virtual distributed filesystem written in Rust. It indexes folders, drives, NAS datasets, other nodes and cloud buckets into one private filesystem with no hosted account or telemetry.
How to install Spacedrive?
Download builds from the Spacedrive GitHub releases page. Nightly CLI and daemon builds are available now but are unsigned and can break, and the 2.0 beta is planned for November 15, 2026.
Is Spacedrive an open source file explorer for Windows?
Yes. Spacedrive is an Apache-2.0 cross-platform file explorer, and it can mount any source or subtree into Windows as well as macOS and Linux.
Official sources
Where developers are discussing it
Posts on Hacker News, dev.to and Lobsters that link to this repository, found by our scan of those communities. 1 in the last 30 days; newest first.
- Spacedrive – Take back your dataHacker News · Oct 25, 2026 · 2 points · 0 comments
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/spacedriveapp-spacedrive)Star history chart for your README
[](https://hysenlabs.com/projects/spacedriveapp-spacedrive)Was this useful?