ENSNode Deployment Options

ENSNode can be deployed in several ways. If you are just getting started, use the Docker Compose path below. It requires the least setup and works locally or on any server that can run containers.

Choose a deployment option

Option	Best for	Effort	Cost control	Notes
Docker	Local development, single-machine self-host, or custom cloud servers	Low	High	Runs the full ENSNode stack with docker compose
Railway	One-click managed cloud deployment from a template	Very low	Medium	Deployed via the Railway Template
Terraform	Render-based production-grade deployment used internally by NameHash Labs	High	Medium	Reference config; currently tailored for NameHash Labs deployments

Recommended starting point

Start with Docker. It runs the full ENSNode suite on a single machine and is the fastest way to validate your namespace, plugins, and RPC configuration before moving to managed infrastructure.

Next steps

Deploy with Docker Run the full ENSNode suite locally or on a server with Docker Compose.

Deploy to Railway Deploy the ENSNode Alpha instance on Railway using the Railway Template.

Deploy with Terraform Deploy ENSNode on Render with Terraform and AWS-managed DNS.