OxiCloud

Self-hosted cloud storage, honestly reviewed. The origin story is in the README: NextCloud was too slow on someone’s home server, so they rewrote the whole thing in Rust.

TL;DR

• What it is: Open-source (MIT) self-hosted cloud storage — files, calendars, and contacts in one binary, built in Rust [1].
• Who it’s for: Homelab users, privacy-conscious founders, and small teams who want NextCloud’s functionality at a fraction of the resource cost. Also anyone running low-spec hardware (a $5 VPS, a Raspberry Pi, an old NUC) [1].
• Cost savings: NextCloud requires ~2 vCPU / 2 GB RAM and a ~1 GB Docker image. OxiCloud runs on 1 vCPU / 512 MB RAM with a ~40 MB image — meaning you can run it on a $4–6/mo VPS that NextCloud would choke on [1].
• Key strength: Raw performance benchmarks from the README are striking: 30–50 MB idle RAM vs 250–512 MB for NextCloud, sub-1-second cold start vs 5–15 seconds, essentially 0% CPU at idle vs 1–5% for NextCloud’s background cron jobs [1].
• Key weakness: Young project (2,788 GitHub stars, no third-party reviews indexed at time of writing), no plugin ecosystem, no managed cloud option — you are entirely on your own for deployment, maintenance, and debugging [1].

---

What is OxiCloud

OxiCloud is a self-hosted cloud storage platform written in Rust. It covers the same ground as NextCloud — file storage, WebDAV sync, CalDAV calendars, CardDAV contacts, shared links, user management — but built from scratch with a different philosophy: single binary, minimal dependencies, and Rust’s zero-cost abstractions instead of PHP’s runtime overhead [1].

The origin story is honest and in the README: the developer found NextCloud too slow on a home server and built OxiCloud instead. That’s not marketing framing — it’s the literal motivation, and it shows in what the project optimizes for [1].

The technical stack is a single compiled binary backed by PostgreSQL. No PHP, no Apache, no Redis for the core installation, no background cron jobs competing for database connections. The Docker image is ~40 MB on Alpine. The comparison table the project ships in its README is blunt and specific [1]:

Metric	OxiCloud	NextCloud
Docker image	~40 MB	~1 GB+
Idle RAM	~30–50 MB	~250–512 MB
Cold start	< 1 s	5–15 s
CPU at idle	~0%	1–5%
Min. hardware	1 vCPU / 512 MB	2 vCPU / 2 GB

The README itself adds the honest caveat: “NextCloud is a mature, feature-rich ecosystem. OxiCloud targets users who prioritise raw performance, simplicity, and low resource usage over plugin breadth.” That’s a fair and accurate framing — not a dismissal of NextCloud, just a clear statement of what OxiCloud is not trying to win [1].

As of this review: 2,788 GitHub stars, 117 forks, 534 commits, MIT license. The project is actively maintained with CI running on every push [1].

---

Why people choose it

No independent third-party reviews of OxiCloud were available at time of writing. The project is young enough that the review ecosystem hasn’t caught up yet. What we have is the GitHub repository, the README, and the project’s own positioning — which is unusually candid for a self-hosted project.

The use case that drives people here is almost always the same one: they tried NextCloud, got burned by the resource footprint or the PHP stack’s unpredictability, and went looking for something lighter. The README’s own framing leans into this: “NextCloud was too slow on my home server. So I built OxiCloud.” [1]

That sentence resonates in homelab communities because it’s a shared experience. NextCloud is powerful. It’s also historically slow on modest hardware, prone to background job pile-ups, and requires a more complex stack (PHP, Apache or nginx, Redis, cron, the app server itself). OxiCloud strips all of that out.

The secondary appeal is the protocol coverage. OxiCloud ships WebDAV, CalDAV, and CardDAV built-in — not as plugins that may or may not work, but as first-class supported protocols [1]. For anyone running a personal data stack where they want their calendar synced to their phone, their contacts synced to Thunderbird, and their files accessible from any WebDAV client, OxiCloud is feature-complete for that use case without touching the plugin system.

