a month ago
Hey Railway team, i want to deploy Telegram's official MTProto Proxy (the reference implementation Telegram publishes for their own protocol) on Railway.
Before deploying, I wanted to confirm if this is compliant, the Acceptable Use Policy's catch-all clause prohibits "operating proxies or anonymization services," and I wanted to make sure an official, protocol-specific Telegram proxy doesn't fall under that before I provision it.
Could your team clarify whether this is allowed? thanks
3 Replies
a month ago
We don't pre-approve specific workloads as compliant. The published terms at railway.com/legal/fair-use and railway.com/legal/terms govern what's permitted, and you'd want to review those to make your own assessment before deploying.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
We don't pre-approve specific workloads as compliant. The published terms at [railway.com/legal/fair-use](https://railway.com/legal/fair-use) and [railway.com/legal/terms](https://railway.com/legal/terms) govern what's permitted, and you'd want to review those to make your own assessment before deploying.
a month ago
yeah i know you cant pre approve, but atleast i want clarity because in the docs it has been mentioned that if you are not sure then ask the team. I just want to know whether its straightaway deny for deploying this service, or it depends on the workload?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
It's not a straightforward deny. Whether an MTProto Proxy deployment is permitted depends on the specifics of the workload, for example whether it's intended for personal/private use or as a public-facing proxy, and at what scale. Could you share more about how you plan to use it (who will connect, roughly how many users, and whether it will be publicly advertised)?
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved a3a • about 1 month ago