Run Your Own Arweave Gateway

This site has a permanent copy on Arweave. The live version you’re reading is served from Cloudflare for speed; the Arweave copy at archerships.arweave.net survives even if a company decides to censor this domain. You don’t have to trust either one – because the content is on a neutral permanent data network, you can serve it yourself with your own gateway.

Why run your own gateway

An Arweave “gateway” is the layer that fetches, caches, and serves data from the Arweave network over HTTP. Public gateways (arweave.net and others) are convenient but are third-party choke points. Running your own means:

The two-layered answer

  1. Quickest access (no gateway): browse any Arweave content through a public gateway you trust. archerships.arweave.net is one; arweave.net and arweave.dev are others. The ARNS name resolves to the latest manifest of the permanent copy.

  2. Real independence (your own gateway): run the server software that talks to the network and serve the data yourself. Official guidance and gateway setups live at:

    • Arweave docs: docs.arweave.org (node + gateway architecture)
    • ar.io gateway network: ar.io (decentralized gateway / resolver subnet)
    • Reference client: arweave-node (the core network node)

Minimal practical path

This site, permanently

If archerships.com ever stops resolving or is blocked, the full modern site (and the legacy archive) remains on Arweave at archerships.arweave.net – and the underlying manifest can be fetched and re-served by any gateway you operate. Point your own gateway at it and the site keeps working on your terms.

To subscribe via Atom/RSS, please find the feed links on my Contact page.