Home  /  Products  /  Storage

🗃 The permanence layer

Your website, mathematically permanent.

Storage mirrors every DCS-built site to Filecoin the moment it publishes — content-addressed, replicated across independent providers, and backed by a cryptographic proof of storage. No vendor in the path. No "deal terminated" email. Ever.

CID bafy…7h2x ORIGIN · 1× REPLICAS · 3× COLD BACKUP · 7× FILECOIN SPs PERMANENT · cryptographically signed · auditable
How permanence works

The hash is the address. Tampering is impossible to hide.

On Filecoin, every file is addressed by the hash of its own contents — its CID. Change a single byte and the hash changes, so the CID stops resolving. There is no way to alter stored data and have it still look like the original.

  • Content addressing — the hash is the identity
  • Tamper detection is built in, not bolted on
  • An authorship certificate (PDF + CID) for every asset
Stored site✓ original
<html> bella-cucina … </html>
CID  bafy…7c4a9
✓  CID resolves — bytes verified intact

Watch a tampered byte break the CID — and the gateway refuse to serve it.

Replication tiers

Pick how permanent permanent should be

Every artifact is pinned with a replication factor and a durability window baked into its receipt. Choose a tier and watch the copies spread.

📄
Your site
bafy…7c4a9
🌏
Provider 01
available
🌏
Provider 02
available
🌏
Provider 03
available
🌏
Provider 04
available
🌏
Provider 05
available
🌏
Provider 06
available
1 copyIndependent providers storing your site
1 yearDurability window in the receipt
LowLoss risk — provider failures tolerated

A representative view — the live network spans thousands of independent providers across every continent. Pay-once-store options available; pricing is fixed, no credits.

Properties you can't get from S3 or R2

Why DCS outlasts Wix, Squarespace and the rest

Decentralized storage isn't a marketing label — it's a different set of guarantees. No single vendor in the path. No pricing changes overnight.

🌏

Global open-source storage

Thousands of independent storage providers across every continent. No single vendor can deplatform you, raise prices unilaterally, or lose your data.

💲

Hypercompetitive pricing

Providers compete in an open market. Pricing is transparent and trends down — pay-once-store-forever deals exist. Try getting that from AWS.

🔒

Provable security

Content addressing means tampering is detectable. Every byte hashes to its CID — change a stored site and the CID simply stops resolving.

Customizable strategy

Replication count, region preference and encryption are configurable per site. Defaults handle the 99% case; the knobs exist for the 1%.

Three proofs, run continuously

Replication you can verify — not just trust

"Stored" should mean provably stored, right now. Three Filecoin-native proofs run across the network so replication is real, not nominal.

01 · PROOF-OF-SPACETIME

Still storing, continuously

Providers continuously prove they still hold the data over time — not just that they once received it. A lapsed proof triggers automatic re-replication.

02 · PROOF-OF-REPLICATION

Every copy is distinct

Each replica is cryptographically distinct. A provider can't store one copy and report many — replication is real, not nominal.

03 · VERIFIABLE ACTION

Publicly-verifiable deals

Every site upload produces a public deal. Anyone can audit when, where and by whom your site was preserved — no trust in DCS required.

Every action, signed and chained

Filecoin secures the data. Storage secures the provenance.

Every DCS agent action — compute, build, deploy, erasure — is signed with ed25519 and pinned to Filecoin alongside the artifact. Same chain head CID surfaces in the OS dashboard, the public verifier and the certificate PDF.

Compute event
🧾ed25519 signed
🌏Pinned to Filecoin
🏷CID = chain head
Verifiable in browser
Live

Ed25519 signed receipts

Every compute_inference, build_complete and erasure_complete event is signed at emit time with the dcs-receipt-key-2026 private key. Canonicalised JSON, sorted keys, no whitespace — anyone can recompute the bytes and verify.

Live

Filecoin pinning · same chain

Each receipt is pinned to Filecoin via Lighthouse SDK 0.4.5. The CID becomes the universal handle. Storage is the only product where every action and every artifact are content-addressed on the same network.

Live

Chain head — everywhere

The same chain head CID surfaces in the OS dashboard, on the public verifier at verify.dcsai.ai, and inside the certificate PDF — three views, one provable handle.

What we preserve on Filecoin

Twelve categories of data, built to outlive any platform

Auto-mirror covers websites today; the others land progressively as the DCS product surface expands.

