Dedicated Saga RPC node. A private Saga RPC endpoint that only you use: no rate limits, every method on, one fixed monthly price.
The Saga Security Chain (SSC) is the Cosmos SDK and CometBFT based mainnet of the Saga protocol, where validators stake SAGA to provide security to the dedicated chainlets launched on the Saga platform. Nodes run the sscd binary on the ssc-1 chain.
Saga RPC endpoint and network details.
| Network | Saga mainnet |
| Currency | SAGA |
| Interfaces | CometBFT RPC · REST · gRPC |
| Dedicated endpoint | Your own Saga RPC endpoint, from $99/mo → |
Public endpoints are listed in Saga's official documentation (nodedocs.saga.xyz). They are shared and rate limited. Facts from Saga's official documentation.
Order a dedicated Saga RPC node.
Pick the node and the city. Where a city shows a price, pay in crypto and we start building; anywhere else, you get a firm quote within the hour.
What every dedicated Saga node includes.
- Fully managed at no additional cost: we set it up, sync it, monitor it 24/7, apply every upgrade and fix it if anything breaks
- Monitoring at no additional cost: live node and server metrics for your node in your dashboard
- No rate limits: the hardware is the only ceiling
- Every RPC method on, heavy queries included
- Unlimited gRPC and RPC connections
- Your own domain and an IP allowlist you control
- 99.99% SLA in writing, with service credits
- 24/7 support answered by engineers
Saga node requirements, and what we build.
Chain facts from Saga's official documentation (nodedocs.saga.xyz). Where it is silent, the row says so.
| Node software | sscd |
| Interfaces | CometBFT RPC, REST, gRPC |
| Full node | Yes, from $99/mo |
| Archive node | Confirmed at quote time |
| Validator | Public validator role; quoted per setup |
| Gas token | SAGA |
| Official hardware guidance | The docs give the minimum specs recommended to run the Saga Security Chain as a validator as 4 Cores CPU, 16GB RAM, 500GB storage and a Linux-based OS, with ports 26656 (P2P) and 26660 (Prometheus) open. source ↗ |
| Argusnodes build | Meets the official guidance above with headroom on top, never at the minimum. Ask and we tell you the exact CPU, RAM and NVMe; root access on request. |
What changed on Saga recently
- SSC upgraded to sscd v4.0.0 (released 12 Mar 2026) under governance proposal #28 'Upgrade SSC to v4' at height 10,852,141 (voting ended 17 Mar 2026), populating liquid validators and enabling liquid staking (80% global cap, 100% per-validator cap); mainnet ssc-1 reports ssc 4.0.0 on CometBFT 0.38.19 as of 22 Aug 2026. source ↗
- In Dec 2025 SSC went through three consecutive mandatory upgrades: v1.0.0 (proposal #23, height 9,458,267), v2.0.0 on 22 Dec 2025 fixing non-deterministic gas and PFM bugs (proposal #24, height 9,519,667) and v3.0.0 on 24 Dec 2025 fixing IBC packet ordering for partners such as Axelar (proposal #25, height 9,547,172). source ↗
- The official installation page still pins 'git clone -b v0.4.0' (the Jul 2025 'Inflation v2' release) while mainnet runs v4.0.0, so operators must install from the latest GitHub release rather than the docs' pinned tag. source ↗
- Actively maintained as of Aug 2026 (ssc repo pushed 9 Mar 2026, chain producing blocks); docs last show a full-node service example dated Jul 2025. source ↗
Sources: nodedocs.saga.xyz · nodedocs.saga.xyz/validator-and-full-node-setup/joining-ssc-mainnet-post-genesis · nodedocs.saga.xyz/introduction/requirements.md
Dedicated Saga RPC node: the questions buyers ask.
What is a Saga RPC node?
A server running Saga's node software (sscd) that answers RPC requests: reading balances and state, and sending transactions. It can be public and free, shared by a provider's customers, or dedicated to one client.
What is a dedicated Saga RPC node?
A Saga node on a bare-metal server that runs for one client only, with its own private RPC endpoint. Nobody else's traffic shares the machine, so there is no rate limit and no noisy neighbour, and every method the client exposes is on. Argusnodes builds, syncs, monitors and upgrades it for you at one fixed monthly price.
Is my Saga node managed and monitored, and what does that cost?
Yes, and so is monitoring, both at no additional cost. We set up and sync the node, watch it 24/7 with live node and server metrics in your dashboard, apply every network upgrade and client update, and fix it when something breaks. If you need help around the node, such as connecting it to your app, moving off another provider or setting up an indexer, our engineers help with that too, at the same monthly price.
What is a private Saga RPC endpoint?
An RPC endpoint that only your applications use. It sits on a dedicated Saga node that is yours alone, on your own domain if you want one, and answers only the IP addresses you allowlist. No other customer's traffic shares the machine, so nobody else's burst becomes your latency, and there is no rate limit to hit.
How long until my Saga node is live?
As soon as it has synced with the Saga network, and we tell you the moment it is ready. Sync time depends on the node type, so your quote carries an estimate for your exact setup rather than a number that is sometimes wrong. The quote itself lands within the hour, around the clock.
What is included in the from $99/mo for my Saga node?
Everything the node can do, with the premium add-ons other providers bill separately included free: unlimited RPS, every RPC method including heavy queries, unlimited gRPC and RPC connections, your own domain with an IP allowlist, 18 cities to choose from, a 99.99% SLA with credits, 24/7 engineer support and live p50/p99 in your dashboard. There is no add-on price list because nothing is an add-on.
What hardware will my Saga node run on?
A machine that meets Saga's official hardware guidance (quoted in the spec sheet on this page) with headroom on top, on a dedicated bare-metal server. We never build at the minimum, because a node sized to the minimum becomes the bottleneck the day the chain grows. Ask before you order and we tell you the exact CPU, RAM and NVMe; the delivery email names the server, and root access is yours if you want it.
Does Argusnodes run Saga archive nodes?
Archive support on Saga is confirmed against its documentation as part of your quote. Every method the client exposes is on by default at no extra charge.
Can I run a Saga validator with Argusnodes?
Yes. Saga has a public validator role, and we operate validators under the same monitoring and support as RPC nodes, quoted per setup. Pick "Validator" in the configurator and describe the stake setup.
Can I move my Saga endpoint from another provider?
Yes. A dedicated Saga node speaks the same CometBFT RPC and REST and gRPC interfaces as the shared endpoint you use today, so migration is pointing your application at your own endpoint. Billing is monthly with no lock-in on our side, and support engineers are on the channels 24/7 during cutover.
Are there rate limits or connection caps on a dedicated Saga node?
No artificial ones: unlimited RPS and no connection cap. The machine is yours alone, so the hardware is the only ceiling: if it can serve the request, you can send it. There is no per-plan connection cap because there is no plan tier.
How do I pay for my Saga node, and can I cancel?
In crypto, with no KYC and no setup fee. Pay monthly, or save 5% quarterly and 10% annually, and your price is locked for as long as your node runs. Cancel at the end of any term; the node is provisioned for you alone, so there is no meter to escape and no exit fee.
What is the Saga RPC URL?
The public Saga RPC URLs are listed in Saga's official documentation (nodedocs.saga.xyz). They are shared, rate limited and run by third parties, so they are fine for a wallet and not for an application. A dedicated node gives you a private Saga RPC URL of your own, on your domain if you want, that nobody else uses.
Is Saga RPC free?
Public Saga endpoints are free and listed in Saga's official documentation (nodedocs.saga.xyz). They are shared and rate limited, which is fine for a wallet or a test. A dedicated Saga node is the paid option for an app, bot or indexer, at one fixed monthly price.
What is the best Saga RPC provider?
It depends on the workload. Check four things: whether the node is single-tenant or shared, whether there are rate limits or credits, whether archive, trace and debug are included, and who answers when it breaks. For a wallet, a free public endpoint is enough. For an app, bot or indexer, a dedicated node with no rate limits avoids the throttling of shared plans. Our comparison pages (argusnodes.com/vs) set us against other providers, with sources.