Dedicated 0G RPC Node & 0G RPC Endpoint | RedSwitches
// dedicated 0g rpc node

Private 0G RPC Endpoints on a Dedicated Node

A private 0G Chain RPC endpoint on single-tenant NVMe bare metal. Full, archive, or validator nodes serve standard EVM JSON-RPC over HTTP and WebSocket, with zero rate limits and no compute units.

Get a QuoteStart Live Chat
  • Private Endpoint, Zero Rate Limits
  • No Compute Units, Unlimited Requests
  • Full, Archive & Validator Builds
  • EVM JSON-RPC, Chain ID 16661
  • CometBFT Sub-Second Finality
  • 20+ Global Tier III Locations
deploy.shlive

$ rs deploy 0g --type full --region fra

allocating single-tenant bare metal

syncing 0gchaind (cometbft) consensus

starting reth evm execution

serving evm json-rpc (eth, net, web3)

attaching DDoS shield + IP allowlist

private endpoint live · https + wss

region Frankfurt · CometBFT + Reth · sub-second finality

  • UnlimitedRequests
  • ZeroRate Limits
  • 100%Isolation
// why redswitches

Why Teams Run 0G Nodes With RedSwitches

A single-tenant node with people behind it: unlimited throughput, a named account manager, direct engineering access, and billing built for Web3 teams.

Unlimited RPS & Responses

One node, unlimited requests and responses. No compute units, no rate caps, no overage bills. A flat monthly price, run as hard as the hardware allows.

Dedicated Account Manager

A named account manager who knows your setup, not a ticket queue. One contact for provisioning, scaling, and anything urgent.

Direct Engineering Access

Talk to the engineers who run the metal. 0gchaind consensus config, Reth or Geth EVM tuning, NVMe IOPS, and Symbiotic restaking setup, handled by people who run 0G nodes daily.

20+ Global Data Centers

Place your node beside your users across 20+ Tier III locations. Multi-region for redundancy, split read and write endpoints.

Pay In Crypto

Settle in crypto or fiat, 0G included. Flexible billing for Web3 teams, with the same predictable flat monthly price either way.

Tailored Load Balancing

Custom load balancing, failover, and split read/write topology, designed and tuned for your traffic by our engineers.

// request your endpoint

Configure Your 0G Node

Pick a node type, tell us your workload, and an engineer sizes and quotes it. One flat monthly price, no compute units, no overages.

1 Dedicated Node = Unlimited RequestsNo Compute Units$0 Overages, Guaranteed

0G Full Node

For dApps, wallets, AI agents & backend APIs

CPU
8–16 high-clock cores
RAM
64 GB+
Storage
1–2 TB NVMe (grows with chain state)
Network
100 Mbps+ on a 10/25 Gbps port
Stack
0gchaind (CometBFT) + Reth/Geth EVM, full root access
Best for
  • Wallet, dApp, and AI-agent read traffic
  • EVM JSON-RPC plus WebSocket subscriptions
  • Private https endpoint with IP allowlisting
Included with every node
  • Unlimited RPS, no rate limits
  • HTTPS & WebSocket (WSS)
  • 99.99% uptime SLA
  • Multi-region endpoints
  • Private networking + IP allowlisting
  • 24/7 Web3 engineering support
From$199/moflat, no compute units

Final price is sized to the node specs your chain needs (full vs archive, storage, region), and typically lands 30-40% below comparable RPC providers.

Node specs above are based on the official 0G documentation.

View official 0G node docs →

Inquiring about: 0G · Full Node

Replies in ~5 minA RedSwitches Web3 engineer specs your private endpoint

No compute units, no rate limits. From $199/mo, flat.

Prefer to talk it through first? Start Live Chat

// why dedicated

Stop Fighting For Bandwidth On Shared 0G RPC

Shared 0G RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated 0G node is your own private backbone: flat-priced, uncapped, and yours alone.

