Hello Railway Team,

I hope you’re doing well.

I’m currently deploying a Node.js + EJS based video conferencing application on Railway, and I would like some clarification regarding a few technical limitations I’m encountering.

Application Overview

My application includes the following key features:

Real-time video and audio streaming between multiple users using WebRTC (Peer-to-Peer)

Screen sharing and session recording (FFmpeg)

A built-in chat system for participants

Secure authentication and session management

TURN/STUN server integration for reliable connections behind NAT and firewalls

Issues Encountered

While testing on Railway, I noticed:

UDP ports (like 3478 for TURN) seem to be blocked.

I cannot run persistent background services such as a Coturn server.

No static public IP is available for stable signaling.

Media traffic (audio/video relay) occasionally fails behind firewalls or restricted networks.

My Questions

1. Is there any way to open or proxy UDP ports for TURN/STUN communication on Railway?

2. Can we run a coturn service alongside the main Node.js app within Railway’s infrastructure?

3. Is there an alternative or recommended solution for WebRTC media relay under Railway’s network environment?

4. Do you plan to support applications requiring persistent UDP connections in future?

If possible, please suggest the best approach to deploy this kind of WebRTC-based app on Railway or any service integration you recommend for TURN/STUN handling.

Thank you for your time and support.

Looking forward to your response.