GATEWAY.TRDN.IO · IPFS + FILECOIN

Sovereign IPFS + Filecoin retrieval at the edge

Resolve any content-addressed identifier through a TRD-operated edge gateway. Multi-upstream fallback, 30-day immutable cache, zero vendor lock-in.

Checking…

How it works

Send a CID, get the bytes back. The gateway accepts any path of the form /ipfs/{cid} or /ipfs/{cid}/{path} and returns the raw content from the IPFS / Filecoin network. Requests are tried against a chain of trustless upstreams until one returns the content; the successful response is cached at the Cloudflare edge for 30 days and served immutably from then on.

GET https://gateway.trdn.io/ipfs/bafy…/manifest.json
trustless-gateway.link w3s.link 4everland.io ipfs.io

Why a TRD-operated gateway

TRD Network products — Storage, Compute, Sovereign, OS — pin receipts, manifests, and artifacts to Filecoin via content addressing. To dereference those CIDs in a browser or auditor's tool you need a gateway that's reliable and outside any single vendor's control plane. gateway.trdn.io is the primary; a cold standby (this Worker, deployed against a separate Cloudflare account) sits behind it and can be DNS-flipped to in minutes if free-tier limits hit or upstream availability degrades.

No accounts. No API keys. No tracking. Just CIDs in, content out.

Gateway in numbers

Uptime · 30d
99.97%
Receipts served
Cache hit rate
Edge POPs
330+
Static placeholder values · wired to a real stats endpoint in Phase 2.

Related products

The gateway is one layer of the TRD trust substrate. Verify the receipts you fetch through it, or explore the products that emit them.