Hi Railway team 👋

We’re evaluating Railway for a fintech use case that integrates with Binance, which requires strict IP allowlisting and rate-limit management.

For this to work reliably, we need the following requirements confirmed:

1. Dedicated IPs
   • Each outbound IP must be dedicated to our account only (not shared with other customers)
2. One unique IP per service
   • We need the ability to assign a distinct static outbound IP to each service
   • No overlap (i.e., different services should not share the same IP)
3. IP stability
   • IPs must remain permanent and unchanged across: * Deployments * Restarts * Scaling (replicas) * Region consistency
4. No shared NAT / hidden routing
   • Outbound traffic should not be routed through shared gateways that could affect behavior or reputation
5. No unexpected rate limiting or throttling
   • We need clarity on any egress limits, bandwidth caps, or throttling policies
6. Scalability of IP allocation
   • Ability to provision and maintain at least 10 distinct static outbound IPs within our project

These requirements are critical for us due to Binance’s IP-based rate limits and whitelist restrictions.

Would appreciate confirmation on whether this setup is fully supported.

Thanks!