A fast self-hosted cloud for people who want files, calendars, contacts, and office editing without dragging a heavy stack behind them. Documentation · Quick Start · Star OxiCloud · Request a Feature · Supported Clients · Project Status If OxiCloud saves you setup time, RAM, or complexity, give it a star . If something is missing, ask for a feature or request a docs improvement . Why People Try OxiCloud OxiCloud is…
OxiCloud is aimed at self-hosters, home labs, and small teams who want the useful parts of a cloud suite without the operational drag of a traditional PHP stack.
What pulls people in:
Standard protocols first: WebDAV, CalDAV, and CardDAV are built in
OxiCloud is not trying to mirror the full plugin ecosystem of Nextcloud. It is designed for a smaller stack, fast startup, and standards-based interoperability.
Quick Start
Docker Compose
Requires Docker and Docker Compose.
git clone https://github.com/AtalayaLabs/OxiCloud.git
cd OxiCloud
cp example.env .env
# If users will access OxiCloud through a domain or reverse proxy,
# set OXICLOUD_BASE_URL in .env before the first login.
docker compose up -d
Open http://localhost:8086.
Prebuilt binary
Binary releases (Linux musl amd64/arm64, macOS Intel/Apple Silicon)
are attached to every tagged release on GitHub — the whole SPA + all
operator subcommands + migrations bake into a single self-contained
executable. See docs/install/binary.md for
the download / verify / systemd walkthrough.
cargo binstall oxicloud works too once a release is out.
Run from source
Requires Rust 1.93+ and PostgreSQL.
git clone https://github.com/AtalayaLabs/OxiCloud.git
cd OxiCloud
cp example.env .env
# If PostgreSQL runs on your host instead of Docker, update both
# OXICLOUD_DB_CONNECTION_STRING and DATABASE_URL to use localhost:5432.
cargo run
OxiCloud ships with more than 4,500 automated tests that run on every change. They cover every layer of the stack — Rust unit and integration tests, frontend unit tests, API wire tests, end-to-end browser flows, and WebDAV compliance.
One guiding principle: every issue a user reports lands with a test once it is fixed. A bug that reached production is proof the test suite missed something; the pin for it ships in the same patch as the fix, in the lowest layer that would have caught it. The test is the deliverable, not the diagnosis.
OxiCloud is co-developed with large language models. The project treats them as a productivity tool, not an authority: anything that touches architecture, security, data integrity, or performance is strictly challenged against first principles — reviewed against the hexagonal boundaries, measured against the 10k-user scale target, benchmarked where it matters, and often rewritten — before it lands. Code suggestions pass the same bar as any human contribution: tests, linters, benchmarks, and reviewer scrutiny.
The regression discipline from the Testing & Quality section applies without exception here: an LLM-authored change that introduces a bug ships its own test the moment the bug is caught, in the same patch as the fix.
If you are not ready to code yet, starring the project and opening a precise feature request is still a meaningful contribution.
Contributors
OxiCloud is a community-driven project, and we appreciate all contributions. Check out the Contributors page to see the amazing people who have helped make OxiCloud better.
评论