We are planning to host a real-time chatting and communication platform with integrated call features. This platform requires consistently low latency and predictable packet delivery. During testing, using WebSockets over TCP introduced high and unstable latency due to TCP retransmissions, head-of-line blocking, and congestion control, which are not suitable for real-time audio communication. These issues cause noticeable delay, jitter, and degraded call quality. Real-time call technologies rely on UDP-based protocols (such as RTP/WebRTC) specifically to avoid these limitations and maintain low-latency communication. Without inbound UDP support, hosting this platform on Railway is not feasible, despite Railway otherwise being an ideal hosting environment. Native inbound UDP support with configurable ports would unlock real-time communication platforms, call services, and other latency-sensitive workloads.