CapabilityShared RPC PoolRedSwitches Dedicated
Request limitsHard rate caps and compute-unit quotas throttle your 0G calls the moment traffic spikesZero rate limits, your 0G node serves unlimited requests up to what the hardware can push
ResourcesA noisy-neighbor pool where another tenant's mint or airdrop steals the throughput you paid for100% single-tenant CPU, RAM, and NVMe, reserved for your 0G workload alone
BillingPer-compute-unit metering with surprise overage bills at the end of the monthOne flat monthly price for the whole node, $0 overages and no usage math
NetworkShared, throttled bandwidth you can neither see nor controlA dedicated 10 / 25 Gbps port, metered or unmetered, that is yours alone
PrivacyA public, pooled endpoint with a wide, shared attack surfaceA private 0G endpoint behind included DDoS protection and IP allowlisting
History & specsLimited history and fixed plans you cannot resize as you growFull 0G archive with custom RAM and disk, sized to your query depth
ControlNo server access, the provider picks the client, version, and configFull root, KVM, and IPMI, run the 0G client and tuning you choose
// network details

0G Node Specifications

The chain IDs, clients, transports, and JSON-RPC namespaces your dedicated 0G node ships with. Built to a standard so your existing tooling connects with no changes.

Chain Parameters

Networks
Aristotle Mainnet, Galileo testnet
Chain IDs
Mainnet 16661 · Galileo testnet 16602
Native token
0G
Consensus
Optimized CometBFT (Tendermint BFT)
Finality
Sub-second
Throughput
11,000 TPS per shard
Execution
EVM-compatible (Reth recommended, Geth supported)
Modular stack
0G Chain + 0G Storage + 0G DA
Archive
Full historical EVM state
Explorer
chainscan.0g.ai

Supported Clients

Consensus client
  • 0gchaind (CometBFT)
Execution clients
  • Reth (recommended)
  • Geth

JSON-RPC Namespaces

  • eth_
  • net_
  • web3_
  • debug_
  • txpool_

You control which namespaces are exposed. Enable debug and trace on archive builds, keep the rest private behind IP allowlisting.

// use cases

What Teams Build On 0G Nodes

Where a private, uncapped endpoint beats a shared RPC pool.

Wallet App Traffic

Balances, transfers, token views, and contract reads all day. A dedicated 0G RPC node gives your wallet stack steadier reads than a shared public endpoint, with reserved CPU, RAM, and NVMe at peak.

Contract Release Flow

Teams shipping contracts through Hardhat or Foundry need a dependable path from staging to production. A private 0G node keeps deployment, verification, and post-release checks on infrastructure your team watches closely.

Live Event Streams

Some products subscribe rather than poll. WebSocket feeds for events, confirmations, and state changes stay stable when your endpoint is not competing with other tenants for the same shared capacity during bursts.

Historical Data Jobs

Backfills, old logs, replay tasks, and time-range analysis need more than current state. Archive-ready storage suits teams running analytics, audits, support cases, or features tied to past chain activity.

Indexing Data Pipelines

Dashboards, explorers, and alerting depend on steady ingestion. Dedicated 0G infrastructure fits when your pipeline reads continuously, enriches chain data, and feeds other systems that cannot tolerate erratic source behavior.

AI Agent Actions

0G positions itself as the chain for AI agents, so agent-led reads and writes are a core workload. Dedicated RPC gives agents consistent onchain access for state checks, triggers, and follow-up actions.

// how it works

From 0G To Private Endpoint In 3 Steps

Pick a node, we provision dedicated bare metal, you get a private, snapshot-ready RPC URL.

  1. 01

    Pick Your 0G Node

    Choose full, archive, or validator. RPC is the EVM execution layer (chain ID 16661); tell us your query depth and the region closest to your users.

  2. 02

    We Provision Bare Metal

    Your single-tenant 0gchaind plus Reth node deploys on NVMe, snapshot-synced, so you skip the long cold sync.

  3. 03

    Get Your Private Endpoint

    Receive a dedicated EVM JSON-RPC endpoint with unlimited requests and zero rate limits, private behind IP allowlisting and DDoS protection.

// latency & locations

Put Your Node Where Milliseconds Are Won

RPC latency is mostly a function of distance. A dedicated node lets you choose the exact region, so you sit next to the traffic that matters instead of fighting for routing on a shared, far-away endpoint.

Place It Where Your Users Are

