Hanzo Object Storage

Object storage that runs as one binary wearing four hats: a master that tracks where everything is, volume servers holding the bytes, a filer for the namespace, and the HTTP gateway your code talks to. Buckets and objects, presigned links, multipart uploads, versioning and object lock, with server-side encryption whose keys are minted by Hanzo KMS rather than read out of a config file. Objects are erasure-coded across ten data shards and four parity shards, so four can be lost and the object still reads. Every call between the pieces speaks one binary protocol — there is no gRPC anywhere in the tree — which leaves one transport to secure and one to debug. And you never pay to read your own data back.