Rollup Gateway
A reference control plane for managing tenant access to blockchain API services.
Rollup Gateway is not a rollup node or a rollup-provisioning system. It is a control-plane reference for teams that need to manage organizations, projects, API keys, usage plans, credits, and configurable blockchain API integrations around their infrastructure.
The implementation is in Rollup Gateway. It demonstrates how an administrative console, authenticated management API, tenant data model, metering, and upstream request routing can fit together. It deliberately leaves the actual validator, rollup, and RPC deployment system outside that control plane.
What it is responsible for
| Concern | Gateway responsibility | Infrastructure responsibility |
|---|---|---|
| Tenant administration | Organizations, projects, teams, and API-key lifecycle. | Identity and access controls for underlying nodes. |
| API access | Authentication, quotas, usage plans, and request accounting. | RPC capacity, request validation, and backend health. |
| Billing integration | Credits, plans, and payment integration hooks. | Financial controls, compliance, and production payment review. |
| Endpoint records | Store the configured endpoint associated with a managed service. | Provision, secure, monitor, and retire the actual endpoint. |
Deployment boundary
Treat the gateway as one layer in an API product, not a security boundary around a chain. Its credentials, upstream configuration, payment integrations, and authorization rules need their own review. A valid API key must not grant broader infrastructure authority than the API route requires.
Before using a similar design in production, test authorization failures, quota exhaustion, upstream timeouts, retry behavior, audit logs, and revocation. Pair it with the Monitoring guidance so a control-plane success response is not confused with a healthy rollup or RPC backend.