Shared
From $49/mo
- All 68+ chains · one API key
- 10M requests / month
- 25 req/s burst
- Community support
Pricing
Transparent tiers, clear upgrade path
Pay for shared capacity while you build. Switch to dedicated nodes when archive state, WebSocket stability, or SLA-backed uptime become part of your production requirements — not after an outage.
Dedicated
From $399/mo
- Isolated node · per chain & region
- Unlimited requests
- Archive, trace & WebSocket
- SLA 99.99% · priority support
Enterprise
Custom
- Private infrastructure · your VPC
- Multi-region · custom routing
- Unlimited + burst capacity
- Custom SLA · compliance
- Dedicated 24/7 support
Compare
Side-by-side
Numbers are starting points. Dedicated and enterprise quotes reflect chain, region, sync mode, and load.
| Shared | Dedicated | Enterprise | |
|---|---|---|---|
| Starting price | From $49/mo | From $399/mo | Custom quote |
| Chains | 68+ via one key | Per deployment | Multi-chain layouts |
| Requests | 10M / mo included | Unlimited | Unlimited + burst |
| Rate limit | 25 req/s burst | Sized for workload | Contractual |
| Node type | Shared edge pool | Private full / archive | Private + redundant |
| WebSocket | Best-effort | Included | Custom fan-out |
| Archive / trace | — | Where chain supports | Multi-tier |
| Regions | Tokyo · Europe | Pick per node | Multi-region |
| SLA | Best-effort uptime | 99.99% | Custom SLA |
| Support | Community | Priority | 24/7 named channel |
| Billing | Self-serve dashboard | Quote + contract | Enterprise agreement |
Guidance
When to choose each tier
Shared
Choose shared when…
- You are building or testing and traffic is under ~10M calls/month
- You need many chains with one integration, not archive depth
- Occasional burst is fine — steady high QPS is not critical yet
Dedicated
Choose dedicated when…
- Production apps or indexers hit shared limits or need archive state
- WebSocket subscriptions must stay stable under load
- You want SLA-backed uptime on infrastructure you do not operate
Enterprise
Choose enterprise when…
- Compliance, VPC placement, or redundant multi-region is required
- Trading or custody workloads need private paths and custom routing
- You need contractual SLA, security review packs, and 24/7 escalation
Billing
How invoicing works
- Shared plans bill monthly through the Azxa dashboard. Overage and upgrade paths are visible in usage charts.
- Dedicated nodes are quoted per deployment — chain, region, and node mode — with clear handover before production cutover.
- Enterprise agreements can include custom invoicing, security questionnaires, and phased rollouts across regions.
FAQ
Common questions
- Can I start on shared and move to dedicated later?
- Yes. Most teams keep the same JSON-RPC integration and swap the endpoint URL when a dedicated node is ready. We help scope region, sync mode, and archive before migration.
- What counts as a request on shared?
- Each JSON-RPC HTTP call counts as one request. Batch calls count per method in the batch. WebSocket messages are metered separately on shared — dedicated plans include subscription capacity sized for your workload.
- Is a credit card required for shared sign-up?
- No card required for the starter tier. Upgrade or add billing when you are ready for higher limits or move to dedicated.
- How is dedicated pricing calculated?
- Quotes depend on chain (disk and CPU profile), region, sync mode (full vs archive), and expected RPC/WebSocket load. Contact us with chain list and peak QPS for a fixed monthly quote.
- Do you offer annual or volume discounts?
- Dedicated and enterprise agreements support annual commits and multi-node bundles. Ask sales when scoping more than one chain or region.
Get started
Start on shared RPC today
No card required for the starter tier. Need dedicated or enterprise? We scope in one call.