# RPC Plane > Your provider is up. Your data is wrong. RPC Plane is a Solana RPC reliability infrastructure provider. It routes requests across multiple RPC providers a team already uses, adding health scoring and automatic failover. RPC Plane is an infrastructure company providing a reliability layer for Solana RPC access. It offers a self-hosted proxy that routes requests across multiple RPC providers a user already has accounts with, applying slot-aware health scoring, circuit-breaker failover, and write broadcast. It targets trading desks, wallet and dApp backends, indexers, and infra teams that need consistent RPC responses, not just provider uptime. The project addresses a gap in how RPC reliability is measured: uptime metrics track HTTP response codes, not data correctness, so a provider can report healthy status while returning stale slots, corrupted cache results, or transactions that never land. RPC Plane runs as a sidecar, speaking standard Solana JSON-RPC so existing tools work unmodified. It does not intercept traffic or hold provider credentials, since routing happens at the application layer using credentials the user supplies. The offering is tiered around one routing engine. The core binary is a source-available, self-hosted proxy that performs routing and failover and runs at no cost. A hosted dashboard adds observability, including provider health history, cost analytics, and alerting, built on optional telemetry. A managed cloud option, still in development, would run the proxy on the provider's behalf via a web interface. RPC Plane positions itself as a neutral layer above RPC providers, used by teams running trading systems, wallets, indexing, and other Solana infrastructure. - Type: Company - Sector: Infrastructure - Status: Active - Founded: 2026-06-01 - Profile: https://thegrid.id/profiles/rpc_plane ## Products - [RPC Plane Binary](https://thegrid.id/profiles/rpc_plane): RPC Plane Binary is a self-hosted Solana RPC proxy that routes requests across multiple RPC providers a user already has accounts with. It runs as a single Rust binary alongside an application, scoring provider health in real time on latency, error rate, and slot freshness, then failing over automatically through circuit breakers when a provider degrades. Developers and trading, wallet, and indexing teams point their existing Solana client at a local endpoint to gain multi-provider routing, slot-drift detection, and parallel write broadcast without changing their application code. (RPC Provider, Live, Main Product) - [RPC Plane Cloud Dashboard](https://thegrid.id/profiles/rpc_plane): RPC Plane Cloud Dashboard is a hosted observability platform for teams running the RPC Plane binary. It ingests lightweight telemetry from the self-hosted proxy to display provider health history, per-method cost analytics, request explorers, and failover and error logs across every connected RPC provider in one interface. Teams use it to diagnose provider degradation, track spend by method and provider, and set alerts, while their provider credentials remain on their own infrastructure. (Developer Tooling, Open Beta) - [RPC Plane Managed Cloud](https://thegrid.id/profiles/rpc_plane): RPC Plane Managed Cloud is a planned fully managed Solana RPC service that runs the routing engine on RPC Plane's own infrastructure instead of a user's servers. It will expose a dedicated tenant endpoint, letting users add provider credentials and tune routing policy through a web interface without deploying or scaling their own proxy. The service is intended to store provider keys encrypted, enforce per-app rate limits and access policy at ingress, and support team access with single sign-on. The offering is in development and accessible only through a waitlist. (RPC Provider, In Development) ## Links - [Main](https://rpcplane.dev) - [Terms of Service](https://rpcplane.dev/terms) - [Documentation](https://docs.rpcplane.dev) - [Privacy policy](https://rpcplane.dev/privacy) - [GitHub](https://github.com/rpcplane/rpc-plane) - [Twitter / X](https://x.com/RPCPlane) ## Legal This data is provided under two licensing models. Model 1 - open data. The open data core is licensed under the Open Database License (ODbL) — a copyleft/share-alike license allowing free use, modification, and sharing for any purpose. Attribution is required: include "Powered by The Grid" linking to https://thegrid.id wherever the data is used. Derivative databases must be shared under ODbL terms. Trademarks, logos, and brand names (marked "Special TPIP") are not covered by the ODbL. For ML/AI use: training datasets that substantially extract ODbL data are Derivative Databases and must be shared under ODbL if publicly used; models must be attributed in documentation. Model 2 - commercial licenses. The Grid Data Service (TGDS) is also available as a commercial license. See [Web Services Terms](https://about.thegrid.id/legal/web-services-terms) for commercial use that is not covered by the open data service. The following applies to both licensing models. - All data is provided AS IS with no guarantees of accuracy. - The Grid does not provide investment, legal, or tax advice, and - a project's presence in The Grid's data does not imply endorsement. - [Data Licensing & Disclaimers](https://about.thegrid.id/legal/data-licensing-and-disclaimers): Licensing models and disclaimers - [Open Data (ODbL)](https://about.thegrid.id/legal/open-data): Open Database License terms and scope for The Grid's open data service. - [Attribution Guidelines](https://about.thegrid.id/legal/open-data-attribution-guidelines): How to attribute The Grid's data when using the open data service. - [Web Services Terms](https://about.thegrid.id/legal/web-services-terms): commercial Terms for using data services. - [All Legal Documents](https://about.thegrid.id/legal): Full index of terms, policies, and disclosures ## Optional - [TGS Field Descriptions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-field-descriptions.md): Schema field definitions for The Grid's data model - [TGS JSON Structure](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-json-structure.md): Data model structure and relationships - [Product Type Definitions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-definitions.md): Definitions for each product type - [Product Type Classification](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-classification.md): Guide for classifying products into types - [Grid MCP Guide](https://github.com/The-Grid-Data/workspace-public/blob/main/grid-search/skills/grid-query/references/grid-mcp-guide.md): How to query The Grid programmatically via MCP