The SSO story is also stronger than expected for a young project. OIDC support for Keycloak, Authentik, Authelia, Google, and Azure AD is listed as built-in, not gated behind a commercial tier [1]. On NextCloud, SSO requires installing and configuring an app; here it’s in the binary.

---

Features

Storage and files [1]:

• Drag-and-drop uploads, multi-file selection, grid and list views
• Chunked uploads via TUS-like protocol — resumable, parallel chunks, MD5 integrity checking
• SHA-256 content-addressable file deduplication with reference counting (if two users upload the same file, only one copy is stored on disk)
• Adaptive compression: zstd or gzip selected based on MIME type
• Trash bin with soft-delete, restore, and retention-policy-based auto-purge
• Full-text search by name, type, date range, size, and recursive subtree (using PostgreSQL ltree)
• Inline preview for images, PDF, text, audio, and video
• Thumbnail generation with WebP/AVIF transcoding on the fly
• MIME type detection from magic bytes, not just file extensions

Protocol support [1]:

• WebDAV (RFC 4918) — streaming PROPFIND, locking, tested against major clients
• CalDAV — tested with Thunderbird, GNOME Calendar, iOS, DAVx⁵
• CardDAV — contacts sync with vCard support
• WOPI — edit Office documents directly in Collabora Online or OnlyOffice
• REST API — complete JSON API covering all operations

Security and auth [1]:

• JWT authentication with refresh tokens
• Argon2id password hashing (the current best-practice for password storage)
• OIDC/SSO — Keycloak, Authentik, Authelia, Google, Azure AD
• Role-based access (admin/user), per-folder permissions
• Storage quotas per user
• Shared links with optional password protection

Infrastructure [1]:

• Single binary, ~40 MB Docker image (Alpine)
• Dual PostgreSQL connection pool — a dedicated maintenance pool prevents background jobs from starving user queries
• Write-behind caching via moka for sub-millisecond hot reads
• LTO-optimized release build (fat LTO, 1 codegen-unit, opt-level=3)
• 112 automated tests, run on every CI push
• 9 UI languages: English, Spanish, German, French, Italian, Portuguese, Dutch, Chinese, Persian

What’s still in progress [1]: The project ships a TODO-LIST.md which is a healthy sign of honesty about gaps. Mobile clients, plugin support, and some features listed in the feature table as “in progress” or not yet confirmed stable should be verified against the current repository state before relying on them in production.

---

Pricing: self-hosted math

OxiCloud has no SaaS tier and no commercial license. It is MIT-licensed, self-hosted only. The cost is your server.

Self-hosted on a cheap VPS:

• OxiCloud binary + PostgreSQL: runs comfortably on a $4–6/mo Hetzner CAX11 (2 vCPU ARM, 4 GB RAM) or a $4/mo Contabo VPS
• With ~30–50 MB idle RAM, you can share this VPS with other services
• Storage cost is whatever your VPS provider charges for block storage — typically $0.04–$0.10/GB/month for attached volumes [1]

NextCloud for comparison:

• NextCloud itself is also free and open-source, but the hosting requirements are higher: minimum 2 GB RAM recommended, 1 GB+ Docker image
• A NextCloud-capable VPS starts around $6–12/mo for a usable setup, and you still need to manage PHP, cron, Redis, and the app ecosystem

Dropbox/Google Drive/iCloud for comparison:

• Google One: $3/mo for 100 GB, $10/mo for 2 TB
• Dropbox Plus: $10/mo for 2 TB
• iCloud+: $3/mo for 200 GB, $10/mo for 2 TB

The comparison math for storage: 2 TB of Hetzner Volume storage is around $40–80/mo depending on region. If you’re comparing storage costs alone, managed cloud wins at that scale. Where OxiCloud wins is when you also want CalDAV, CardDAV, WebDAV sync, shared links, user accounts, and OIDC — features that would cost $15–30/mo per user on managed platforms and are included for free here.

For a small team (2–5 people) sharing a file server with calendar and contact sync, the economics are clear: OxiCloud on a shared $10/mo VPS beats $15–30/mo per user on managed alternatives by an order of magnitude.

---

Deployment reality check

