Self-host ENSNode

Self-hosting provides extra benefits compared to using one of the publicly Hosted Instances. Having your own ENSNode instance allows you to:

• Select ENS Namespace: choose which ENS protocol deployment ENSNode will provide data for (ex: mainnet or sepolia). Great for testing and development.
• Select ENSNode Plugins: activate only the plugins you need for your use cases, reducing resource usage and improving performance.
• Tailor “name healing” coverage: apply a label set that fits your needs for ENSRainbow to perform “name healing”.
• Index ENS data the way you want: customize indexing logic and indexed data model stored in your own ENSDb instance by implementing an ENSDb Writer.
• Build custom APIs and data pipelines: implement an ENSDb Reader to build apps using your own ENSDb instance as a source of truth for ENS live data.
• Control versioning and updates: choose when to update your ENSNode instance to new versions, giving you control over when to adopt new features or breaking changes.
• Manage uptime: apply strategies for ensuring high availability and uptime guarantees.

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 will make it cheap and easy to begin working with indexed ENS data.

Cut your RPC bill

Skip the historical RPC fanout entirely. Pull down a published ENSDb snapshot instead of replaying 9+ years of ENS history through your own RPC provider - saving real money on every bootstrap, every CI run, every fresh environment.

Spin up in minutes, not days

Skip the long historical backfill too. A nearly up-to-date ENS index is ready as fast as you can download it - no specially configured Postgres required, no days of waiting. Perfect for hackathons, demos, prototypes, and any other time you need a fresh ENSDb fast.

Repeatable CI environments

Use snapshots as deterministic fixtures for tests and CI pipelines. Every run starts from the same well-known ENS state, with zero RPC dependency.

Confident release reviews

Diff snapshots across ENSNode versions to catch unexpected changes in indexed data - a powerful way to validate indexing-logic refactors before a release ships.

Easier self-hosting

Bootstrap your own ENSNode instance from a recent snapshot, then catch up to realtime from there. Less time waiting, more time building.

ensdb-cli: purpose-built ops tooling

`ensdb-cli` surfaces the operations you actually need day-to-day: inspect indexer instances, manage snapshots, clean up unused schemas, and more.

More about ENSDb Snapshots and ensdb-cli Roadmap for ENSDb Snapshots and ensdb-cli

Massive scalability

Learn about ENSNode scalability Architecture overview of how to scale ENSNode to handle a massive volume of requests.

Deployment options

Deploy with Docker The Docker deployment option provides the easiest way to run the full ENSNode suite of services both locally and in the cloud.

Deploy 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.