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.
A private Gravity RPC endpoint on single-tenant NVMe bare metal. Full or archive Arbitrum Nitro nodes, snapshot-synced, with zero rate limits and no compute units.
$ rs deploy gravity --type full --region fra
allocating single-tenant bare metal
restoring nitro chaindata snapshot
connecting ethereum l1 + beacon
starting arbitrum nitro node
attaching DDoS shield + IP allowlist
private endpoint live · https + wss
A single-tenant node with people behind it: unlimited throughput, a named account manager, direct engineering access, and billing built for Web3 teams.
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.
A named account manager who knows your setup, not a ticket queue. One contact for provisioning, scaling, and anything urgent.
Talk to the engineers who run the metal. Arbitrum Nitro config, snapshot strategy, trace and debug builds, and the Ethereum L1 plus beacon dependency, handled by people who run Gravity nodes daily.
Place your node beside your users across 20+ Tier III locations. Multi-region for redundancy, split read and write endpoints.
Settle in crypto or fiat, G included. Flexible billing for Web3 teams, with the same predictable flat monthly price either way.
Custom load balancing, failover, and split read/write topology, designed and tuned for your traffic by our engineers.
Pick a node type, tell us your workload, and an engineer sizes and quotes it. One flat monthly price, no compute units, no overages.
For dApps, wallets, bots & indexers
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 Gravity documentation.
View official Gravity node docs →For deep history, tracing & analytics
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 Gravity documentation.
View official Gravity node docs →Thanks. A Web3 engineer will spec your private endpoint and reach out shortly.
Something went wrong. Please try again or email sales@redswitches.com.
Shared Gravity RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated Gravity node is your own private backbone: flat-priced, uncapped, and yours alone.
The chain IDs, clients, transports, and JSON-RPC namespaces your dedicated Gravity node ships with. Built to a standard so your existing tooling connects with no changes.
You control which namespaces are exposed. Enable debug and trace on archive builds, keep the rest private behind IP allowlisting.
Where a private, uncapped endpoint beats a shared RPC pool.
When users open balances, approve tokens, or track pending activity, delay erodes trust. A dedicated Gravity RPC node gives account reads, state checks, and transaction lookups a cleaner path on reserved hardware.
Data teams replay logs, rebuild tables, and refill missing ranges after changes or outages. Dedicated Gravity RPC infrastructure helps backfill jobs run with fewer interruptions from shared rate limits and noisy neighbors.
Notification systems, reward triggers, and app alerts depend on fresh on-chain signals. This fits teams that listen continuously and need their Gravity RPC layer to hold steady subscriptions and event capture over WebSockets.
Many apps make several contract reads before one screen loads or one action completes. Routing logic, eligibility checks, balances, and reward states stack quickly, and dedicated capacity keeps those paths clean under query pressure.
Gravity often ties to campaign logic, task completion, and reward delivery. This fits platforms that verify on-chain actions, assign outcomes, and issue rewards, where late or inconsistent reads break the user journey.
Exchanges, custodial tools, and finance dashboards need dependable deposit checks, confirmation reads, and withdrawal status tracking. Dedicated infrastructure matters here because even short lookup delays ripple into user trust and support load.
Pick a node, we provision dedicated bare metal, you get a private, snapshot-ready RPC URL.
Choose full or archive, and bring or host the Ethereum L1 RPC plus beacon endpoint your Nitro node depends on. Pick the region closest to your users.
Your single-tenant Arbitrum Nitro node deploys on dedicated NVMe, bootstrapped from a current chaindata snapshot, so you skip the multi-day replay.
Receive a dedicated HTTPS + WSS RPC endpoint with unlimited requests and zero rate limits, private behind IP allowlisting and DDoS protection.
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.
Deploy across 20+ Tier III locations in the US, EU, Asia, and Australia. Put your Gravity node in the region your traffic actually comes from, not wherever a shared pool happens to route you.
RPC latency is mostly physical distance. Running in the same region as the Gravity sequencer 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.
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.
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.
Real reviews from Trustpilot, HostAdvice, Cryptwerk, and Google.
Port speeds on cloud were capped and shady. With RS I actually get the 25Gbps they say. No throttle bs.
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.
Set up multiple Solana + Avalanche validators through them. Hardware was clean, latency was low (especially in Europe), and uptime’s been 100% so far.
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.
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.
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.
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.
Deployed a few Ethereum and Bitcoin nodes here. Uptime’s been flawless, and sync speed was great thanks to their storage config.
They provide what they promise, I got no throttling while running my RPC Nodes. I got server in a Amsterdam for the best price.
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.
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.
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.
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.
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.
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 is super responsive. I had an issue with an OS reinstall and they jumped in within 10 minutes… Transparent pricing = win.
They have an instant delivery section… they delivered it within 120 mins with all my requirements fulfilled (OS/RAID/Software configured etc).
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.
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).
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.
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.
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.
"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.
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!
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.
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.
We have been using Red Switches for several years since 2021. I have never experienced such fast customer service.
Absolutely delighted with RedSwitches! The setup was quick and free, and the fact that they accept all major payment gateways made the process seamless.
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.
Chain IDs, clients, archive data, getLogs limits, and why dedicated beats compute-unit billing.
A Gravity RPC node is the server your app talks to when it needs chain data, transaction status, logs, or contract reads. Today the live production target is Gravity Alpha Mainnet, which Gravity documents as an Ethereum rollup using the Arbitrum Nitro stack. We run that node on dedicated hardware so your app gets a private Gravity RPC lane instead of competing inside a public pool.
Not in the staking sense. Gravity Alpha Mainnet is an Ethereum rollup on the Arbitrum Nitro stack with a centralized sequencer, so there is no permissionless, stake-to-earn validator like Ethereum or Solana. What we provision is what apps and indexers actually need: a fast, dedicated full or archive RPC node running the Nitro client, with trace and debug builds available for heavier workloads.
Yes. Gravity's live node guide is clear on this: you need a local data directory, an Ethereum mainnet RPC endpoint with unlimited eth_getLogs, and an Ethereum beacon chain RPC endpoint. The guide also requires the latest snapshot, because syncing from genesis is not supported due to historical data availability format changes. You can bring your own Ethereum endpoints or host them with us in the same region for tighter latency, and we plan around those upstream dependencies from day one.
For Gravity Alpha Mainnet the official chain ID is 1625 and the native token is G. Gravity's docs also list the official RPC endpoint and explorer references for the live network. If you are connecting a wallet, backend, or middleware stack, we use those live settings as the base and then point your services to your private RedSwitches endpoint once your server is ready.
Most teams do not need archive on day one. A full node is usually enough for wallets, dashboards, internal services, transaction tracking, and many dApps. Archive is the better fit when you need deeper historical state access, long-range research, forensic work, or heavier historical processing. Since Gravity's live network runs on Nitro today, we use this as our practical sizing approach for production Gravity RPC workloads.
Yes. Gravity's self-hosted node guide maps HTTP on 8547 and WebSocket on 8548, so a self-managed or managed dedicated deployment can serve both request-response traffic and subscription-driven workloads. We usually recommend HTTPS for standard app reads and broadcasts, then WebSockets for live event listeners, bots, notifications, and systems that need fresh block or log updates without constant polling.
Not every app needs it. If you are building a simple wallet, portfolio view, or basic dashboard, standard RPC methods are often enough. If you are running indexers, debugging failed contract behavior, reviewing incidents, or doing deeper engineering analysis, trace and debug become much more useful. Gravity's current node guide explicitly adds both endpoints, so we can expose them on your Dedicated Gravity RPC node when your workload needs more than plain reads and writes.
Yes. This is one of the biggest reasons teams choose us over a generic shared API. Our dedicated RPC platform supports keeping endpoints private with firewall rules and IP allowlisting, and our dedicated infrastructure also supports private networking, VPN-style access patterns, and direct server control with root and IPMI. If your RPC endpoint is part of your security boundary, that control matters.
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.
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.
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.
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.
Official Gravity resources for builders running a node: docs, explorers, source, network status, and faucets. Every link points at the first-party source, not a wrapper.
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.