Implemented foundation
The current project direction includes the core parts of a modern self-hosted file server:
- File and folder browsing, management, and search.
- Sharing with permissions and revocable links.
- Local authentication, two-factor options, recovery codes, and optional OIDC.
- User permissions, scoped tokens, login controls, and audit logs.
- Local version history.
- WebDAV, API, CLI, desktop, and Android access paths.
- Local storage with per-space backend choices.
- SQLite with optional PostgreSQL.
This list describes implemented capability, not identical maturity across every workflow.
Testing gaps
| Area | Present status | Why it matters |
|---|---|---|
| Android | Emulator-only validation | Physical devices add storage, battery, camera, and background-work behavior |
| Windows client | Alpha; expect bugs, missing features, and breaking changes. Files-on-demand not verified | Placeholder and hydration behavior can vary by Windows version |
| AVIF | Preview coverage incomplete | Encoders and metadata combinations need broader fixtures |
| iOS | No mature client path stated | Mobile users need a clear, supported alternative |
| Video | Playback and transcoding scope is limited | Codec support differs across browsers and devices |
| Storage migration | Not presented as a finished workflow | Moving large libraries between backends needs resumability and verification |
Operational limits
Early releases should be treated as lab or carefully supervised deployments. Upgrade and rollback behavior, large-library performance, interrupted transfers, and long-running client sync need evidence across more real environments.
Version history applies to local storage and must not be read as a universal promise across every backend. A version history is also not a backup: deletion, administrative error, or a failed disk can affect both current and historical data.
Near-term priorities
The roadmap should remain evidence-based rather than turning wishes into commitments. Confirmed priorities from the current brief are:
- Publish reproducible server artifacts and a verified deployment contract.
- Expand real-hardware testing for Android and desktop clients.
- Move the Windows client out of alpha and verify its files-on-demand behavior.
- Improve media-format coverage, including AVIF and video.
- Define and test storage migration procedures.
- Document backup, restore, upgrade, and security reporting paths.
Dates will be added only when the project can support them.
How status will improve
Public releases should connect each status claim to something inspectable: an automated test, a hardware test note, a known-issues entry, or a reproducible procedure. The goal is not a green dashboard; it is a trustworthy description of what a user can depend on today.