> loading
> loading
Launch a coin. Get your own server. Keep your project alive when traditional hosting fails.
Watch a coin boot, replicate and survive. At the end, kill hosts yourself and see where traffic goes.
Your wallet signs pump.fun's create transaction. The mint key is generated in your browser; 404 never holds a key that can move your funds.
Create your coin on pump.fun from your own wallet. 404 verifies the transaction on-chain before anything else happens.
Your coin gets an isolated tenant environment: its own storage, website, logs, quotas and a server ID in the 404 Network.
The site is copied to an independent secondary host and IPFS, verified by checksum on a schedule, and rerouted when the primary fails.
┌──────────────┐
visitors ─▶│ /go/404-ID │ failover resolver
└──────┬───────┘
healthy ┌──┴──┐ primary down
▼ ▼
┌──────────┐ ┌──────────┐
│ PRIMARY │ │SECONDARY │ independent provider
└────┬─────┘ └────┬─────┘
└─────┬──────┘
▼
┌──────────────┐
│ IPFS (CID) │ content-addressed copy
└──────────────┘
every copy verified by sha256 on a scheduleWhat a "server" is here, precisely: each coin gets an isolated tenant environment on shared infrastructure — a separate storage namespace with quotas, a sandboxed website, its own health checks, replicas and logs. It is not a dedicated physical machine or VM.
Backups are tested, not just uploaded: the worker downloads each copy from where visitors would get it and compares its SHA-256 with the published version.
No hosting survives a complete global internet outage. 404 removes single points of failure in hosting; it does not promise the impossible.
> see live infrastructure status