Cut your RPC bill
Self-host ENSNode
This page will help you decide whether to self-host ENSNode or use the hosted instances. Includes architecture overview of the ENSNode stack (ENSIndexer, ENSDb, ENSRainbow, ENSApi).
Follow these guides to deploy an ENSNode instance to the cloud.
Running your own ENSNode instance is helpful for those that wish to:
- Maintain control over their own infrastructure
- Ensure control over their own availability and uptime guarantees
- Customize ENSNode’s behavior
- Own the resulting Postgres index for custom queries or
JOINs
Note that because ENSNode makes many label healing requests to ENSRainbow while indexing, it’s imperative that they be on the same local network to minimize request time.
Bootstrap from a snapshot (coming soon)
Section titled “Bootstrap from a snapshot (coming soon)”Self-hosting today means standing up a fresh ENSNode instance from zero and waiting on an initial backfill - including the RPC bill that comes with it. ENSDb snapshots and ensdb-cli flatten that ramp.
The headline value props for self-hosters:
Spin up in minutes, not days
Repeatable CI environments
Confident release reviews
Easier self-hosting
ensdb-cli: purpose-built ops tooling
Deploying with Docker
Section titled “Deploying with Docker”The Docker deployment option provides the easiest way to run the full ENSNode suite of services both locally and in the cloud.
Deploying with Terraform
Section titled “Deploying with Terraform”An example Terraform deployment reference is available, showing an example of deploying the full ENSNode suite on Render with AWS managed domain names.