Ironforge: Solana RPC load balancer, slot drift, firewall

Ironforge is a Solana RPC control plane. You add your own endpoints, then send app traffic through a project URL. Quick start: docs/get-started/quick-start. X @IronforgeCloud. Footer: Ironforge, Inc. The LST swap host sanctum-api.ironforge.network is a different product: Sanctum API.

Log into the dashboard. Add RPC endpoints. In Load Balancer, new project, pick those endpoints. You get an API key and an endpoint URL. Point the app at that URL. Then watch Analytics and Logs. Docs do not publish a public OpenAPI for the proxy itself.

Routing

Load balancer docs: Primary and Dynamic strategies, then per-strategy algorithms. Sequential: try endpoints in UI order until one succeeds. Parallel: fire all, take the first success (higher cost). Weighted: pick by weight, then failover set if the pick fails. Routing algorithms.

Slot drift protection watches how far an endpoint is behind the tip. Drift threshold is in slots (example in docs: 100). Exclude lagging RPCs on: drop them until they catch up. If every endpoint is lagging, the response is No RPC endpoints available. Off: Sequential and Weighted move laggers to the end; Parallel prefers a non-lagging success, else the least-drifted lagging reply.

Firewall, alerts, transactions

Firewall default is allow. Rules deny, rate limit, or log. Rank order: higher rank evaluates first. Alerts watch metrics (docs examples: landing under 90%, latency up 20%, uptime under 90%) and fan out to Slack, Discord, PagerDuty. Transaction pages cover landing rate, priority fee, compute units requested vs used, plus per-tx logs.