Spacedrive

A file manager built on a virtual distributed filesystem
spacedrive.com · v2 Documentation · Discord

Spacedrive is an open source cross-platform file manager, powered by a virtual distributed filesystem (VDFS) written in Rust.

Organize files across multiple devices, clouds, and platforms from a single interface. Tag once, access everywhere. Never lose track of where your files are.

[!IMPORTANT] v2.0.0-alpha.1 Released: December 26, 2025

This is Spacedrive v2—a complete ground-up rewrite. After development of the original alpha version stopped in January this year, I rebuilt Spacedrive from scratch with the hard lessons learned.

Current status: Alpha release for macOS and Linux. Windows support coming in alpha.2. Mobile apps (iOS/Android) coming soon.

Download Release · Visit v2.spacedrive.com for complete documentation and guides.

If you’re looking for the previous version, see the v1 branch.

The Problem

Computing was designed for a single-device world. The file managers we use today—Finder, Explorer, Files—were built when your data lived in one place: the computer in front of you.

The shift to multi-device computing forced us into cloud ecosystems. Want your files everywhere? Upload them to someone else’s servers. The convenience came at a cost: data ownership. This wasn’t accidental—centralization was the path of least resistance for solving multi-device sync.

Now AI is accelerating this trend. Cloud services offer intelligent file analysis and semantic search, but only if you upload your data to their infrastructure. As we generate more data and AI becomes more capable, we’re giving away more and more to access basic computing conveniences.

The current system isn’t built for a world where:

• You own multiple devices with underutilized compute and storage
• Local AI models are becoming competitive with cloud alternatives
• Privacy and data sovereignty matter
• You shouldn’t have to choose between convenience and control

The Vision

Spacedrive is infrastructure for the next era of computing. It’s an architecture designed for multi-device environments from the ground up—not cloud services retrofitted with offline support, but local-first sync that scales to the cloud when you want it.

As local AI models improve, Spacedrive becomes the fabric that enables the same insights cloud services offer today, but running on hardware you already own, on data that never leaves your control. This is a long-term project correcting computing’s trajectory toward centralization.

The file explorer interface is deliberate. Everyone understands it. It’s seen the least innovation in decades. And it has the most potential when you bake distributed computing, content awareness, and local AI into something universally familiar.

How It Works

Spacedrive treats files as first-class objects with content identity, not paths. A photo on your laptop and the same photo on your NAS are recognized as one piece of content. This enables:

• Content-aware deduplication - Track redundancy across all devices
• Semantic search - Find files in under 100ms across millions of entries
• Transactional operations - Preview conflicts, space savings, and outcomes before execution
• Peer-to-peer sync - No servers, no consensus protocols, no single point of failure
• Offline-first - Full functionality without internet, syncs when devices reconnect

Files stay where they are. Spacedrive just makes them universally addressable with rich metadata and cross-device intelligence.

---

Architecture

Spacedrive is built on four core principles:

1. Virtual Distributed Filesystem (VDFS)

Files and folders become first-class objects with rich metadata, independent of their physical location. Every file gets a universal address (SdPath) that works across devices. Content-aware addressing means you can reference files by what they contain, not just where they live.

2. Content Identity System

Adaptive hashing (BLAKE3 with strategic sampling for large files) creates a unique fingerprint for every piece of content. This enables:

• Deduplication: Recognize identical files across devices
• Redundancy tracking: Know where your backups are
• Content-based operations: “Copy this file from wherever it’s available”

3. Transactional Actions

Every file operation can be previewed before execution. See exactly what will happen—space savings, conflicts, estimated time—then approve or cancel. Operations become durable jobs that survive network interruptions and device restarts.

4. Leaderless Sync

Peer-to-peer synchronization without central coordinators. Device-specific data (your filesystem index) uses state replication. Shared metadata (tags, ratings) uses a lightweight HLC-ordered log with deterministic conflict resolution. No leader election, no single point of failure.

---

Core Features

Feature	Description
Cross-Platform	macOS, Windows, Linux, iOS, Android
Multi-Device Index	Unified view of files across all your devices
Content Addressing	Find optimal file copies automatically (local-first, then LAN, then cloud)
Smart Deduplication	Identify identical files regardless of name or location
Cloud Integration	Index S3, Google Drive, Dropbox as first-class volumes
P2P Networking	Direct device connections with automatic NAT traversal (Iroh + QUIC)
Semantic Tags	Graph-based tagging with hierarchies, aliases, and contextual disambiguation
Action Preview	Simulate any operation before execution
Offline-First	Full functionality without internet, syncs when devices reconnect
Local Backup	P2P backup between your own devices (iOS photo backup available now)
Extension System	WASM-based plugins for domain-specific functionality

---

Tech Stack

Core

