ARCHITECTURE & DESIGN

What is Mornye Network Storage?
Architecture & Comparative Analysis

Author: NavyaXdev • Category: Architecture Deep Dive • Read Time: 8 min

In the modern self-hosting landscape, individuals and small engineering teams face a persistent dilemma when choosing a private storage server. On one end lie heavyweight collaborative suites like Nextcloud and ownCloud, which bundle hundreds of megabytes of PHP runtimes, relational databases, collaborative document editors, video conference servers, and background cron workers. On the other end sit low-level network file-sharing protocols like Samba (SMB/CIFS) or NFS, which were designed in the 1990s for local area network (LAN) segments, traverse firewalls poorly, and expose broad attack surfaces when routed to the internet.

Mornye Network Storage was created by systems developer NavyaXdev to occupy the optimal middle ground: a lean, single-purpose, highly performant network storage engine and RFC 4918 WebDAV server built from the ground up for modern Linux infrastructure. It combines rootless Docker containerization, cryptographic Argon2id password hashing, and automated Cloudflare Zero-Trust WAN tunneling.

Project Identity & Brand Distinction:

Mornye Network Storage is an open-source Linux self-hosted network storage system and RFC 4918 WebDAV server engineered and maintained by NavyaXdev. It is completely independent and separate from the Flutter/Rust desktop music application known as Mornye (mornyeapp).

Core Design Principles

PRINCIPLE 01

RFC 4918 Protocol Purity

No proprietary sync apps. Mounts natively in Windows 11/10 Explorer, macOS Finder, GNOME Files, KDE Dolphin, iOS Files, and mobile players like VLC and Symfonium.

PRINCIPLE 02

Attack Surface Reduction

Zero non-standard HTTP interfaces. No web dashboards on ports 8080/9000. Exactly one authenticated WebDAV endpoint, with admin operations via POSIX Bash CLI.

PRINCIPLE 03

Rootless Container Isolation

The internal engine executes under an unprivileged user (UID: 1000, GID: 1000) with all Linux kernel capabilities dropped and privilege escalation disabled.

PRINCIPLE 04

Zero Port Forwarding

Connects out to Cloudflare edge PoPs over outbound QUIC/HTTP2 tunnels. Inbound router ports stay closed, completely immune to WAN port scans.

PRINCIPLE 05

Deterministic Self-Healing

Through ./mornye.sh doctor --fix, Mornye inspects 11 system layers and automatically repairs permission drifts with safety snapshots.

Internal Architecture Breakdown

1. Transport & Authentication Boundary

Incoming requests arrive via loopback (127.0.0.1:8001) or Cloudflare edge SSL. Credentials are validated using Argon2id (64 MB memory cost, 3 iterations, 4 threads), the OWASP gold standard, rendering GPU dictionary attacks mathematically unfeasible.

2. Two-Phase Atomic Upload Pipeline

Streaming PUT uploads write into isolated temporary files with a .part suffix. On completion, Mornye runs binary magic bytes inspection via puremagic to verify file headers. If verified, the file is atomically renamed to its canonical path in ./storage and registered in SQLite with its SHA-256 hash.

3. SQLite Virtual Hierarchy & Physical Disk Isolation

Mornye decouples physical disk organization from the virtual WebDAV hierarchy. Storage files are kept safely in a deterministic flat structure while an ACID-compliant SQLite database (configured with Write-Ahead Logging / WAL mode) maintains folder relationships, quotas, and recycle bin retention.

Architectural Comparison: Mornye vs Alternatives

Feature / Metric Mornye Network Storage Nextcloud / ownCloud TrueNAS (Core/Scale) Samba (SMB/CIFS)
Primary Focus Fast, lean WebDAV file/music storage Full collaboration suite (Office, Talk) Enterprise ZFS appliance OS LAN file-sharing daemon
RAM Footprint ~60 MB – 120 MB 500 MB – 2 GB+ 8 GB – 16 GB+ ~40 MB – 80 MB
Container Privileges Rootless (UID: 1000, drop all caps) Typically Apache/PHP as www-data App containers / VM middleware Runs as root daemon
Remote Access (WAN) Cloudflare Tunnel (Zero port forwarding) Requires Reverse Proxy & Open Ports Requires WireGuard/OpenVPN Unsafe for raw WAN (Port 445)
Client Requirements Zero: Native Windows, Mac, Linux WebDAV Proprietary desktop/mobile sync apps Standard OS SMB/NFS client Standard OS SMB client
Self-Healing CLI Built-in (./mornye.sh doctor --fix) Manual occ commands Web GUI middleware & alerts Manual config editing

Deploy Sovereign Storage in Under 2 Minutes

Get your private cloud server running on modern Linux with our automated setup wizard.

View Installation Guide → Technical Documentation