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:
mainnetorsepolia). 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.
High-level architecture
Section titled “High-level architecture”Before diving into the details of self-hosting, it’s important to understand the high-level architecture of ENSNode. This will give you a better understanding of how the different components of ENSNode work together and what infrastructure requirements you may need to consider when self-hosting.
Next steps
Section titled “Next steps” ENSNode Operations Understand how to operate and manage ENSNode deployments.
ENSNode Deployment options Learn about different deployment options for self-hosting ENSNode, including Docker, Railway, and Terraform.