Solana JSON-RPC, on the same key as your gRPC.

One endpoint for reads, one endpoint for streams, one API key for both. No credit metering, no per-method surcharges, sendTransaction lives in its own quota bucket so heavy reads never starve your submits.

20–40ms
p50 getSlot
1 key
RPC + gRPC
$99
Flat monthly start
AMS / FRA
Edge colocated
01

Flat monthly, no credits

$99–$249/mo. You pay the same bill whether you fire 10k or 500k requests. No method multipliers, no overage surprises when the market moves.

02

Bundled with gRPC

Stream with Yellowstone on grpc.subglow.io:443, read with JSON-RPC on rpc.subglow.io. One key, one bill, one dashboard.

03

sendTransaction bucket

Submits have their own daily quota separate from reads. When the market spikes and your scanner goes hot, sendTransaction still has budget to get your trade in.

Drop-in replacement

Point your existing code at rpc.subglow.io

Standard JSON-RPC over HTTPS. No SDK lock-in, no custom wire format. Works with every Solana client library.

TypeScript / @solana/web3.js
import { Connection } from "@solana/web3.js";

const conn = new Connection(
  "https://rpc.subglow.io/" + process.env.SUBGLOW_API_KEY,
  "confirmed",
);

const slot = await conn.getSlot();
Python / solders
from solders.rpc.requests import GetSlot
import httpx, os

url = f"https://rpc.subglow.io/{os.environ['SUBGLOW_API_KEY']}"
r = httpx.post(url, data=GetSlot().to_json())
print(r.json()["result"])

Method coverage

Every standard mainnet-beta method on every paid tier. Archival methods are Dedicated-only so shared plans stay fast.

Reads
  • getAccountInfo
  • getBalance
  • getTokenAccountsByOwner
  • getLatestBlockhash
  • getSlot
  • getTransaction (recent)
  • getSignatureStatuses
  • simulateTransaction
  • + full standard surface
Writes (dedicated bucket)
  • sendTransaction
  • sendRawTransaction

Separate daily quota so a heavy-read bot never starves its own submits during a market spike.

Archival — Dedicated only
  • getProgramAccounts (unfiltered)
  • getSignaturesForAddress (historical)
  • getBlock (historical)
  • getBlocks ranges

Archival on shared infra silently degrades everyone's latency. We reject instead of throttle.

Bundled quotas

What you get on each plan

Every plan includes both products. The table below shows the RPC and sendTransaction caps — gRPC stream counts and filter access are documented on the gRPC page.

PlanPriceRPC / daysendTx / dayArchival
Free trialFree(apply)2,00050
Sniper$99/mo50,0002,000
Pro$249/mo500,00020,000
DedicatedCustomUnlimitedUnlimitedYes
One bill, both products

Pick your tier

Free trial
Free(apply)
Kick the tires before committing
  • 1 concurrent stream
  • 2k JSON-RPC requests/day
  • 50 sendTransaction/day
  • Pump.fun + Raydium + Jupiter presets
  • Pre-parsed JSON
  • Manual review (~24h)
Apply for free trial
Sniper
$99/mo
Solo traders and bot builders
  • 2 concurrent streams
  • 50k JSON-RPC requests/day
  • 2k sendTransaction/day
  • Pump.fun + Raydium + Jupiter filters
  • Pre-parsed JSON
  • WebSocket fallback
Start sniping
Pro
$249/mo
Serious trading operations
  • 10 concurrent streams
  • 500k JSON-RPC requests/day
  • 20k sendTransaction/day
  • Custom Program ID filters
  • Full-speed delivery, zero rate limits
  • Shred-aware filtering
Go Pro
Dedicated
Custom
Institutional, latency-critical
  • Unlimited concurrent streams
  • Unlimited JSON-RPC + sendTransaction
  • Private gRPC + RPC endpoint
  • Colocated Frankfurt or NY4
  • 99.9% latency SLA
  • Archival + custom parsing pipelines
Talk to us

FAQ

How is Subglow's Solana RPC different from Helius or QuickNode?

Three differences: (1) flat monthly pricing — Sniper $99/mo, Pro $249/mo, no credit metering and no per-method surcharges; (2) bundled with gRPC on the same API key — point your Connection at rpc.subglow.io and your Yellowstone client at grpc.subglow.io:443 using one credential; (3) dedicated sendTransaction bucket so heavy read traffic can't starve your transaction submits. We run our own edge infrastructure colocated in AMS/FRA with server-side method gating and quota enforcement at the edge.

Which JSON-RPC methods are supported?

All standard read methods — getAccountInfo, getBalance, getTokenAccountsByOwner, getLatestBlockhash, getSlot, getTransaction, getSignatureStatuses, simulateTransaction, and the rest of the mainnet-beta surface. Write-path methods (sendTransaction, sendRawTransaction) land in a dedicated quota bucket so heavy reads cannot starve submits. Archival methods (getProgramAccounts without filters, getSignaturesForAddress before recent slots, getBlock on historical slots) are gated to the Dedicated plan where we can provision archival capacity deterministically.

What's the latency for a typical getSlot or sendTransaction?

p50 getSlot round-trip sits around 20–40ms from our AMS / FRA edge. sendTransaction forwarded to a Jito-priority relay lands the signed transaction at validator leaders with a typical 40–80ms submit tail. The gateway is colocated with our gRPC edge, so if you stream and submit from the same bot you avoid an extra cross-region hop.

How do quotas work?

Each plan gets a flat daily RPC-request cap plus a separate sendTransaction cap. Counters reset at midnight UTC. Free trial: 2k RPC / 50 sendTx per day. Sniper ($99/mo): 50k RPC / 2k sendTx. Pro ($249/mo): 500k RPC / 20k sendTx. Dedicated: unlimited and contractual. The split bucket means that a bot scanning 400k accounts/day still has its 20k submit budget intact — no credit math.

Can I use it as a drop-in replacement for my current RPC URL?

Yes. Point your Solana Connection or Web3.js client at https://rpc.subglow.io/<apiKey> (or use a Bearer header if you prefer) and every standard method just works. Existing libraries — @solana/web3.js, @coral-xyz/anchor, solders (Python), solana-sdk (Rust) — need no code changes beyond the URL. See /docs/rpc for copy-paste snippets.

Do I need a separate account for RPC and gRPC?

No. One Subglow API key opens both endpoints. Your dashboard shows the gRPC messages, RPC requests, and sendTransaction counts side by side. One bill, one quota view, one Telegram channel for support.

Do you offer archival / historical queries?

Full archival access is available on the Dedicated tier, where we provision dedicated archival capacity sized to your workload. On Sniper and Pro, heavy archival methods are rejected rather than silently throttled, because running unfilled getProgramAccounts on a shared tier degrades every other customer's latency. Most trading use cases don't need archival — they need recent slots fast, which every tier delivers.