
Launch a coin. Get your own server. Keep your project alive when traditional hosting fails.
Your wallet signs a real Pump.fun create_v2 transaction on Solana mainnet. Optional dev buy executes in the same transaction. 404 builds and simulates it; you see the exact SOL cost before signing. Funds never touch a 404 wallet.
[ wallet ]──sign──▶ create_v2 (+ buy)
│ simulate ✓ cost ✓
▼
Solana mainnet ──▶ mint + curve verifiedConfirmation on-chain provisions a server with a sequential ID. Each server is an isolated, managed website environment with its own deployments, backups, checks and history — not a dedicated VPS.
confirmed tx ──▶ SERVER 404-000001
├─ website v1
├─ primary + secondary deploy
└─ IPFS backupEvery coin gets a generated site with logo, ticker, contract, socials and a Pump.fun link. Edit, preview and publish; every version is an immutable snapshot you can restore.
content ─▶ render (escaped, no JS) ─▶ v3.html
sha256 ─▶ 9f2c…e1
restore v1 ─▶ publishes v4 (history kept)Each version is pinned to IPFS via Pinata, then fetched back through gateways and hashed. A backup is VERIFIED only when the retrieved bytes match the original SHA-256 — an upload receipt is not proof.
snapshot ─pin─▶ CID bafy…
CID ─fetch─▶ gateway ─sha256─▶ match? ─▶ VERIFIED
└─no─▶ FAILEDA worker measures primary, secondary and IPFS every ~60s: HTTP status, latency, and a content checksum. Uptime is computed only from real measurements, starting when monitoring began.
t+00s PRIMARY 200 142ms sha ✓ t+60s PRIMARY 200 151ms sha ✓ t+120s PRIMARY --- timeout ✗ (1/3)
After N consecutive failed checks the resolver routes visitors to an independent secondary host, then IPFS, then the archive. Recovery requires sustained health and a minimum hold time — no flapping. Run a Blackout Test to prove it.
/go/404-000001 PRIMARY ✗✗✗ ──▶ SECONDARY ✓ (failover logged) PRIMARY ✓✓✓ + hold 5m ──▶ PRIMARY
Every server is a node in the 404 Network, wired to the shared infrastructure layer. Components that are not configured are shown as NOT CONFIGURED — never as operational.
[ MONITOR ]
│
○─○─○─┼─[ PRIMARY ] ○ = server node
○─○───┼─[ SECONDARY ]
○─────┴─[ IPFS ]Everything shown on 404 comes from real records: transactions, deployments, checksums and measurements. If something is not configured, it says so.