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 filecoin rpc node
Private Filecoin RPC Endpoints on a Dedicated Node
A private Filecoin RPC endpoint on single-tenant NVMe bare metal. Full or archive nodes serving both the native Filecoin JSON-RPC and the Ethereum JSON-RPC over FEVM, with zero rate limits and no compute units.
- Private Endpoint, Zero Rate Limits
- No Compute Units, Unlimited Requests
- Full & Archive Builds
- Filecoin & Ethereum (FEVM) JSON-RPC
- Lotus & Forest Clients
- 20+ Global Tier III Locations
deploy.shlive
$ rs deploy filecoin --type full --region fra
allocating single-tenant bare metal
restoring lightweight chain snapshot
syncing lotus to finalized head
enabling filecoin + eth json-rpc (fevm)
attaching DDoS shield + IP allowlist
private endpoint live · filecoin + eth json-rpc
- UnlimitedRequests
- ZeroRate Limits
- 100%Isolation
// why redswitches
Why Teams Run Filecoin 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. Lotus vs Forest client choice, FEVM eth_ RPC enablement, chain snapshot restore, and NVMe tuning, handled by people who run Filecoin 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, FIL 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 Filecoin 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
Filecoin Full Node
For dApps, wallets, bots & backend APIs
- CPU
- 8–16 high-clock cores
- RAM
- 32–64 GB
- Storage
- 2 TB+ local NVMe (snapshot-pruned chain, grows)
- Network
- 1 Gbps+ on a 10/25 Gbps port
- Clients
- Lotus or Forest · Filecoin + Ethereum (FEVM) JSON-RPC
Best for
- Filecoin JSON-RPC reads and message broadcast
- FEVM eth_ calls for Solidity tooling and wallets
- HTTP and WebSocket for production app backends
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 Filecoin documentation.
View official Filecoin node docs →Filecoin Archive Node
For indexers, explorers & deep history
- CPU
- 16–32 high-clock cores
- RAM
- 64–128 GB
- Storage
- 8 TB+ NVMe for full history (grows continuously)
- Network
- 1 Gbps
- Clients
- Lotus or Forest archive · full chain history
Best for
- Deep historical state for analytics and explorers
- Long-range backfills and message/receipt history
- Older-epoch reads without choking live RPC
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 Filecoin documentation.
View official Filecoin 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 Filecoin RPC
Shared Filecoin RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated Filecoin 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 Filecoin calls the moment traffic spikesZero rate limits, your Filecoin 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 Filecoin 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 Filecoin endpoint behind included DDoS protection and IP allowlisting
History & specsLimited history and fixed plans you cannot resize as you growFull Filecoin 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 Filecoin client and tuning you choose
// network details
Filecoin Node Specifications
The networks, node software, data interfaces, and chain parameters your dedicated Filecoin node ships with. Filecoin is hybrid: it serves the native Filecoin JSON-RPC (Filecoin.* methods) and, via the FEVM, the Ethereum JSON-RPC (eth_*) so standard Ethereum tooling connects too.
Chain Parameters
- Networks
- Mainnet, Calibration testnet
- Chain IDs (FEVM)
- Mainnet 314 · Calibration 314159
- Native token
- FIL
- Consensus
- Expected Consensus (Storage Power: PoRep + PoSt)
- Block time
- ~30 seconds per epoch
- Finality
- Hard finality at 900 epochs (~7.5 hours)
- Execution
- FVM with FEVM (Ethereum-compatible runtime)
- Data interfaces
- Filecoin JSON-RPC + Ethereum JSON-RPC (FEVM)
- Archive
- Full chain history vs snapshot-pruned full
- Explorer
- filfox.info, filscan.io
Supported Clients
Node software
- Lotus (reference, Go)
- Forest (Rust, ChainSafe)
Data interfaces
- Filecoin JSON-RPC (Filecoin.*)
- Ethereum JSON-RPC (eth_*, FEVM)
- HTTP & WebSocket
JSON-RPC Namespaces
- eth_
- net_
- web3_
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 Filecoin Nodes
Where a private, uncapped endpoint beats a shared RPC pool.
FEVM dApp Backends
Solidity dApps on the FEVM need stable eth_ RPC. A dedicated node serves contract calls, logs, and transaction broadcast with standard Ethereum tooling, with no shared rate caps during traffic spikes.
Storage Deal Monitoring
Track storage deals, sectors, and message receipts over the native Filecoin JSON-RPC. A dedicated node keeps deal-state polling and confirmations consistent without public-endpoint throttling.
Explorer And Indexing
Explorers and indexers query full chain history nonstop. A dedicated archive node supports long-running ingestion across both Filecoin and FEVM data without shared-endpoint limits.
Exchange Deposit Tracking
Track FIL deposits, confirmations, and tipset reorgs without public limits. Dedicated resources cut the timeout spikes that cause missing deposits and delayed crediting.
WebSocket Event Streams
Stream chain events and FEVM logs over WebSockets without drops. A dedicated node keeps long-lived subscriptions stable during busy periods, fit for dashboards and alerting.
Multi-Region Read Layer
Deploy Filecoin nodes close to users across regions. A primary endpoint plus regional readers smooths global read traffic without routing everything to one location.
// how it works
From Filecoin 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 Filecoin Node
Choose full or archive, and Lotus or Forest. Tell us if you need the native Filecoin JSON-RPC, the FEVM eth_ RPC, or both, and the region closest to your users.
- 02
We Provision Bare Metal
Your single-tenant Lotus or Forest node deploys on local NVMe, restored from a current chain snapshot, so you skip the long sync from genesis.
- 03
Get Your Private Endpoint
Receive a dedicated Filecoin and Ethereum (FEVM) 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 Filecoin 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 Filecoin 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 Filecoin RPC node, and what does it actually do?
A Filecoin RPC node is a server running a Filecoin client such as Lotus or Forest that exposes APIs your app uses to read chain data and broadcast messages. In practice, teams rely on a Filecoin node to serve dApps, wallets, indexers, explorers, and storage-deal tooling with stable, predictable access.
Does a Filecoin node serve the Ethereum JSON-RPC, or only the Filecoin JSON-RPC?
Both. Filecoin nodes expose the native Filecoin JSON-RPC (Filecoin.* methods) for chain, message, and storage operations, and through the FEVM they also expose the Ethereum JSON-RPC (eth_* methods). That means standard Ethereum tools like Hardhat, Foundry, and MetaMask work against your dedicated node alongside Filecoin-native tooling.
What are the FEVM chain IDs for mainnet and the testnet?
The FEVM uses chain ID 314 for Filecoin mainnet and 314159 for the Calibration testnet. Calibration is the most production-like testnet and is the recommended place to stage smart contracts and network upgrades before mainnet. A dedicated node can serve either network.
Which client do you run, Lotus or Forest?
Either. Lotus is the Go reference implementation and the most production-tested. Forest is the Rust implementation from ChainSafe and is compatible with most of the Lotus JSON-RPC API. We deploy the client that fits your workload and can advise on the trade-offs for your read patterns and resource budget.
Full node vs archive node: which one supports my required queries?
Choose a full node when you mainly need recent state, receipts, and current reads; it runs on a snapshot-pruned chain to keep storage manageable. Choose an archive node when you need deep historical state for analytics, explorers, or long-range backfills. A dedicated setup lets you pick the right tier without sharing limits.
Why choose a dedicated Filecoin node instead of shared RPC endpoints?
Shared RPC endpoints throttle, vary in latency, and change policies without warning. A dedicated Filecoin node runs on single-tenant CPU, RAM, and NVMe, so your throughput and response times depend on your hardware headroom, not other tenants or shared quotas. You also control which Filecoin and FEVM methods are exposed.
What causes RPC failures during traffic spikes, and how does dedicated hardware help?
Most failures trace back to storage I/O saturation, CPU contention, or too many concurrent WebSocket sessions. Filecoin chain state is large and grows continuously, so disk speed matters. Dedicated hardware removes noisy-neighbor contention, and local NVMe reduces read and write stalls, which is why teams move to a dedicated node when usage becomes production-grade.
Can I scale CPU, RAM, and NVMe as my Filecoin usage grows?
Yes. You can scale up resources as load grows, add NVMe capacity for archive needs, and move to higher core counts for heavy concurrency. Because Filecoin chain and archive data grow continuously, we size storage with headroom and refresh snapshots so your endpoint stays stable as your product grows.
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
Filecoin Developer Resources
Official Filecoin 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 Filecoin 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.