Summary: Akave is a policy-shaped object-storage wrapper over decentralized storage backends. The point is zoning, residency, and S3-style control surfaces, not a new storage primitive.
What it does:
Offers S3-compatible object storage and tooling so developers can use decentralized storage through familiar cloud-style interfaces
Exposes policy controls around data residency, geofencing, encryption, replication, tiering, and verifiable provenance rather than only offering one generic storage class
Chunks uploaded files, encrypts data blocks with derived keys, applies Reed-Solomon erasure coding, and distributes resulting blocks across geographically dispersed nodes
Replicates stored blocks to Filecoin as an additional resilience layer, making Filecoin a backend durability component inside a higher-level storage-control plane
Uses Akave Oasis as the coordinating concept that links zones/subnets and manages zoning and geofencing restrictions across the network
Reconstructs missing or corrupted blocks during retrieval from available data/parity blocks before decrypting and reassembling the original file
Key claims:
The official docs frame Akave as AI-ready sovereign cloud storage with S3-compatible object storage, no vendor lock-in, zero egress fees, and immutable erasure-coded storage, which is the cleanest top-level classification signal
The docs emphasize programmable identity and policy controls, geofencing for data residency compliance, and cryptographically verifiable audit trails, which means the key novelty claim is a policy/governance layer above basic object storage
The main site describes Akave Oasis as enabling a marketplace of storage policies including tiered storage management, zoning, erasure coding, replication policies, and encryption, which is analytically important because policy composition is presented as a first-class mechanism
The data-security docs say files are split into 32 MB chunks and then smaller blocks, encrypted with derived keys from a master key plus file identifiers, and Reed-Solomon parity blocks are created for redundancy
The same security docs say Akave performs periodic data sampling and mini-proving for integrity checking, distributes blocks across geographically dispersed nodes, and has each node replicate data to Filecoin as a secondary resilience layer
The zoning docs say nodes are organized into explicit geographic zones and that data can be restricted to one zone for sovereignty, regulatory, or performance reasons, so geography itself becomes a protocol-level control surface rather than a hidden hosting choice
The zoning docs also describe Akave Oasis as the core coordinating node that manages data flow between zones and geofencing restrictions, which means practical authority may concentrate in the policy and coordination layer even if storage itself is decentralized
Whitepaper: No official standalone whitepaper or formal technical paper was found in the primary sources reviewed for this pass. See ../whitepapers/akave-primary-sources-2026-05-09.md.