🤖
AI-generated sites Every DCS-built site, auto-mirrored to Filecoin on publish.Live
📄
Documents & archives Documents, photos and archives that should outlive any platform.Soon
App state & configs State, configs and settings that travel with the user, not the vendor.Soon
📊
Operational records Records preserved beyond corporate lifecycle events.Soon
📚
Public datasets Open knowledge — Wikipedia, OpenStreetMap, Gutenberg — backed up forever.Soon
🔐
Encrypted files Encrypted client-side via Kavach — plaintext never leaves the browser.Soon
🎥
Video Long-form video without YouTube's compression and policy risk.Soon
🔬
Scientific datasets Reproducibility-grade preservation for datasets and code.Soon
🎵
Audio archives Audio independent of any single hosting provider.Soon
📜
Tamper-evident logs Tamper-evident logs for compliance and forensics.Soon
Timestamped agreements Provable timestamping of agreements and addenda.Soon
🔗
Permanent references Decentralized references — no IPFS-pinning-service risk.Soon
Public datasets we'll preserve

Five datasets we plan to preserve permanently

Open knowledge benefits from open infrastructure. These are the datasets DCS intends to mirror — pinning sequenced as community partnerships and budget allow.

📚
Wikipedia ~95 GB · all languagesPLANNED
🗺
OpenStreetMap ~52 GB · planet-osm.pbfPLANNED
🧬
gnomAD ~8 GB · genomic variantsPLANNED
📖
Project Gutenberg ~12 GB · 70k+ booksPLANNED
🌧
OpenAQ ~5 GB · global air qualityPLANNED
Shipped & coming

What's live now, in-flight, and next

Transparent about what works in production today and what's on the way.

Live

Replication tiers

1× / 3× / 5× replication with 1y / 7y / 99y durability windows — the SLA tier is baked into every receipt.

Live

Integrity meter

Batched cross-replica query in under 30s. A public meter shows replica count and any at-risk receipts.

Live

Cryptographic erasure

Per-tenant DEK + KEK wrapping. Erasure shreds the key; data on Filecoin becomes mathematically unreadable, with a signed receipt.

Live

Compute artifact auto-pin

Build logs, image bank and agent outputs auto-pinned to Filecoin after every Compute run — prompt to site to artifacts, all chained.

Live

Hourly re-pin sweep

An hourly sweep re-attempts failed or pending pins — no artifact gets stuck in limbo on a transient backend blip.

Live

On-chain operator reputation

Operator reputation anchored on Base alongside the receipt chain — the first mint is executed and live.

Live

EU region

An EU backend is deployed; gateway and orchestrator images are public on GHCR for independent inspection.

In-flight

x402 agent payments

The x402 HTTP payment protocol on the upload endpoint — agents pay-as-they-pin, on rails Filecoin natively understands.

Next

"Make Permanent" checkout

A one-click upgrade to a pay-once, store-forever permanence deal — straight from the dashboard.

Named, dated, honest

Phase by phase, with dates

Six phases from auto-mirror to cross-product permanence. Most of the underlying infrastructure already runs in production; phase milestones are productisation steps.

MAY 2026 · PHASE 1-4 · FOUNDATION SHIPPED

Storage service scaffolded

Magic-link auth, Cloudflare Pages frontend, Lighthouse SDK 0.4.5 wedge unlock, asset vault CRUD with sha256 dedup, drag-drop upload, per-asset certificate PDF, v3 premium frontend redesign. 30+ items completed across May 7-12. 19 sessions verified mirrored.

MAY 17 2026 · PHASE 5 · VERIFIABLE BUILD PROVENANCE SHIPPED

Ed25519 receipt chain + public verifier

Receipt chain, public verifier, certificate-chain PDF, network stats, embed badge, press kit, JSON export. Satisfies Storage NEW 1 + Compute NEW 1 + Unified Roadmap X1 simultaneously. Day 1-10 v3 marathon delivered this.

~3-4 DAYS · PHASE 6 · PERMANENCE SLA TIERS SOON

Standard / Guaranteed / Permanent

Standard (mirrored), Guaranteed (multi-region pinned + monitored), Permanent (endowment-style, Arweave pay-once model adapted). Live on-chain "last proven retrievable" timestamp per tier — wraps Filecoin's 2026 SLA-driven storage markets as a product available now.

NEXT · PHASE 7 · CROSS-PRODUCT PERMANENCE SOON

Auto-pin Compute artifacts

