Ethereum infrastructure that runs on the node, not next to it.
blazed.sh · Docs · Live demo · RPC reference
We run fully-synced Ethereum mainnet nodes, and we let you deploy Docker containers and Node.js scripts directly onto the same hosts. Your code reaches the chain over a local Unix socket rather than the public internet, which removes the network round-trip that dominates remote RPC latency, along with the shared rate limits that come with it.
// Injected into every container and script. No endpoint to pick, no API key to rotate.
const provider = new ethers.WebSocketProvider("ws://eth:8545");
const head = await provider.getBlock("latest");That is the whole idea: sub-10ms round-trips because there is no network in the path, and a direct mempool view served by the node your process is sitting on. Ethereum mainnet is the only network live today.
Three container templates, one per runtime. Each ships a Dockerfile, a working example that
subscribes to new blocks over the injected socket, and an Actions pipeline that builds a
multi-arch image and pushes it to GHCR on every commit to main. Press Use this template,
push once, then point a container at the image it publishes.
| Template | Stack |
|---|---|
| template-js | Bun and TypeScript with ethers.js v6 |
| template-go | Go with go-ethereum |
| template-python | Python with web3.py |
eth-explorer is a self-hosted block, transaction and contract explorer that needs nothing but an RPC connection. Single static binary with the frontend embedded, SQLite for storage, live mempool over WebSocket. It is the same code behind explorer.blazed.sh, and it runs against your own node just as happily as ours.
rpc-rproxy is the JSON-RPC reverse proxy we built to make the above work: on-the-fly request parsing, Unix domain socket support, and little enough overhead that it does not undo the point of being co-located.
The rest is smaller. snap-peek reads blocks and transactions straight out of Erigon snap-sync torrents, blazed.sh is the command-line client, and nodejs_runner is the runtime behind script deployments.
If you would rather not build an image at all, the scripts editor at panel.blazed.sh runs Node.js against the same socket with ethers.js and web3.js already installed.