Distributed storage that heals itself

curl -sSfL https://sh.getnauka.com | sh

Nauka splits every file into Reed-Solomon shards scattered across the nodes of a cluster. As long as k shards per stripe survive somewhere, the file comes back byte-for-byte identical.

Nodes find each other on the BitTorrent DHT, elect a founder if the cluster does not exist yet, authenticate one another, spread data by disk capacity and network distance, then repair and rebalance themselves — continuously, with no central server and no configuration file.

nauka keygen --out ./nauka-keys      # once
scp -r nauka-keys vps:/etc/          # to every machine
nauka --keys /etc/nauka-keys serve   # the same command everywhere

That’s it. The cluster forms itself.

Durable by arithmetic, not by copying

4+2 by default: every stripe survives losing any 2 shards out of 6, for a 50% storage overhead — where ×3 replication charges 200% for the same tolerance. BLAKE3 integrity is checked at every boundary; a corrupted shard is caught on read and treated as lost, never served.

Nothing to configure

A node’s identity is derived from its Ed25519 public key. Its address is auto-detected. The cluster is found on the Mainline DHT under a key derived from the cluster key — nothing else to distribute, not even a URL.

Aware of where it stores

Placement is weighted by declared disk capacity, so every node fills to the same percentage. Nodes also learn their network positions from measured round-trip times and pull a stripe’s shards apart — a file survives losing a region, not merely a machine.

Proofs, not claims

A node can assert it still holds what it quietly lost. Nauka demands blake3(nonce ‖ bytes) proofs of possession before giving up any redundancy, and audits its peers continuously by sampling.

How it compares

	Nauka	Garage	MinIO	IPFS
Erasure coding (no ×3 replication)	✅	❌	✅	❌
Self-healing	✅	partial	✅	❌
Config-free cluster formation	✅	❌	❌	✅
Single binary	✅	✅	~	~
Capacity-weighted placement	✅	✅	❌	❌
Topology-aware placement	✅	❌	❌	❌

Status

Young, but serious. The foundation is proven by integration tests that kill processes, cut power to the whole cluster, saturate the network and corrupt disks on purpose.

What is still missing before production use is spelled out without hedging in Operations and the Backlog — chiefly API authentication, NAT traversal and an S3 API.

Yogfile

Yogfile is the file-sharing service built on Nauka: end-to-end encryption in the browser, share links whose key never leaves the client, encrypted video playback with seeking. Nauka is the engine underneath.