Your First Request
Blockspace isn't one subscription that unlocks everything. Every product has its own access model, its own timeline, its own entry point — find the row below that matches your situation.
| Product | What it is | How to start | Time to first call |
|---|---|---|---|
| ShredStream | Stream Solana shreds before slot confirmation | Start free → self-serve | minutes |
| Direct Shreds | Dedicated IP, your bandwidth alone | Provision → — provisioning ~30 min | ~30 min |
| SWQOS | Stake-weighted priority lane (HTTP RPC) | Enable → — public endpoint, no key | minutes |
| SWQOS QUIC | Stake-weighted priority lane (QUIC, signed) | Subscribe or trial → — self-serve, add pubkey in dashboard | minutes |
| Relayer/TPU | MEV mempool + bundle relay, pay-on-performance | Apply → | days (application review) |
If you're on a self-serve product — ShredStream, SWQOS HTTP, SWQOS QUIC, Direct Shreds onboarding — provisioning happens right in the dashboard. Application-gated products work differently: start with an email to support-blockspace@everstake.com.
After provisioning
Once you're provisioned, the product page in the dashboard shows the connection details: endpoint URL, region, and whichever authentication method that product uses (token / source-IP allowlist / signing-pubkey allowlist / on-chain tip). The full matrix is in Authentication.
From there, go straight to the product quickstart — each one has copy-paste examples:
- ShredStream Quickstart: gRPC client, x-token metadata
- Direct Shreds Quickstart walks through the UDP receiver against your allowlisted IP
- SWQOS Quickstart — HTTP send with tip instruction (or QUIC with signing keypair)
- For Relayer/TPU, the quickstart covers the gRPC push to a Block Engine you operate, plus TPU-direct bundle submission
Reference
- Authentication has the per-product auth matrix
- Rate Limits — per-tier ceilings
- Need to know where a product runs? See Regions & Endpoints
- Troubleshooting — common failures, by product