Running a peaq validator requires a robust and reliable Virtual Private Server (VPS) or dedicated server to ensure optimal performance and uptime. You can also opt for a managed node provider like OnFinality to reduce operational overhead. This guide will help you choose a suitable provider, with examples from AWS, DigitalOcean, Linode (Akamai), and OnFinality. The recommended hardware specifications provided by the peaq engineering team serve as a baseline for reliable results.

​
Prerequisites

  • Basic familiarity with setting up virtual servers.
  • Aim to run a peaq validator node using the recommended hardware.
  • Your goal is to balance performance, cost-efficiency, and reliability when selecting a VPS provider.
  • You are running Ubuntu 20.04 as your operating system.
  • OS: Ubuntu 20.04
  • CPU: 3.3 GHz AMD EPYC 7002
  • Storage: 1TB SSD
  • Memory: 8GB RAM
The above specifications have been tested and proven by peaq’s engineering team to produce reliable results over time. While these are recommended, you can experiment with other configurations to optimize for cost and performance.

​
Managed Node Provider (OnFinality)

If you prefer a managed experience, OnFinality offers dedicated collator (validator) nodes for peaq. This approach removes most server administration while providing fast sync and production-grade monitoring.

​
Why OnFinality

  • Managed provisioning, monitoring, and scaling for peaq nodes
  • Dedicated nodes with “Lightning Restore” for fast sync
  • Built-in secure API endpoints (HTTP/WebSocket)
  • Clear operational guidance for collator setup

​
Quick start with OnFinality

  1. Create an account and deploy a Dedicated Node for peaq (Collator Node Type).
  2. Use the recommended image version and region; ensure resources meet peaq’s baseline specs.
  3. During on-chain configuration, set --rpc-methods=unsafe (temporarily) and enable external RPC if needed. After setup, switch back to --rpc-methods=safe and disable unsafe external RPC.
  4. Generate session keys via author_rotateKeys (UI or RPC), then set them on-chain (session.setKeys).
  5. Stake the minimum required amount and join the validator candidate pool.
Refer to the step-by-step guide for details: How to Set Up a Validator for peaq on OnFinality.

​
Instructions for Choosing a VPS Provider

Ensure the chosen VPS provider offers a machine with:
  • High-performance CPU (preferably AMD EPYC 7002 or equivalent)
  • Ample SSD storage (1TB or more)
  • Adequate RAM (8GB or more)

​
2. Compare VPS Providers

If you’re managing your own infrastructure, the following VPS providers are commonly used. Otherwise, see the managed option above for OnFinality.

​
Amazon Web Services (AWS)

  • Instance Recommendation: c5ad.xlarge
  • Specs:
    • 4 vCPUs (AMD EPYC)
    • 8GB RAM
    • Up to 10 Gbps network bandwidth
    • Elastic Block Storage (EBS) for SSD storage
  • Why AWS:
    • High availability and reliability
    • Flexible scaling options
    • Extensive documentation and support
  • Considerations:
    • Pricing can be higher compared to other providers.

​
DigitalOcean

  • Instance Recommendation: Premium AMD CPU Droplet (e.g., CPU-Optimized 8GB)
  • Specs:
    • 4 vCPUs
    • 8GB RAM
    • 160GB SSD local storage (option to scale to 1TB via storage volumes)
  • Why DigitalOcean:
    • Simplicity in UX for setup and management
    • Competitive pricing
    • Integrated monitoring tools
  • Considerations:
    • Limited to specific regions for Premium CPUs.

​
Linode (Akamai)

  • Instance Recommendation: Dedicated CPU Plan (e.g., Dedicated 8GB)
  • Specs:
    • 4 Dedicated vCPUs
    • 8GB RAM
    • 160GB SSD (scale up with storage volumes)
  • Why Linode:
    • Affordable pricing
    • Strong performance for dedicated resources
    • User-friendly interface / UX
  • Considerations:
    • Storage upgrades may require additional configurations.

​
OnFinality (Managed Provider)

  • Offering: Dedicated collator (validator) nodes for peaq
  • Why OnFinality:
    • Managed node lifecycle (deploy, monitor, scale) with rapid sync
    • Secure RPC endpoints and operational best practices
    • Reduces complexity vs self-managing VPS
  • Considerations:

​
3. Cost and Regional Availability

  • Compare the monthly pricing for the recommended instances from AWS, DigitalOcean, and Linode.
  • Check for regional availability to ensure low latency, especially if you are running a collator in a specific geographic location.

​
4. Additional Factors to Consider

  • Network Performance: Ensure the VPS offers sufficient bandwidth and low latency.
  • Support and SLAs: Check if the provider offers technical support and Service Level Agreements (SLAs) for uptime.
  • Scalability: Choose a provider that allows easy scaling of resources in case your node requires higher specs.
  • Backup and Recovery: Opt for providers that offer automated backups and disaster recovery solutions.

​
Summary

ProviderRecommended PlanSpecsPricing Notes
AWSc5ad.xlarge4 vCPUs, 8GB RAM, 1TB SSDHigher cost, high reliability
DigitalOceanCPU-Optimized 8GB4 vCPUs, 8GB RAM, scalable SSDModerate cost, easy to use
LinodeDedicated 8GB4 vCPUs, 8GB RAM, scalable SSDAffordable, solid performance
OnFinalityManaged Dedicated NodeManaged collator with fast sync, secure RPCManaged service (usage-based), minimal ops
By following this guide, you can choose a VPS provider that aligns with your technical requirements and budget to reliably run your peaq validator node. While AWS, DigitalOcean, and Linode are excellent options, the final choice depends on your specific needs and preferences. If you want to minimize operational overhead, consider the managed route with OnFinality and follow their peaq validator guide: How to Set Up a Validator for peaq on OnFinality.