Dedicated Story RPC Node & Story RPC Endpoint | RedSwitches
// dedicated story rpc node

Private Story RPC Endpoints on a Dedicated Node

A private Story RPC endpoint on single-tenant NVMe bare metal. Full, archive, or validator nodes run story-geth plus the story consensus client with full Ethereum JSON-RPC, 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
  • story-geth + story Consensus Client
  • Full Ethereum JSON-RPC & WebSockets
  • 20+ Global Tier III Locations
deploy.shlive

$ rs deploy story --type full --region fra

allocating single-tenant bare metal

starting story-geth execution client

syncing story (cometbft) consensus client

serving ethereum json-rpc over https + wss

attaching DDoS shield + IP allowlist

private endpoint live · https + wss

region Frankfurt · story-geth + CometBFT · single-block finality

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

Why Teams Run Story 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. story-geth plus story consensus setup, archive --gcmode tuning, and Ethereum JSON-RPC config, handled by people who run Story 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, IP 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 Story 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

Story Full Node

For IP apps, wallets, bots & backend APIs

CPU
4–8 high-clock cores
RAM
16–32 GB
Storage
1–2 TB NVMe
Network
1 Gbps+ on a 10/25 Gbps port
Stack
story-geth + story (CometBFT consensus)
Best for
  • Live reads, contract calls, and tx broadcasts
  • Wallet, licensing, and IP app traffic
  • Private Ethereum JSON-RPC over HTTP and WSS
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 Story documentation.

View official Story node docs →

Inquiring about: Story · 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 Story RPC

Shared Story RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated Story 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 Story calls the moment traffic spikesZero rate limits, your Story 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 Story 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 Story endpoint behind included DDoS protection and IP allowlisting
History & specsLimited history and fixed plans you cannot resize as you growFull Story 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 Story client and tuning you choose
// network details

Story Node Specifications

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

Chain Parameters

Networks
Story Mainnet, Aeneid testnet
Chain IDs
Mainnet 1514 · Aeneid 1315
Native token
IP
Consensus
CometBFT (Cosmos SDK) Proof of Stake
Finality
One-shot, single-block (CometBFT)
Execution
story-geth, EVM (Ethereum JSON-RPC)
Transports
HTTP JSON-RPC and WebSocket (WSS)
Archive
Full historical state (--gcmode=archive)
Explorer
storyscan.xyz · explorer.story.foundation

Supported Clients

Execution client
  • story-geth (Geth fork)
Consensus client
  • story (CometBFT)

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 Story Nodes

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

IP Asset Onboarding

Creator apps register IP assets, confirm ownership signals, and turn uploads into Story-linked records. A dedicated node keeps registration reads and writes steady under demand for media, music, art, and gaming products.

License Rule Engines

Licensing platforms read on-chain terms, trigger approved contract actions, and track remix, commercial, and distribution rights. Reserved CPU and NVMe keep policy checks tied to current chain data without stalling during traffic spikes.

Royalty Flow Tracking

Dashboards follow royalty events, claim signals, and payout activity without turning raw transactions into guesswork. Dedicated infrastructure gives creators, studios, and rights holders clearer revenue views faster than a throttled shared pool.

AI Data Rights

AI-data platforms verify dataset ownership, usage terms, and licensing records before granting access. Dedicated capacity keeps rights-linked verification reads fast at scale before model training, resale, or gated delivery begins.

IP Graph Indexing

Indexers map how IP assets, derivatives, licenses, owners, disputes, and royalty paths connect. Archive-ready storage supports the deep backfills these graphs require, giving search tools and analytics richer context than basic feeds.

Creator Marketplace Sync

Marketplaces keep listings, license mints, ownership changes, and buyer alerts close to chain activity. WebSocket-ready setup keeps the feed current without constant polling, reducing stale states when creators publish or users act.

// how it works

From Story 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 Story Node

    Choose full, archive, or validator. Story serves Ethereum JSON-RPC over story-geth; tell us your archive depth and the region closest to your users.

  2. 02

    We Provision Bare Metal

    Your single-tenant node deploys story-geth plus the story consensus client on NVMe, synced from current state so you skip the long cold sync.

  3. 03

    Get Your Private Endpoint

    Receive a dedicated Ethereum JSON-RPC endpoint over HTTP and WSS 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 Story 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 Story 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 Story RPC Node?

A Story RPC Node lets your app read Story Mainnet data, send transactions, and interact with Story smart contracts through RPC calls. We deploy it on dedicated hardware so your backend, wallet, indexer, or IP app gets private Story RPC access instead of depending only on public endpoints.

Why choose a Dedicated Story RPC Node instead of a public RPC?

Public RPCs are useful for testing, but production teams need steadier access, cleaner controls, and reserved capacity. With a Dedicated Story RPC Node from RedSwitches, your CPU, RAM, NVMe, and network resources stay tied to your workload, not a shared endpoint pool.

Which Story clients are required to run a Dedicated Story RPC Node?

Story nodes use two core clients: story-geth for the execution layer and story for consensus. We install the required client stack, check current release guidance, and plan deployment around sync time so your team starts from a clean baseline.

Does a Story RPC Node support HTTP and WebSocket access?

Yes. story-geth exposes standard Ethereum JSON-RPC over HTTP and WebSocket. HTTP fits backend reads, contract calls, and transaction flow. WebSockets help apps track blocks, transactions, IP activity, license events, and marketplace updates in real time.

What is the difference between a full Story RPC node and an archive Story RPC node?

A full Story RPC Node fits live app reads, transaction broadcasts, wallets, and normal backend calls. An archive node keeps deeper historical state for indexers, analytics, explorers, royalty tracking, and long-range IP data review. Story's docs describe archive mode with --gcmode=archive.

Can Story RPC support IP registration apps, licensing platforms, and royalty dashboards?

Yes. A Story RPC setup can support IP asset onboarding, licensing workflows, royalty signals, creator marketplaces, and analytics products. We size your server based on request volume, WebSocket needs, storage depth, and whether your app needs full-node or archive Story data.

How long does a Story RPC Node take to deploy?

We provision the server quickly, but go-live depends on Story sync time, node mode, current chain state, and storage needs. Full nodes usually move faster than archive builds. Our promise is simple: we deploy according to sync time, not fake instant-sync claims.

Should production teams run more than one Story RPC Node?

For production, we recommend at least two nodes when uptime, maintenance windows, or regional traffic matter. A Premium Story dedicated node cluster can separate reads, writes, indexing, and failover so one heavy workload does not slow every service.

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

Story Developer Resources

Official Story 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 Story 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