Deploy across 20+ Tier III locations in the US, EU, Asia, and Australia. Put your 0G node in the region your traffic actually comes from, not wherever a shared pool happens to route you.

Cut The Round Trips

RPC latency is mostly physical distance. Running in the same region as your users and the 0G network's peers shaves the round-trips a far-away, shared endpoint can never give back, which is what high-frequency reads and transaction submission live or die on.

Multi-Region By Design

Run a primary node plus regional read replicas for fast reads everywhere and built-in redundancy. Split public read endpoints from private admin, debug, and trace endpoints.

Need a node within a target latency budget of a specific region or venue? Tell us the endpoint and we'll recommend the closest facility.

// supported chains

One Backbone For Every Major Chain

Run validators, RPC, and archive nodes across the chains your stack depends on, all on the same dedicated bare metal, with the same isolation, speed, and control.

// customer reviews

Trusted To Run Production Nodes

Real reviews from Trustpilot, HostAdvice, Cryptwerk, and Google.

  • 4.8/525Gbps Bare Metal
    Port speeds on cloud were capped and shady. With RS I actually get the 25Gbps they say. No throttle bs.
    Felix MartinsenDenmark
  • 5.0/5VPN Operations
    Network has been rock solid. They’ve got Tier 1 carriers like Arelion, GTT, and TATA… We just ping them on Telegram and they sort things out quickly.
    TomasNetherlands
  • 4.8/5Validators
    Set up multiple Solana + Avalanche validators through them. Hardware was clean, latency was low (especially in Europe), and uptime’s been 100% so far.
    Peppe TerranovaSouth Korea
  • 5.0/5Full Root Access
    As a sysadmin, I care more about control than flashy dashboards. RedSwitches gives me root access, IPMI, and actual hardware specs I can configure. Good for serious users.
    Eun-Woo GimSouth Korea
  • 5.0/5Enterprise Uptime
    We were searching for a truly reliable and stable hosting provider with maximum uptime and a powerful network infrastructure to ensure the lowest possible latency. RedSwitches not only met but exceeded our expectations.
    AppsLabGermany
  • 5.0/5Cloud Exit
    RedSwitches gave us full control over our infrastructure without the vendor lock-in we kept running into with cloud hosts. Customizable builds, fast provisioning, and actual humans handling support tickets. It’s refreshing.
    Princeton OttUnited States
  • 5.0/599.99% Uptime
    My website works smoothly, thanks to their 99.99% uptime guarantee. The support team is another plus for me, as I always have been able to get help whenever I needed it in just 5 minutes on average.
  • 5.0/5ETH & BTC Nodes
    Deployed a few Ethereum and Bitcoin nodes here. Uptime’s been flawless, and sync speed was great thanks to their storage config.
    Ervin KaruGermany
  • 5.0/510Gbps RPC
    They provide what they promise, I got no throttling while running my RPC Nodes. I got server in a Amsterdam for the best price.
    Atri MukherjeeIndia
  • 5.0/5Streaming
    I am using their 10gbps streaming server for last 6 months and I have no complaints. Extremely quick live chat support and I love that they accept crypto.
    Tarun GhoshIndia
  • 5.0/5Bare Metal
    A really great hosting provider - what stands out the most is the stability of the network connection and the wide selection of bare metal servers. We’re very satisfied, and RedSwitches covers all of our needs.
    Борис ВербицкийPoland
  • 5.0/5AI Workloads
    Pros: Extremely reliable hardware, low-latency network, transparent billing… Great choice if you need raw power without cloud complexity. Works well for our dev environment and some AI workloads.
    Henry HarrisonUnited States
  • 5.0/5Switched Provider
    I have worked with OVH and Contabo in the past, but RedSwitches hit a better balance of price vs. support. Not the cheapest, but I get better performance and faster help.
    Samual SuttonUnited Kingdom
  • 5.0/5Game Servers
    Been using RedSwitches for 6 months now for my small game server biz. Uptime has been great, and I haven’t run into any hidden charges.
    Jerold PerkinsUnited States
  • 5.0/5AI Storage
    Using the storage servers to archive logs and snapshots from our AI pipeline… I also love that I could pick the datacenter closest to our team.
    Eino KoppelEstonia
  • 4.8/5Support
    Support is super responsive. I had an issue with an OS reinstall and they jumped in within 10 minutes… Transparent pricing = win.
    Boniface LeandreUnited States
  • 5.0/5Instant Delivery
    They have an instant delivery section… they delivered it within 120 mins with all my requirements fulfilled (OS/RAID/Software configured etc).
    Daniel StuartSri Lanka
  • 5.0/5Fast Provisioning
    A dedicated server has been installed within 30 minutes. Thirty minutes. It takes DAYS for some famous providers out there, but these guys do their work right.
    Ярослав СавенковNetherlands
  • 5.0/55+ Years
    I have been using their services for over 5+ years… Uptime: 10/10, Network: 10/10, Hardware Quality: 10/10, Customer Support: 20/10 (No, That’s Not A Typo).
  • 5.0/51 to 14 Servers
    They offer top quality hardware, excellent uptime and very responsive support… They helped us scale our business exponentially and we went from 1 server to 14 dedicated servers in less than a year.
    Sandip PanditIndia
  • 5.0/5Reliability
    Great hardware, non congested network and excellent service. Already using them for over a year and would definitely recommend Redswitches if you are looking for a reliable hosting provider.
    CandiceUnited States
  • 4.8/5Global Locations
    With servers available in numerous strategic locations, RedSwitches offers exceptional versatility and performance for our company’s diverse hosting needs. Plus, their no setup fee policy really helps keep costs down.
    Tiberiu RomanUnited States
  • 5.0/5Exam Platform
    "Your server is ready" - I read this message within 30 mins of starting the chat with their Sales Team… Excellent DELL Hardware and 100% Uptime.
    Mridul MehtaIndia
  • 5.0/5Bare Metal Cloud
    The dedicated server I got from RedSwitches has been incredibly reliable and fast. Their bare metal cloud solutions offer excellent performance, and the cloud VPS options are perfect for scaling. Highly recommended!
  • 5.0/5Zero Downtime
    I have been using their dedicated server from 9 months now. Starting from pre-sales till today I have not experienced downtime or lack of support.
    Amit BhatiaIndia
  • 5.0/524/7 Support
    First of all, all services work as expected - secondly - support is outstanding, no matter when you start the conversation with colleagues at support they have knowledge to help you out.
    LukaSlovenia
  • 5.0/5Since 2021
    We have been using Red Switches for several years since 2021. I have never experienced such fast customer service.
    Eitan WaisgerberIsrael
  • 5.0/5Easy Onboarding
    Absolutely delighted with RedSwitches! The setup was quick and free, and the fact that they accept all major payment gateways made the process seamless.
    Birk SpillumNorway
  • 5.0/5Bare Metal
    Very good experience using their bare metal servers. Their customer service is one of the finest I have experienced - always prompt at resolving troubles. Highly recommend.
