Onchain, S3-compatible decentralized object storage running as an Avalanche L1 with Filecoin as the cold-tier. Targets enterprise/AI workloads with verifiable audit trails, zero egress fees, and SQL/Iceberg integrations.
- 01S3 drop-in with onchain audit trail
- 02AI / analytics datasets (Iceberg / Snowflake-compatible)
- 03DePIN data layers with verifiability
- 04geofenced data sovereignty workloads
- 05ransomware-resistant enterprise object storage
- pnpm add @aws-sdk/client-s3
| Variable | Scope | Description |
|---|---|---|
| AKAVE_ACCESS_KEY_ID | Server | Akave Cloud S3 access key (from the Akave dashboard). Server-side only. |
| AKAVE_SECRET_ACCESS_KEY | Server | Akave Cloud S3 secret access key. Server-side only. |
| AKAVE_ENDPOINT | Server | Akave S3-compatible endpoint, e.g. `https://o3.akave.xyz`. Confirm the exact host in the Akave dashboard. |
| AKAVE_BUCKET | Server | Bucket name created in your Akave Cloud account. |
Akave is S3-compatible — use the AWS SDK v3 directly. Initialize with `new S3Client({ endpoint: process.env.AKAVE_ENDPOINT, region: 'akave-network', credentials: { accessKeyId: AKAVE_ACCESS_KEY_ID, secretAccessKey: AKAVE_SECRET_ACCESS_KEY }, forcePathStyle: true })` and use `PutObjectCommand` / `GetObjectCommand` / multipart upload commands as you would with S3. Generate presigned URLs for browser uploads via `getSignedUrl(s3, new PutObjectCommand({ Bucket, Key }), { expiresIn: 900 })`. For onchain provenance, query the Akave L1 explorer or its smart-contract APIs to verify the storage proofs / audit trail for a given object — Akave anchors metadata onchain so you can prove existence without trusting the gateway. For programmatic L1 setup, the open-source `akavesdk` repo provides Go and lower-level access.
- ⚑Akave is Avalanche-L1 native — proofs and audit metadata live on the Akave L1, not on Filecoin or Avalanche C-Chain. Verify which chain your contract reads from before integrating onchain checks.
- ⚑S3 compatibility covers core object operations; some advanced AWS features (object lock, replication policies, SSE-KMS) may not behave identically — always test multipart uploads and lifecycle rules end-to-end.
- ⚑Zero-egress is the headline price but throughput SLAs differ from AWS — for very high-QPS read paths put a CDN in front; do not assume single-region S3 latency.
- ⚑Encryption-at-rest defaults to network-managed keys; for client-side E2E encryption you must encrypt before upload and manage keys yourself.
- ⚑Akave is relatively new (2026 launch on Avalanche L1) — APIs and endpoint URLs can change. Pin the SDK version and monitor changelog for breaking endpoint moves.
- ⚑Don't conflate Akave with Akash — `akave.com` / `akave.network` is the storage L1; `akash.network` is the unrelated decentralized compute marketplace.