Architecture & trust model

How a request actually flows through Triport — from your client, through the edge and routing layer, to an upstream node and back — and an honest account of what Triport operates versus what it routes to.


Type	Triport platform overview
Network	Solana \| Ethereum \| Polygon
Authentication	n/a — conceptual reference

What Triport is

Triport is a multi-chain RPC gateway: a single authenticated endpoint (https://triport.io) that authenticates your key, enforces your tier's rate limits, routes each call to a healthy upstream node for the target chain, and returns the upstream result unchanged.

It is deliberately not presented as a sole-owned global validator network. Triport operates its own edge and routing infrastructure and a pool of Solana RPC hosts, and routes to a curated set of upstream nodes — some Triport-operated, some vetted infrastructure partners — chosen per chain and per method for health and latency. Calling it a gateway/aggregation layer is the accurate description.

Request lifecycle

Code

client
  │  POST https://triport.io/<chain>   (key via x-token / Bearer)
  ▼
┌──────────────────────────────────────────────────────────────┐
│ Triport edge (multi-region: EU + US)                          │
│  1. TLS termination (Cloudflare → origin)                     │
│  2. Auth — resolve API key, scope, and tier                   │
│  3. Rate limit — per-tier RPS + burst (per category)          │
│  4. Route — pick chain + a healthy upstream from the pool     │
└──────────────────────────────────────────────────────────────┘
  │
  ▼
┌──────────────────────────────────────────────────────────────┐
│ Upstream node pool (per chain / per method)                   │
│  • Triport-operated Solana RPC / cohort hosts                 │
│  • Vetted infrastructure partners for EVM + specialty methods │
│  • Health-checked; unhealthy hosts are taken out of rotation  │
└──────────────────────────────────────────────────────────────┘
  │
  ▼
upstream JSON-RPC result  ──►  returned to client unchanged

What each layer does

Layer	Responsibility	Notes
Edge	TLS, request intake, auth, rate limiting	Runs in more than one region; the EU PoP is primary today. Auth headers are stripped before forwarding (your key is never sent onward).
Router	Select chain and a healthy upstream	Routing is per-chain and, for some chains, per-method (e.g. heavy reads, trace, mempool may use different upstreams than standard reads).
Upstream pool	Serve the actual chain RPC	A mix of Triport-operated hosts and infrastructure partners. Unhealthy hosts are removed from rotation by continuous health checks; the pool is refreshed periodically.
Response	Return the upstream result	Triport does not rewrite successful results — what the node returns is what you get. Triport adds rate-limit headers and standardized error envelopes (see Errors).

What is and isn't guaranteed

Result fidelity. Successful upstream results are passed through unchanged.
Auth isolation. Your API key is validated at the edge and never forwarded to upstream nodes or echoed in responses.
Health-based routing. Upstream selection prefers healthy, low-latency hosts; failed hosts are taken out of rotation.
Honest scope. Triport advertises Solana, Ethereum, and Polygon for RPC. Crypto payments additionally settle over BSC and Tron — that is a payment-rail set, not an RPC chain set (see Billing).
Not claimed. Triport does not claim to own every node it routes to, nor a full independent validator/archive network across all chains. Where archive or specialty capability is served by a partner, it is still delivered behind the single Triport endpoint and SLA.

Regions & failover

Triport runs edge infrastructure in multiple AWS regions (EU primary, US secondary). DNS for triport.io is fronted by Cloudflare. Within a region, the router fails over between upstreams in the pool when a host degrades. Cross-region active-active routing is available on higher tiers (see Rate limits & tiers); single-region accounts are pinned to their nearest PoP.

Streaming

WebSocket and gRPC streaming (Solana pubsub, Yellowstone gRPC, EVM mempool feeds) ride the same auth and routing model but hold a persistent connection to an upstream stream source. See the Streaming section for the per-surface details (proto versions, filters, and delivery semantics).