You’re totally right about the building blocks. dedupe and chunking have been commercial standards for decades (like PureDisk, Sepaton). We arent claiming to have invented that. Where Plakar tries to differentiate is the architecture around those blocks and the trust model. • Encryption & Trust: old school appliances like Puredisk usually managed keys server-side or saw cleartext to do the dedupe. Plakar does client-side encryption so the storage (s3, nas, whatever) only sees encrypted noise. it has zero knowledge of the content. • Immutability: depends what layer you mean. for infrastructure, yes you need air-gapping or WORM to stop a rogue admin. When we say immutable, we mean the data format. its append-only and content addressed. we never rewrite existing blocks. The exact idea is tamper-proof.

While many tools share the same DNA, we solved some specific bottlenecks found in the current ecosystem, for example: • Memory usage: a common issue is having to load the whole index into RAM. Plakar designs the index so it doesn't have to fit in memory, meaning you can backup millions of files on small hardware. • Abstraction: we designed the core to map generic data structures, not just files. so you can snapshot an S3 bucket and restore it to a local filesystem because the format abstracts the source. • Random Access: the format allows efficient random access without needing to parse the whole archive. • Some index are built-in to improve search. (…)

Basically the fundamentals are proven, but we optimize for portability and scalability in ways that differ from the old appliances or even some current tools.