• Rust - Entire VDFS implementation (~183k lines)
• Tokio - Async runtime
• SQLite + SeaORM - Local-first database with type-safe ORM queries
• Iroh - P2P networking with QUIC transport, hole-punching, and local discovery
• BLAKE3 - Fast cryptographic hashing for content identity
• Wasmer - Sandboxed WASM extension runtime
• Axum - HTTP/GraphQL server for web and API access
• OpenDAL - Unified cloud storage abstraction (S3, Google Drive, OneDrive, Dropbox, Azure Blob, GCS)
• Specta - Auto-generated TypeScript and Swift types from Rust

Cryptography & Security

• Ed25519 / X25519 - Signatures and key exchange
• ChaCha20-Poly1305 / AES-GCM - Authenticated encryption
• Argon2 - Password hashing
• BIP39 - Mnemonic phrase support for key backup
• redb - Encrypted key-value store for credentials

Media Processing

• FFmpeg (via custom sd-ffmpeg crate) - Video thumbnails, audio extraction
• libheif - HEIF/HEIC image support
• Pdfium - PDF rendering
• Whisper - On-device speech recognition (Metal-accelerated on Apple platforms)
• Blurhash - Compact image placeholders

Interface (shared across web and desktop)

• React 19 - UI framework
• Vite - Build tooling
• TypeScript - Type-safe frontend code
• TanStack Query - Server state management
• Zustand - Client state management
• Radix UI - Accessible headless components
• Tailwind CSS - Utility-first styling
• Framer Motion - Animations
• React Hook Form + Zod - Form management and validation
• Three.js / React Three Fiber - 3D visualization
• dnd-kit - Drag and drop
• TanStack Virtual / TanStack Table - Virtualized lists and tables

Desktop

• Tauri 2 - Cross-platform desktop shell (macOS, Linux, Windows)

Mobile (React Native)

• React Native 0.81 + Expo - Cross-platform mobile framework
• Expo Router - File-based routing
• NativeWind - Tailwind CSS for React Native
• React Navigation - Native navigation stack
• Reanimated - Native-thread animations
• sd-mobile-core - Rust core bridge via FFI

Architecture Patterns

• Event-driven design with centralized EventBus
• CQRS: Actions (mutations) and Queries (reads) with preview-commit-verify
• Durable jobs with MessagePack serialization and checkpointing
• Domain-separated sync with clear data ownership boundaries
• Compile-time operation registration via inventory crate

---

Project Structure

spacedrive/
├── core/                  # Rust VDFS implementation
│   ├── src/
│   │   ├── domain/        # Core models (Entry, Library, Device, Tag, Volume)
│   │   ├── ops/           # CQRS operations (actions & queries)
│   │   ├── infra/         # Infrastructure (DB, events, jobs, sync)
│   │   ├── service/       # High-level services (network, file sharing, sync)
│   │   ├── crypto/        # Key management and encryption
│   │   ├── device/        # Device identity and configuration
│   │   ├── filetype/      # File type detection and registry
│   │   ├── location/      # Location management and indexing
│   │   ├── library/       # Library lifecycle and operations
│   │   └── volume/        # Volume detection and fingerprinting
│   └── tests/             # Integration tests (pairing, sync, file transfer)
├── apps/
│   ├── cli/               # CLI and daemon entry point
│   ├── server/            # Headless server for Docker/self-hosting
│   ├── tauri/             # Desktop app shell (macOS, Windows, Linux)
│   ├── web/               # Web app (Vite, connects to daemon via WebSocket)
│   ├── mobile/            # React Native mobile app (Expo)
│   ├── api/               # Cloud API server (Bun + Elysia)
│   ├── landing/           # Marketing site and docs (Next.js)
│   ├── ios/               # Native iOS prototype (Swift)
│   ├── macos/             # Native macOS prototype (Swift)
│   └── gpui-photo-grid/   # GPUI media viewer prototype
├── packages/
│   ├── interface/         # Shared React UI (used by web and desktop)
│   ├── ts-client/         # Auto-generated TypeScript client and hooks
│   ├── swift-client/      # Auto-generated Swift client
│   ├── ui/                # Shared component library
│   └── assets/            # Icons and images
├── crates/
│   ├── crypto/            # Cryptographic primitives
│   ├── ffmpeg/            # FFmpeg bindings for video/audio
│   ├── images/            # Image processing (HEIF, PDF, SVG)
│   ├── media-metadata/    # EXIF/media metadata extraction
│   ├── fs-watcher/        # Cross-platform file system watcher
│   ├── sdk/               # WASM extension SDK
│   ├── sdk-macros/        # Extension procedural macros
│   ├── task-system/       # Durable job execution engine
│   ├── sd-client/         # Rust client library
│   └── ...                # actors, fda, log-analyzer, utils
├── extensions/            # WASM extensions (photos, test-extension)
└── docs/                  # Architecture documentation

---

Extensions

Spacedrive’s WASM-based extension system enables specialized functionality while maintaining security and portability.

