Solana Archival RPC
unmatched performance for a fraction of BigTable price
We host our proprietary ArchivalRPC server, engineered for both cost efficiency and high performance. This solution eliminates the necessity for the costly
Google BigTable dependency that has been standard since the inception of Solana.
Our services cater specifically to high-demand applications such as RPC Providers and data indexers. We provide options for both shared archival instances and, for more intensive needs, dedicated instances. Each plan includes dedicated resources, including external load balancers, ensuring each client operates within an isolated ArchivalRPC environment. We do not impose restrictions based on credits or bandwidth.
For further details, you can refer to our documents. Or dig deeper in our GitHub.
Our services cater specifically to high-demand applications such as RPC Providers and data indexers. We provide options for both shared archival instances and, for more intensive needs, dedicated instances. Each plan includes dedicated resources, including external load balancers, ensuring each client operates within an isolated ArchivalRPC environment. We do not impose restrictions based on credits or bandwidth.
For further details, you can refer to our documents. Or dig deeper in our GitHub.
Dedicated resources
No limitations
No RPS enforcements
100% opensource
| Method | BigTable+DefaultRPC | HBase+ArchivalRPC |
|---|---|---|
| getTransaction | 400-800ms | 5-25ms |
| getBlock | 400-800ms | 100-200ms |
| getBlocks-10k | 30-40sec | 30-40ms! |
Performance
We are committed to both cost optimization and performance enhancement. By relocating our database from commercial cloud environments, which often come with multiple layers of networks, we inherently improve performance. However, our strategy extends beyond this.Our ArchivalRPC server is designed to be significantly more efficient than traditional heavy validators that are typically used for RPC services. This allows it to process more requests per second (RPS) with reduced demands on CPU and RAM.
We are continually developing our ArchivalRPC server with a clear objective to reduce all RPC request response times to below 20 milliseconds. We are approaching this target, demonstrating substantial progress in our performance goals.