// faqs

Frequently Asked Questions

Chain IDs, clients, archive data, getLogs limits, and why dedicated beats compute-unit billing.

What is a 0G RPC node?

A 0G RPC node is the endpoint your app calls to read chain state, send transactions, and watch onchain activity on 0G. It is the part of your stack that wallets, dApps, bots, and backends depend on every day. We position our service as dedicated 0G RPC infrastructure on single-tenant hardware, not a shared public gateway. 0G's Aristotle mainnet uses chain ID 16661, and the official docs list evmrpc.0g.ai as the public EVM RPC.

What is the difference between a public 0G RPC endpoint and a dedicated 0G RPC node?

A public endpoint is shared, so your traffic competes with everyone else using that service. A dedicated 0G RPC node gives you hardware reserved for your workload, so CPU, RAM, and NVMe are not being pulled by unrelated tenants. That matters once your traffic grows, your reads need to stay predictable, or your team wants its own upgrade and recovery path. 0G also recommends adding third-party RPCs for production redundancy, which tells you one public endpoint should not be your whole plan.

Does a dedicated 0G RPC node support both HTTP and WebSocket connections?

Yes. 0G Chain is EVM-compatible, so teams can keep using familiar Ethereum-style tooling and JSON-RPC call patterns. It supports standard JSON-RPC access and WebSocket subscriptions, which makes a dedicated node useful for both request-response traffic and live event streams. We size the box around that real split, not around a narrow reads-only view of RPC.

