Goldsky

Goldsky Boost

Keep your RPC provider. Cut your bill.

A global CDN for your existing RPC endpoints, answering reads in milliseconds while saving you money.

Your RPC requestsHit Boost's cacheReducing paid requestsReducing billable requests to your provider

Users save 45% on average

Boost my endpoints

Read the docs

Best-in-industry teams build with Goldsky

View case study

Good for the bill, great for the app

Grand for both your wallet and users.

Cache hitCache miss

Hit our cache instead of your wallet

We already made that RPC call, let us share it with you.

Works with Alchemy, QuickNode, Infura, Dwellir, Ankr, and dRPC.

Bring your own RPC provider

Add Boost in front of the RPC endpoints you already use.

Serve reads from a server close to your users

Leverage our 4-region global CDN to minimize latency.

Have providers on standby

Keep backup upstreams on file. Automatic failover coming soon.

Boost is free for a limited timeUsers save 45% on average

See what a free CDN could save you

Estimate how much traffic Boost can answer before it reaches your RPC provider.

Provider price/ millionMonthly requestsmillion

Cache hit rateThe 45% default is based on the past week of production traffic. Actual cache hit rates vary by chain and RPC method. See the Boost docs for details.45%

Estimated monthly RPC cost today compared with Boost
Today	$500 per month Provider$500all 50M requests at $10/M Provider
With Boost45% SavedNo savings yet	$275 per monthSave $225 Provider passthrough$27555% of requests forwardedFree cache hits$22522.5M cache hits at no charge Provider passthroughSavings from free cache hits

Free

Free for a limited time. Unlimited requests. Fair use limits apply. No credit card required.

Boost my endpoints

Enterprise

Custom

Add contractual guarantees and infrastructure tailored to your production requirements.

Committed support response times
Uptime SLAs
Custom configurations
Private networking
Other advanced functionality

Talk to sales

free

45%

default cache hit rate

~4 ms

cache responses

1 line

to switch

Boost your RPC endpoints with one URL swap

No migration project or new SDK. Swap back anytime.

Create your Boost endpoint
Paste the endpoint URL you already use with any provider. We hand you a Boost URL.
Swap the URL in your app
Replace the old provider URL with the Boost one and redeploy. Swap back anytime.

Boost my endpoints

Built for regulated environments

The controls and paper trail your security review expects, ready before it starts.

SOC 2 Type II

Audited controls, with reports available under NDA.

Credentials encrypted

Provider URLs and headers are encrypted at rest. Replace or remove them anytime.

Reorg-aware

Cached data follows your provider's view of the chain, picking up reorgs within about 100ms.

Verifiable responses

Every response carries a cache-status header, so you can audit exactly what we served.

No lock-in

Turning Boost off is the same one-line change as turning it on.

Standby providers

Keep backup providers on file per chain and switch the active one when you need to.

Ready to shrink your RPC bill?

Boost my endpoints

Read the docs

Frequently asked questions

What is Boost?

Boost is a cache and global CDN that sits between your app and your RPC provider. When your app asks for blockchain data Goldsky has already indexed, Boost answers directly in milliseconds. Everything else is forwarded to your provider exactly as you sent it, and the response comes back exactly as they answered it. You keep your provider, your credentials, and your contracts. Boost just answers the repeat questions before they reach your provider.

What does it cost?

Boost is free for a limited time. If pricing is ever introduced, it will always be a subset of the proven savings, so your total RPC bill only goes down.

There are no usage fees for cache hits or requests forwarded to your provider. Enterprise is available for teams that need committed support response times, uptime SLAs, custom configurations, private networking, or other advanced functionality.

Do I have to switch RPC providers?

No, and that's the point. Boost works in front of whichever provider you use today. You tell us where to forward requests, swap one URL in your app, and everything else stays the same. If you ever want out, swap the URL back and you're done.

Which RPC providers are compatible with Boost?

All of them, as long as the endpoint is reachable over https. Alchemy, QuickNode, Infura, dRPC, Nirvana Labs, Ankr, Chainstack, a node you run yourself — if your app can call it, Boost can front it. Providers that authenticate with a bearer token or API-key header work too: custom headers are configured once and applied to every forwarded request. You can even put Boost in front of Goldsky's own Edge RPC.

What changes in my code?

One URL. Point your RPC client at your Boost endpoint instead of your provider's, and you're running. Boost speaks standard JSON-RPC, so viem, ethers, foundry, and every other client work unchanged.

How do I know the responses are correct?

Anything time-sensitive, like latest, pending, safe, or finalized reads, always skips the cache and goes straight to your provider. Cached answers come from Goldsky's indexed blockchain data, which follows your source chain and picks up reorgs within about 100 milliseconds. And every response includes a header that says whether it came from the cache or your provider, so you can verify us from your very first request.

What happens when the cache doesn't have an answer?

The request forwards to your provider byte-for-byte, and the response comes back untouched. Forwarded requests are free. A miss costs a little latency, never correctness.

Which chains and methods are supported?

Boost caches historical reads at concrete block heights: blocks, transactions, receipts, and logs. Tagged reads like latest and pending forward to your provider, as does every other method. See the docs for the full list of supported networks and RPC methods.

How is Boost different from Edge RPC?

Edge RPC is Goldsky's fully managed RPC service: we run the endpoints, routing, and failover for you. Boost keeps your current provider in place and adds a cache in front of it. They work well together, too: you can use Edge RPC as the provider behind Boost.

Does Goldsky populate its cache with my requests?

No. Goldsky populates Boost's cache from our own internal indexing workloads and the chain-level indexing that powers Turbo and other Goldsky products. Boost customer requests and response data are not used to build the cache.