One RPC integration.
No provider stack to manage.
Managed EVM JSON-RPC service for production teams.
SolidRPC owns upstream diversity, routing, failover, monitoring, and recovery. Use this pack to structure a technical evaluation and procurement review.
This is a review template, not a contract, certification, or performance report. Print this page or save it as a PDF from your browser.1. Service overview.
Your application connects to SolidRPC. We manage the upstream operations behind that integration. Coverage is specific to the network, RPC method, and historical range. Validate the requests you depend on before migration.
- Standard service
- Managed RPC routing and recovery, API keys, usage reporting, and support access.
- Account-specific agreement
- Capacity, limits, price, billing arrangements, support commitments, and applicable SLA coverage.
- Engineering review
- An initial workload review is free. Any paid evaluation, special deployment, security control, or recovery commitment is scoped and agreed separately.
2. Public security and supplier facts.
SolidRPC, Inc. provides the service. Review the current company page and service terms for company and contractual information.
- API keys can be viewed and revoked through the dashboard. They must be treated as secrets.
- Enterprise accounts support SAML single sign-on (SSO), company sign-in enforcement, and role-based team access.
- Password authentication uses hashed passwords. Dashboard authentication uses signed tokens.
- Application releases and infrastructure configuration use version control and automated deployment workflows.
- Automation follows action-specific policies. Engineers remain accountable for the service.
- Recovery coverage varies by network and data type. Agree requirements before commitment.
See security practices and privacy and data handling. Required certifications, data restrictions, access controls, and recovery objectives need explicit confirmation.
3. Workload review worksheet.
Prepare the following without API keys, private endpoint URLs, or personal data from your users.
| Area | Your input |
|---|---|
| Application | What the product does and why RPC reliability matters |
| Coverage | Networks, method mix, historical depth, HTTP or WebSocket needs |
| Traffic | Average and peak calls/s, burst duration, concurrent connections |
| Current operations | Provider coordination, routing, incident response, and maintenance work |
| Decision | Engineering owner, commercial owner, security reviewer, target date |
| Requirements | Capacity, budget, support, security controls, and procurement constraints |
4. Evaluation and handover template.
Agree the scope and fill in the thresholds before the test begins. Leave unknown results blank.
| Check | Definition to agree |
|---|---|
| Coverage | Exact networks, methods, block ranges, and expected response semantics |
| Completion | Successful eligible calls / attempted eligible calls, with exclusions and errors listed |
| Latency | Client location, load, p50/p95/p99, sample count, and test window |
| Freshness | Reference, permitted lag, and measurement cadence |
| Capacity and cost | Sustained and burst load, usage units, limits, included usage, and overage |
| Decision | Results, gaps, named owners, acceptance decision, and next action |
| Handover | Staged cutover, rollback criteria, support contacts, escalation, and agreed service terms |
Evaluation measurements are distinct from contractual SLA calculations. Use the applicable SLA terms for contractual definitions.
5. Materials and next step.
- Trust and procurement index
- Network coverage and integration documentation
- Security practices, privacy, terms, and SLA terms
- Talk to an engineer about your workload and review requirements