The setup is straightforward by self-hosted standards. The repository ships a docker-compose.yml and an example.env. The README’s Quick Start section covers Docker Compose deployment [1].

What you actually need:

• A Linux VPS or home server with at least 512 MB RAM (1 GB recommended for comfort)
• Docker and docker-compose
• PostgreSQL (bundled in the docker-compose or external)
• A reverse proxy (Caddy or nginx) for HTTPS — not strictly required for local use, but necessary for remote access or CalDAV/CardDAV clients that require HTTPS
• A domain name if you want HTTPS with a trusted cert

What you get from the docker-compose: The default docker-compose.yml includes OxiCloud and PostgreSQL. That’s it — notably simpler than NextCloud’s docker-compose which typically includes the app, a database, Redis, and a cron container [1].

What can go sideways:

• OxiCloud is a younger project than NextCloud or Seafile. With 2,788 stars and 534 commits, it has meaningful adoption but a much smaller community to debug against. If you hit an edge case, you’re filing a GitHub issue, not searching a five-year-old forum thread.
• The feature status table in the README distinguishes between “Working,” “In Progress,” and unlisted — worth reading carefully before depending on any specific protocol or feature in production.
• Helm charts are included for Kubernetes deployment, but Kubernetes is overkill for what this project is — stick with docker-compose unless you’re already running k8s for other reasons.
• WOPI (Office editing via Collabora or OnlyOffice) requires those services separately. OxiCloud provides the WOPI integration; you bring the office server.
• No official mobile app was confirmed stable at time of writing — the merged profile lists “mobile_app” as a feature, but verify against the current TODO-LIST.md before planning mobile-first workflows.

Realistic time estimate for a technical user: 20–40 minutes to a working instance with Docker Compose. For someone comfortable with Linux but new to self-hosting: 1–2 hours including domain and HTTPS setup. No previous Rust experience required — you’re pulling a pre-built Docker image.

---

Pros and cons

Pros

• Genuinely lightweight. The 30–50 MB idle RAM and ~40 MB Docker image aren’t marketing claims — they follow directly from a single compiled Rust binary replacing a PHP stack. If you’re running services on modest hardware, this is a real difference [1].
• MIT license. No fair-code restrictions, no commercial tiers, no license review required. You can embed it in your product, fork it, or self-host without legal overhead [1].
• Protocol coverage is first-class. WebDAV, CalDAV, CardDAV, WOPI, and OIDC/SSO are all built into the binary, not plugins. On NextCloud these require separate apps that may lag behind the main release [1].
• SHA-256 deduplication. Storage-efficient by design — duplicate file content is stored once with reference counting. Most file servers don’t do this [1].
• Argon2id for passwords. The password hashing choice shows security awareness. This is the current OWASP recommendation and better than what many mature projects still use [1].
• Honest README. The project explicitly states what it doesn’t try to win against NextCloud. Self-aware scope is a green flag for long-term maintainability.
• 112 automated tests running on every push. Not a guarantee of stability, but a meaningful signal that the maintainer treats CI as a real gate [1].

Cons

• No independent reviews exist yet. For a tool you’re betting your file infrastructure on, the absence of community battle-testing is a real concern. You’re early.
• No plugin ecosystem. NextCloud’s app store has hundreds of integrations. OxiCloud has none — what ships in the binary is what you get. If you need something the binary doesn’t include, you’re filing a feature request or writing it yourself.
• No managed cloud option. NextCloud has Nextcloud.com. Seafile has SeafileCloud. OxiCloud is self-host only. If deployment is the blocker, there’s no paid tier to fall back on.
• Mobile client maturity unclear. The feature list includes mobile app support, but verifying current stability against the TODO-LIST.md is necessary before mobile-first workflows [1].
• Small community means slower issue resolution. 2,788 stars is respectable for a project this age, but it’s three orders of magnitude smaller than NextCloud’s user base. Stack Overflow answers, forum threads, and blog posts don’t exist yet.
• Single maintainer risk. The project appears to be primarily from a single organization (DioCrafts). There’s no YC backing or company behind it — just an open-source project. This is fine for a homelab tool, more concerning if you’re running it for a team of 20.