SDXL image bank, build logs, agent outputs — auto-pinned. Storage becomes the permanence layer for the entire DCS ecosystem, not just the website product. The moat made concrete — requires owning Platform + Compute + Storage at once.

What Storage won't do

The honest list of things it isn't built for

We've watched too many "decentralised storage" products oversell. Here's the honest list of things Storage is not built for, and won't pretend to handle.

✖ WON'T DO

Compete with S3 on hot-read latency

Your customer-facing site loads from Vercel's edge — sub-100ms globally, same speed as Wix. The Filecoin mirror is for permanence and verification, not for serving traffic. We trade a few latency points for guarantees AWS structurally can't offer.

✖ WON'T DO

Replace your primary database

Filecoin is for content-addressed artifacts, not transactional records. Storage mirrors websites, certificates and signed receipts — all things that benefit from immutable + auditable. Your CRM, your bookings table, your inventory — those live in Postgres.

✖ WON'T DO

Index private encrypted data

Private archives are encrypted client-side via Kavach. Plaintext never leaves the browser. We physically cannot search inside encrypted blobs — if you need search, store metadata separately.

✖ WON'T DO

Push crypto wallets onto end users

Your customers visit a normal HTTPS URL — no wallets, no MetaMask, no seed phrases. The Filecoin mirror is invisible to them. We won't bolt on a Web3 layer that adds friction to your users' experience.

See it in action

Publish once. Preserved forever.

A site auto-mirrored on publish — and an integrity check anyone can run.

auto-mirror on publish
[platform] site published — bella-cucina.dcsai.app [storage] hashing site — CID bafy…7c4a9 [storage] pinning 3× across independent providers [storage] authorship certificate generated — PDF + QR [deal] public Filecoin deal confirmed
Mirrored — permanent in 58s
verify integrity
$ dcs storage verify bafy…7c4a9 [verify] querying 3 replicas… [verify] re-hashing bytes — CID match on all 3 [verify] proof-of-storage current — 0 at risk [proof] integrity confirmed, client-side
Verified — bytes intact, no trust in DCS
1×–5×Replication tiers
99 yearsTop durability window
<100msEdge latency, hot read
<30sCross-replica integrity query
CID-addressedTamper-evident by design
Built on the open decentralized stack

Open standards, no proprietary lock-in

Filecoin IPFS Lighthouse SDK Content addressing x402 payments Base (on-chain reputation) S3-compatible API
Works with

The rest of the platform

Storage is the permanence layer — these products write to it.

FAQ

What people actually ask

Real questions, answered straight.

What happens to my site if DCS shuts down?
Your site is content-addressed on Filecoin under a CID anyone can fetch from any Filecoin gateway. The certificate PDF includes the CID, deal IDs and provider list. If DCS disappears tomorrow, your site keeps serving from its mirror — no dependency on us.
Is Filecoin slower than regular hosting?
For serving traffic, no. Your customer-facing site loads from Vercel's edge — sub-100ms globally, same speed as Wix or Squarespace. The Filecoin mirror is a permanence layer, not a serving layer.
How is this different from "we make backups"?
Backups live with the vendor. Filecoin mirrors live on a public, content-addressed network with cryptographic proofs of storage, replication and retrievability. A backup is gone when the vendor is gone; a mirror isn't.
Do my customers need crypto wallets to view my site?
No. They visit a normal HTTPS URL on your custom domain or our edge. The Filecoin mirror is invisible to the visitor — it just makes the site survivable.
What does the authorship certificate prove?
It cryptographically binds the site content (its sha256 and CID) to a point in time, the deal IDs that pinned it, the providers that stored it, and a QR code anyone can verify against the public network — no trust in DCS required.
Does this cost extra on top of DCS?
Auto-mirror on publish is included for the AI-built sites. Higher replication tiers (3× / 5×) and pay-once-store-forever permanence deals are priced separately — transparent, with no hidden credits.
Can I export my site from DCS?
Yes — the CID alone is your export. Anyone with the CID can pull the full bytes from the network. There's also a one-click ZIP export from the Storage dashboard.
What's on the roadmap?
Phase 6 (permanence SLA tiers) lands next, followed by Phase 7 (cross-product auto-pin for Compute artifacts). The honest timeline above shows dates and current status.

Be first when site mirroring goes live across all DCS plans.

One email when auto-mirror unlocks for every tier. No drip campaign. No sales sequences.

Make your site permanent.

Content-addressed, replicated, and provable — preserved long after any vendor is gone.

Pick a permanence tier How it works