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 japan open chain rpc node
Private Japan Open Chain RPC Endpoints on a Dedicated Node
A private Japan Open Chain RPC endpoint on single-tenant NVMe bare metal. Full or archive nodes serving standard Ethereum JSON-RPC over HTTP and WebSocket, with zero rate limits and no compute units.
- Private Endpoint, Zero Rate Limits
- No Compute Units, Unlimited Requests
- Full & Archive Builds
- Go-Ethereum Stack, Full Root Access
- Standard Ethereum JSON-RPC, HTTP & WSS
- 20+ Global Tier III Locations
deploy.shlive
$ rs deploy japanopenchain --type full --region fra
allocating single-tenant bare metal
syncing go-ethereum (joc) client
verifying clique poa peers
serving eth json-rpc over https + wss
attaching DDoS shield + IP allowlist
private endpoint live · https + wss
- UnlimitedRequests
- ZeroRate Limits
- 100%Isolation
// why redswitches
Why Teams Run Japan Open Chain 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.
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. Go-Ethereum (Clique PoA) config, Geth archive tuning, and standard eth JSON-RPC namespaces, handled by people who run Japan Open Chain 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, JOC 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 Japan Open Chain 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
Japan Open Chain Full Node
For wallets, dApps, payments & backend APIs
- CPU
- 12–16 high-clock cores
- RAM
- 64 GB (DDR4 / DDR5)
- Storage
- 2–4 TB NVMe
- Network
- 10/25 Gbps uplink, metered or unmetered
- Stack
- Go-Ethereum (Geth) JOC client (EVM L1, chain ID 81)
Best for
- Wallet reads, balances, and transaction broadcast
- Stablecoin payment and settlement flows
- Private JSON-RPC over HTTP and WebSocket
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 Japan Open Chain documentation.
View official Japan Open Chain node docs →Japan Open Chain Archive Node
For explorers, indexers & deep history
- CPU
- 16+ high-clock cores
- RAM
- 64–128 GB (DDR4 / DDR5)
- Storage
- 4 TB+ NVMe (full history, no pruning)
- Network
- 10/25 Gbps uplink, unmetered for backfills
- Stack
- Go-Ethereum (Geth) JOC client with archive history
Best for
- Explorer and analytics backfills
- Older-block eth_call and historical state
- Compliance and audit query workflows
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 Japan Open Chain documentation.
View official Japan Open Chain node docs →Request Sent
Thanks. A Web3 engineer will spec your private endpoint and reach out shortly.
Something went wrong. Please try again or email sales@redswitches.com.
// why dedicated
Stop Fighting For Bandwidth On Shared Japan Open Chain RPC
Shared Japan Open Chain RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated Japan Open Chain 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 Japan Open Chain calls the moment traffic spikesZero rate limits, your Japan Open Chain 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 Japan Open Chain 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 Japan Open Chain endpoint behind included DDoS protection and IP allowlisting
History & specsLimited history and fixed plans you cannot resize as you growFull Japan Open Chain 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 Japan Open Chain client and tuning you choose
// network details
Japan Open Chain Node Specifications
The chain IDs, clients, transports, and JSON-RPC namespaces your dedicated Japan Open Chain node ships with. Built to a standard so your existing tooling connects with no changes.
Chain Parameters
- Networks
- Mainnet, Testnet
- Chain IDs
- Mainnet 81 · Testnet 10081
- Native token
- JOC
- Consensus
- Clique Proof of Authority
- Validators
- Permissioned · vetted Japanese enterprises
- Finality
- ~5 seconds (deterministic)
- Execution
- EVM (go-ethereum / Geth based)
- Archive
- Full historical state
- Explorer
- explorer.japanopenchain.org
Supported Clients
Node software
- go-ethereum (Geth) JOC build
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 Japan Open Chain Nodes
Where a private, uncapped endpoint beats a shared RPC pool.
Stablecoin Payment Rails
Run payment flows that need fast balance checks, transaction broadcast, and settlement visibility. JOC promotes stablecoin issuance with financial institutions, so a dedicated node keeps those reads and writes steady under load.
Merchant Settlement Ops
Drive merchant settlement workflows where your backend watches balances, triggers payment logic, and reconciles transfers across wallets. A dedicated JOC node gives business payment systems private chain access and cleaner operational control.
Wallet State Reads
Power wallet backends that fetch balances, token holdings, nonce data, and transaction status with predictable read capacity, fewer retry loops, and clean account views when shared endpoints throttle during busy periods.
Exchange Deposit Monitoring
Track incoming deposits, confirmation states, and withdrawal activity through private JOC RPC access. Dedicated infrastructure helps when your exchange or treasury system cannot risk crowded public endpoints during high-volume monitoring windows.
Explorer Data Pipelines
Feed block explorers, internal dashboards, and analytics stacks that pull chain data on a fixed schedule. JOC supports standard Ethereum JSON-RPC, so you reuse the indexing and query tooling many EVM teams already run.
Enterprise App Backends
Support production dApps that need private reads, contract calls, and predictable chain access behind customer-facing products. JOC targets business and finance apps, enterprise NFT projects, and practical Web3 services that demand isolated infrastructure.
// how it works
From Japan Open Chain To Private Endpoint In 3 Steps
Pick a node, we provision dedicated bare metal, you get a private, snapshot-ready RPC URL.
- 01
Pick Your Japan Open Chain Node
Choose a full node for live reads and writes or an archive node for deep history. JOC speaks standard Ethereum JSON-RPC; tell us the region closest to your users.
- 02
We Provision Bare Metal
Your single-tenant go-ethereum (Geth) JOC node deploys on NVMe and syncs to chain tip, so you skip the long cold sync from genesis.
- 03
Get Your Private Endpoint
Receive a dedicated Ethereum 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 Japan Open Chain 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 Japan Open Chain 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.
Ethereum
Solana
Polygon PoS
BNB Chain
Avalanche
Cardano
Cosmos
NEAR
Sui
Aptos
TRON
Polkadot
Kusama
Algorand
Tezos
TON
Fantom
XRP Ledger
Hedera
0G
Berachain
Celestia
Flare
Flow
Gnosis Chain
Hyperliquid
Injective
Japan Open Chain
Kaia
Monad
Nomina
Osmosis
peaq
Plasma
Ronin
Sahara AI
Sei
Sonic
Stellar
Story
Vana
Cronos
ZetaChain
XDC Network
PulseChain
Filecoin
IoTeX
Chiliz
Viction
Tempo
Stable
SORA
Waves
Moonbeam
Moonriver
Moonbase Alpha
Astar
Shiden
Aleph Zero EVM
Darwinia
Manta Atlantic
Acala
Karura
Bifrost
Hydration
Basilisk
Centrifuge
Interlay
Phala
Aleph Zero
Bittensor
Enjin
Nodle
Frequency
Humanode
Crust Network
Robonomics
Integritee
NeuroWeb
Tangle
Mythos
Pendulum
Amplitude
Aventus
Acurast
Energy Web X
Heima
Krest
Liberland
BalanceAI
Zeitgeist
xx network
Hyperbridge
Polkadot Asset Hub
Polkadot Bridge Hub
Polkadot Collectives
Polkadot Coretime
Kusama People
Polkadot People
Westend People
Paseo
Arbitrum
Base
Optimism
Polygon zkEVM
Linea
Scroll
zkSync Era
Starknet
Abstract
Arbitrum Nova
B3
Blast
Celo
Cyber
Fluent
Fraxtal
Fuel
Gravity
Hemi
Immutable zkEVM
Ink
Lens
Lisk
Mantle
Mode
Morph
Movement
Soneium
Sophon
Stacks
Taiko
Unichain
World Chain
Xai
Zora
opBNB
Manta Pacific
Boba Network
MegaETH
Bitcoin
Dogecoin
Litecoin
// customer reviews
Trusted To Run Production Nodes
Real reviews from Trustpilot, HostAdvice, Cryptwerk, and Google.
- 25Gbps Bare Metal
Port speeds on cloud were capped and shady. With RS I actually get the 25Gbps they say. No throttle bs.
- VPN 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.
- Validators
Set up multiple Solana + Avalanche validators through them. Hardware was clean, latency was low (especially in Europe), and uptime’s been 100% so far.
- Full 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.
- Enterprise 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.
- Cloud 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.
- 99.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.
- ETH & BTC Nodes
Deployed a few Ethereum and Bitcoin nodes here. Uptime’s been flawless, and sync speed was great thanks to their storage config.
- 10Gbps 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.
- Streaming
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.
- Bare 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.
- AI 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.
- Switched 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.
- Game 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.
- AI 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.
- Support
Support is super responsive. I had an issue with an OS reinstall and they jumped in within 10 minutes… Transparent pricing = win.
- Instant Delivery
They have an instant delivery section… they delivered it within 120 mins with all my requirements fulfilled (OS/RAID/Software configured etc).
- Fast 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.
- 5+ 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).
- 1 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.
- Reliability
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.
- Global 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.
- Exam 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.
- Bare 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!
- Zero 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.
- 24/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.
- Since 2021
We have been using Red Switches for several years since 2021. I have never experienced such fast customer service.
- Easy 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.
- Bare 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 Dedicated JOC RPC Node?
A Dedicated JOC RPC Node is a private Japan Open Chain node that runs on single-tenant server hardware instead of a shared public endpoint. We use dedicated infrastructure so your app, wallet, indexer, or backend gets its own CPU, RAM, storage, and network lane. That matters on JOC because the official public RPC endpoints are listed for non-commercial use, and JOC itself tells production users to run their own node or use a provider.
How is a dedicated JOC RPC node different from a shared RPC endpoint?
The difference is control, isolation, and more predictable throughput. With a shared endpoint, your traffic sits in a multi-tenant pool and performance can change when other users spike demand. With our JOC RPC Node setup, the hardware is yours, so you avoid shared throttling, keep full root access, and tune the node around your own workload through root, KVM, and IPMI.
Can I run a JOC validator node?
Not in the public staking sense. Japan Open Chain is an Ethereum-compatible Layer 1 whose validators are permissioned, operated by known, approved companies rather than an open stake-to-earn role like Ethereum or Solana. What we provision is what apps and indexers actually need: a fast, dedicated full or archive RPC node running the Geth-based JOC stack, with full history available for deep lookups and analytics.
What is the JOC mainnet chain ID and RPC URL format?
The official JOC mainnet chain ID is 81. JOC's quick-start and chain-spec pages list mainnet RPC URLs in the format https://rpc-1.japanopenchain.org:8545, with additional official endpoints also shown in the docs. For production use, we do not advise building around those public URLs. JOC states that its public endpoints are for non-commercial use and may change without notice, so we provision your own JOC RPC Node on dedicated infrastructure.
How much CPU, RAM, and NVMe storage should I start with for JOC RPC?
For most production teams, we would start a Dedicated JOC RPC Node at roughly 12 to 16 high-clock cores, 64GB RAM, and 2 to 4TB NVMe. That is not a fake official JOC minimum. It is our engineering starting point based on JOC running on Geth and current Geth storage guidance. Geth's own docs say disk is usually the main bottleneck and recommend high-performance SSD storage. If you expect heavy backfills or deep history, we size above that.
How long does a JOC node take to deploy and sync?
Server delivery and node readiness are different. The server can be provisioned first, but a usable JOC RPC Node still depends on sync time. We do not want to promise live in minutes when chain sync is the real variable. JOC's official node guide shows a Geth-based setup with install, init, and sync steps. In plain terms, we provision the server first, then bring the node online according to current sync conditions and the spec you choose.
Can I use a Dedicated JOC RPC Node for wallets, dApps, exchanges, and backend APIs?
Yes. That is exactly where this setup makes sense. A Dedicated JOC RPC Node can serve wallet reads, transaction broadcast, exchange deposit monitoring, event listeners, internal APIs, explorer-style workloads, and business backends. JOC is positioned as a public Ethereum-compatible Layer 1 suited to business and finance use cases, and our dedicated RPC servers are built around production workloads.
What is the difference between managed and unmanaged JOC node operations?
With unmanaged service, we give you the dedicated hardware foundation, root access, DDoS protection, and remote management access, while your team handles OS updates, client changes, hardening, monitoring, backups, and day-to-day operations. With managed service, we take on more of that operational work, including OS installation, updates, baseline hardening, monitoring, patching, and incident help within scope. Both paths run the same Dedicated JOC RPC Node hardware.
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
Japan Open Chain Developer Resources
Official Japan Open Chain 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 Japan Open Chain 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.