Do I need a full node or an archive node for my 0G application?

Most teams start with a full node. That fits normal production reads, transaction sends, wallet backends, and contract calls. Archive becomes the better choice when you need deep historical state, long-range logs, backfills, support investigations, or analytics tied to old chain activity. 0G's node docs separate archival nodes from other roles for exactly that reason. We usually scope this around your query depth, not just your budget.

What hardware should I choose for production 0G RPC traffic?

We use 0G's published node requirements as the floor, then size above that for real traffic. The 0G node docs list 64 GB RAM, 8 cores, 1 TB NVMe SSD, and 100 MBps for mainnet nodes, while archival guidance keeps 64 GB RAM and 8 cores but calls for large NVMe SSD for full history. On our side, we can provision up to 128 dedicated cores, up to 2 TB RAM, enterprise NVMe, and 10 Gbps or 25 Gbps uplinks, so we can fit a simple private RPC, an archive-heavy build, or a bigger multi-service setup.

Can I keep my 0G RPC endpoint private and restrict who accesses it?

Yes, and in many cases that is the better production design. We can keep the RPC private behind firewall rules, IP allowlists, and strict port exposure so only your app servers, partners, or internal services can reach it. If you need finer traffic control, you can add a reverse proxy in front for method filtering or internal throttling. That works well for partner apps, internal backends, staging, and customer-specific access paths.

How should I plan redundancy for production 0G apps?

We would not plan production around one endpoint alone. 0G's own mainnet docs recommend multiple RPC providers for redundancy. Our usual pattern is a dedicated primary node for your steady traffic, then a secondary path in another region for failover. If your workload is heavier, we also split public reads from indexers, backfills, and internal services so one noisy job does not drag the whole stack.

What is the difference between running a 0G RPC node and running a validator?

A dedicated 0G RPC node serves application traffic. A validator does that, plus participates in consensus and staking-related validator operations. On 0G, validator setup has extra requirements that non-validator nodes do not have: the validator guide calls for restaking-related configuration and an Ethereum RPC for Symbiotic, while non-validator nodes do not need those restaking flags. So if your goal is private app access, you do not need to jump straight into validator complexity.

Do you charge per request or per compute unit?

No. Unlike shared RPC providers that bill per "compute unit" and throttle you past a quota, a dedicated node is a flat monthly price with unlimited requests and zero overages. One node equals all the throughput your hardware can serve. That makes budgeting predictable and removes the surprise bills that come with usage-based RPC pricing.

How is this different from a shared RPC endpoint?

Shared RPC pools serve thousands of customers from pooled infrastructure, so you inherit rate limits, noisy-neighbor latency, and compute-unit billing. A RedSwitches node runs on single-tenant bare metal that is yours alone: reserved CPU, RAM, and NVMe, a dedicated 10/25 Gbps port, and a private endpoint you control. Performance tracks your hardware, not another tenant's traffic.

Do I have to sync the node myself, or wait days for it?

No. We provision from current snapshots so your node is live in hours rather than syncing from genesis for days. You can run it yourself with full root access, or choose our fully managed option where our engineers handle the sync, updates, and monitoring. Either way you receive a working private endpoint, not an empty server.

Can I deploy close to a specific region or sequencer?

Yes. With 20+ Tier III locations across the US, EU, Asia, and Australia you can place your node in the same region as your users or a chain's sequencer to cut round-trip latency. Tell us your target region and we will recommend the closest facility. You can also run multi-region nodes for redundancy and split read and write endpoints.

// developer resources

0G Developer Resources

Official 0G resources for builders running a node: docs, explorers, source, network status, and faucets. Every link points at the first-party source, not a wrapper.

// launch your node

Launch Your Private 0G Node

From $199/mo flat, sized to your chain's node specs and typically 30-40% below other providers. Snapshot-ready provisioning, zero setup fees, 24/7 Web3 engineers, no compute units, no rate limits.

Get a QuoteStart Live Chat