[!NOTE] The extension system is under active development. A stable SDK API will be available in a future release.

Professional Extensions

Extension	Purpose	Key Features	Status
Photos	AI-powered photo management	Face recognition, place identification, moments, scene classification	In Progress
Chronicle	Research & knowledge management	Document analysis, knowledge graphs, AI summaries	In Progress
Atlas	Dynamic CRM & team knowledge	Runtime schemas, contact tracking, deal pipelines	In Progress
Studio	Digital asset management	Scene detection, transcription, proxy generation	Planned
Ledger	Financial intelligence	Receipt OCR, expense tracking, tax preparation	Planned
Guardian	Backup & redundancy monitoring	Content identity tracking, zero-redundancy alerts, smart backup suggestions	Planned
Cipher	Security & encryption	Password manager, file encryption, breach alerts	Planned

Open Source Archive Extensions

Extension	Purpose	Provides Data For	Status
Email Archive	Gmail/Outlook backup	Atlas, Ledger, Chronicle	Planned
Chrome History	Browsing history backup	Chronicle	Planned
Spotify Archive	Listening history	Analytics	Planned
GPS Tracker	Location timeline	Photos, Analytics	Planned
Tweet Archive	Twitter backup	Chronicle, Analytics	Planned
GitHub Tracker	Repository tracking	Chronicle	Planned

---

Getting Started

Prerequisites

• Rust 1.81+ (rustup)
• Bun 1.3+ (bun.sh) - For Tauri desktop app

Quick Start with Desktop App (Tauri)

Spacedrive runs as a daemon (sd-daemon) that manages your libraries and P2P connections. The Tauri desktop app can launch its own daemon instance, or connect to a daemon started by the CLI.

# Clone the repository
git clone https://github.com/spacedriveapp/spacedrive
cd spacedrive

# Install dependencies
bun install
cargo run -p xtask -- setup  # generates .cargo/config.toml with aliases
cargo build # builds all core and apps (including the daemon and cli)

# Copy dependencies into the debug Folder ( probably windows only )
Copy-Item -Path "apps\.deps\lib\*.dll" -Destination "target\debug" -ErrorAction SilentlyContinue
Copy-Item -Path "apps\.deps\bin\*.dll" -Destination "target\debug" -ErrorAction SilentlyContinue

# Run the desktop app (automatically starts daemon)
cd apps/tauri
bun run tauri:dev

Quick Start with CLI

The CLI can manage libraries and run a persistent daemon that other apps connect to:

# Build and run the CLI
cargo run -p sd-cli -- --help

# Start the daemon (runs in background)
cargo run -p sd-cli -- daemon start

# Create a library
cargo run -p sd-cli -- library create "My Library"

# Add a location to index
cargo run -p sd-cli -- location add ~/Documents

# Search indexed files
cargo run -p sd-cli -- search .

# Now launch Tauri app - it will connect to the running daemon

Running Tests

Spacedrive has a comprehensive test suite covering single-device operations and multi-device networking scenarios.

# Run all tests
cargo test --workspace

# Run specific test
cargo test test_device_pairing --nocapture

# Run with detailed logging
RUST_LOG=debug cargo test test_name --nocapture

# Run core tests only
cargo test -p sd-core

See the Testing Guide for detailed documentation on:

• Integration test framework
• Multi-device subprocess testing
• Event monitoring patterns
• Test helpers and utilities

All integration tests are in core/tests/ including device pairing, sync, file transfer, and job execution tests.

Development Commands

# Run all tests
cargo test

# Run tests for specific package
cargo test -p sd-core

# Build CLI in release mode
cargo build -p sd-cli --release

# Format code
cargo fmt

# Run lints
cargo clippy

---

Privacy & Security

Spacedrive is local-first. Your data stays on your devices.

• End-to-End Encryption: All P2P traffic encrypted via QUIC/TLS
• At-Rest Encryption: Libraries can be encrypted on disk (SQLCipher)
• No Telemetry: Zero tracking or analytics in the open source version
• Self-Hostable: Run your own relay servers and cloud cores
• Data Sovereignty: You control where your data lives

Optional cloud integration (Spacedrive Cloud) is available for backup and remote access, but it’s never required. The cloud service runs unmodified Spacedrive core as a standard P2P device—no special privileges, no custom APIs.

---

Documentation

• v2 Documentation - Complete guides and API reference
• Self-Hosting Guide - Deploy Spacedrive server
• Whitepaper - Technical architecture (work in progress)
• Contributing Guide - How to contribute
• Architecture Docs - Detailed system design
• Extension SDK - Build your own extensions

---

Get Involved

• Star the repo to support the project
• Join Discord to chat with developers and community
• Read the v2 Documentation for guides and API reference
• Read the Whitepaper for the full technical vision
• Build an Extension - Check out the SDK docs