Dedicated Nodes aka Custom Nodes
What are Dedicated Nodes?
Custom nodes aka Dedicated nodes operate by providing exclusive access to a blockchain network for individual users or organizations. Unlike shared nodes, which distribute resources among multiple users, dedicated nodes allocate all resources to a single user or entity. This ensures maximum control, reliability, and performance for the dedicated node operator.
Which nodes are available?
All 100+ nodes from the list on our website.
How to run a Dedicated Node?
Request a node on nownodes.io/dedicated-nodes and NOWNodes executes all the other steps.
Do you need a node that is not on the list?
Just drop us a message at [email protected] and let's keep in touch.
Dedicated Node VS Shared Node
Shared nodes offer practical solutions for businesses requiring greater throughput with limited resources, ideal for early-stage dApps. However, dedicated nodes provide top-notch performance, enhanced security, and complete control over transactions and data. They are the premium choice for high-performance dApps and projects demanding high reliability and scalability.
| Feature | Shared Nodes | Dedicated Nodes |
|---|---|---|
| Usage | For crypto businesses needing greater throughput with limited resources. | For high-performance dApps, large-scale crypto storage, or projects aiming to scale rapidly. |
| Access / Security | Shared among Crypto APIs customers with a low risk. | Exclusively yours, ensuring enhanced security and privacy. |
| Connection Stability | Stable connection with lower traffic than public nodes. | High-quality performance, hence the network stability. |
| Suitability | Suitable for early-stage dApps, providing easy access for stress-testing performance. | Can process unlimited requests per second, perfect for projects demanding high reliability and scalability. |
| Control over Transactions | Transactions and data are shared among multiple users. | Complete control over transactions and data, ensuring privacy and security. |
How to use credentials?
You need to put your credentials before domain name
Here's an example:
curl --location 'https://{login}:{password}@{domain_name}' \
--header 'Content-Type: application/json' \
--data '{
"jsonrpc": "2.0",
"method": "eth_blockNumber",
"params": [],
"id": 83
}'