Live matrix sourced from the gateway provider contract.
rpc-fabric
Public web on Vercel. RPC edge on a real host.
This site is the public surface for your RPC business. The actual multichain gateway stays on a long-lived Docker host where HTTP, websocket RPC, health checks, and project-scoped routing belong.
Live target
Gateway base URLhttps://rpc.swivy.dev
LivenessThe operation was aborted due to timeout
ReadinessThe operation was aborted due to timeout
Provider statusThe operation was aborted due to timeout
Last checked: 5/16/2026, 1:54:07 PM
Networks with every known upstream marked healthy right now.
Networks advertising websocket transport through the public contract.
The public site reads the same pass-through model Swivy and other clients consume.
Network matrix
Live transport availability
No network data is available yet. Once the gateway is configured, this page will render the provider metadata and live status feeds.
Integration shape
What clients connect to
HTTP RPCConfigure the gateway first
WebSocket RPCConfigure the gateway first
Provider statusUnavailable until the gateway URL is set
Why this split works
Vercel for web. Dedicated host for RPC.
Vercel app
- Public landing page and onboarding surface
- Live provider and network status from the gateway contract
- Links into the gateway login and docs
Gateway host
- HTTP and websocket RPC ingress
- Project auth, usage, limits, and upstream failover
- Prometheus metrics and readiness gating
Upstream layer
- Alchemy or other providers at first
- Your own EVM and Solana nodes later
- Per-project upstream pinning when customers bring nodes