Gateway RPC
Public, managed, and dedicated RPC access for supported blockchain networks, with capacity, regions, observability, support, and service commitments defined by the selected plan and agreement.
- What it is
- Connectivity service
- Current posture
- Available for supported networks
- What varies
- Architecture, providers, operating scope, and commitments
An endpoint is simple. Depending on it is not.
Applications, wallets, reporting, and operations inherit the availability, latency, consistency, rate-limit, network, and incident behaviour of their RPC layer. Gateway RPC makes those dependencies visible and gives eligible workloads a defined service boundary.
Keep the core authoritative.
- Applications and wallets
- Reporting systems
- Operations tooling
Change the capability at a controlled boundary.
Gateway RPC changes the boundary, not the institution’s authority.
A known connectivity model
Choose published, managed, or dedicated access for a supported network and workload.
Capacity with context
Define request patterns, methods, rate limits, regions, scaling, and fair-use behaviour for the selected service.
Operations around the endpoint
Scope telemetry, alerts, escalation, incident communication, support, and service-level commitments.
What Gateway RPC contributes. What still needs a decision.
Published access
Use current public endpoints and published limits for supported networks where available.
Managed endpoints
Configure authenticated access, request policies, capacity, and operational visibility for eligible workloads.
Dedicated capacity
Scope isolated infrastructure, regions, scaling, and performance objectives for the target workload.
Network coverage
Select from currently supported networks and methods; compatibility is confirmed against the application.
Observability
Review available request, error, latency, capacity, and service-health telemetry for the selected plan.
Support and service levels
Record coverage hours, response targets, availability commitments, and exclusions in the applicable agreement.
Continue from Gateway RPC into the operating model.
Bring the requirement. Define the Gateway RPC boundary.
A focused workshop maps the target capability, existing systems, providers, controls, and deployment variables.