What's not allowed
Programs, methods, and use cases blocked on shared plans, with workarounds.
// updated 2026-06-04
Honest, complete list of what shared plans don't support - and what to use instead.
Restrictions are validated by Supanode engineering for v1, pending final sign-off before public launch.
gRPC: blocked programs
The programs below cannot be used in accounts.owner or transactions.account_include on shared plans (FOCUS, BUILD, GROW, PROFESSIONAL). They generate too much traffic to serve reliably on shared infrastructure. Available on Dedicated Node.
| Program | Address |
|---|---|
| Token Program | TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA |
| Token-2022 | TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb |
| System Program | 11111111111111111111111111111111 |
| Compute Budget | ComputeBudget111111111111111111111111111111 |
| Associated Token Account | ATokenGPvbdGVxr1b2hvZbsiqW5xWH25efTNsLJA8knL |
For details and reasoning per program, see gRPC Restrictions.
gRPC: other constraints
- Replay (
from_slot) - shared plans only stream forward. Historical replay needs Dedicated. - Full block streaming -
blockswith emptyaccount_includeis available on shared as a paid add-on. See Full Block Streaming.
WebSocket: blocked subscriptions
| Subscription | Reason |
|---|---|
blockSubscribe | Full block payloads - too heavy for shared infrastructure |
voteSubscribe | Validator vote firehose |
slotsUpdatesSubscribe | Sub-step slot updates |
logsSubscribe("all") and logsSubscribe("allWithVotes") | All logs of all transactions |
programSubscribe without dataSize or memcmp filter | Whole-program subscriptions are unconditionally blocked |
For details, see WebSocket Restrictions.
RPC: how it's restricted
No method blocklist for RPC. Every method in the Solana RPC spec is supported. Heavy traffic is shaped by method weights, not bans.
What controls heavy traffic is the method weight system. Calls that touch many accounts cost more RPS units per call - getProgramAccounts is 30 units, getTransaction is 10. See RPC Limits for the table.
The plan price reflects this implicit budget. A 100 RPS plan handles ~100 simple getAccountInfo calls per second, but only ~3 getProgramAccounts calls per second.
Acceptable use
Don't use Supanode for:
- Public proxy services that resell our capacity to third parties.
- Workloads that intentionally probe rate limits to map other tenants.
- Anything illegal in the jurisdiction where you operate.
Standard stuff. We won't run a 50-page legal document - we'll use reasonable judgment, and if something is borderline, we'll talk to you before action.
What you can do instead
Dedicated Node - shared restrictions don't apply.
Full Block Streaming add-on for gRPC.
gRPC with proper filters - same data, more efficient.
Telegram @supanode_tgs.
Per-product restrictions pages
What RPC blocks (none) and how weights work.
Blocked WS subscriptions in detail.
Per-program reasoning for shared plans.
Next steps
All 5 Bundle plans.
48-hour trials on every product.
Shared-plan restrictions don't apply.
Fully custom hardware.