---

Who should use this / who shouldn’t

Use OxiCloud if:

• You’ve tried NextCloud and found it too slow or too heavy on your hardware.
• You’re running a home server, Raspberry Pi, or low-spec VPS and need a file+calendar+contacts stack that won’t consume your entire resource budget.
• You want MIT-licensed software with no strings attached.
• Your use case is covered by what’s in the binary: file storage, WebDAV, CalDAV, CardDAV, OIDC, shared links, basic RBAC.
• You’re comfortable diagnosing issues with a smaller community and younger project.

Skip it and use NextCloud if:

• You need a plugin ecosystem — NextCloud has hundreds of apps covering everything from video chat to project management to e-signature.
• You need a large support community, years of Stack Overflow answers, and commercial support options.
• Your team is non-technical and needs a managed option with a support contract.
• You depend on NextCloud-specific integrations (Talk, Collectives, Mail as a standalone app, etc.).

Skip it and use Seafile if:

• You prioritize file sync reliability and performance over protocol breadth. Seafile has a more mature client ecosystem and a longer track record for sync.

Skip it entirely (use managed cloud) if:

• Your primary concern is storage cost at multi-terabyte scale — object storage from Backblaze B2 or Wasabi is cheaper per gigabyte than block storage on any VPS.
• You have no technical person on your team and won’t pay to have one deploy this.

---

Alternatives worth considering

• Nextcloud — the obvious comparison. Mature, extensible, massive plugin ecosystem, much higher resource footprint. If you need breadth over performance, NextCloud wins. [nextcloud.com]
• Seafile — strong file sync client, better track record on reliability, older project. Less protocol coverage out of the box (no CalDAV/CardDAV without plugins). Community edition is free.
• Syncthing — not a cloud server, but a peer-to-peer sync tool. Zero server cost, no web UI, no shared links — but excellent for pure file sync between devices you control.
• Immich — purpose-built for photos and videos. If photos are your primary use case, Immich is more specialized and more polished than any general-purpose cloud storage for that workflow.
• Filestash — lightweight web file manager with WebDAV and S3 backend support. More of a frontend than a storage platform.
• ownCloud — the older fork that NextCloud came from. Slower development pace than NextCloud now, but still maintained.

For a non-technical founder whose primary use case is escaping Google Drive or Dropbox pricing, the realistic choice is OxiCloud vs Nextcloud. Pick OxiCloud if resource efficiency matters and you don’t need plugins. Pick NextCloud if you need ecosystem depth and are willing to provision more hardware.

---

Bottom line

OxiCloud is what you get when someone actually bothered to rewrite the problem correctly instead of extending the legacy stack. The performance numbers are genuine: a 40 MB Docker image and 30–50 MB idle RAM is not NextCloud-with-optimizations, it’s a fundamentally different architecture. For homelab users and small teams who’ve bounced off NextCloud’s resource requirements, OxiCloud delivers everything you actually need — file storage, calendar sync, contacts sync, WebDAV, OIDC — in a single binary backed by Postgres.

The honest caveats are about maturity, not quality. The project has 2,788 stars and no third-party review ecosystem yet. There are no plugins, no managed cloud tier, and no large community to debug against. You’re betting on a well-architected early-stage project, not a hardened production platform. For a homelab or a small team, that’s an acceptable trade. For running mission-critical infrastructure for a 50-person company, wait another year.

If deployment is the blocker — setting up Docker, a reverse proxy, and a domain — that’s a one-time setup task, not an ongoing burden. It’s exactly the kind of thing upready.dev deploys for clients as a one-time service.

---

Sources

1. DioCrafts/OxiCloud — GitHub Repository and README. Primary source for all feature claims, performance benchmarks, and architectural comparisons. https://github.com/DioCrafts/OxiCloud

Note: No independent third-party reviews of OxiCloud were available at time of writing (April 2026). The third-party sources provided for this article were unrelated to OxiCloud (Yahoo Mail, Japanese news, Microsoft layoff coverage) and are not cited. All claims in this review are grounded in the project’s primary source materials.