I publish templates on Railway — 64 of them, mostly fixed versions of broken starters in the catalog (Flask, NestJS, Rails, Ghost, Twenty CRM, Superset, n8n). My workspace was permanently restricted today for a ToS violation, and support has confirmed the decision is final. I am not appealing it here. I am posting because two things led me straight into it, and they will lead the next person into it too.

The Fair Use Policy is invisible at the moment it applies.

I built a fixed version of the Telegram MTProxy template, published it, and deployed it twice to verify the card. Nothing in that flow — the template editor, the publish dialog, the deploy screen — mentions that proxies are prohibited. There is no checkbox, no link, no category warning. I read railway.com/legal/fair-use for the first time in the email telling me my workspace was restricted. The line is unambiguous: "operating proxies or anonymization services". Had it been shown anywhere before publishing, I would have stopped.

The catalog says the opposite of the policy.

Open railway.com/deploy?q=mtproxy right now:

Telegram MTProxy — 2,893 deployments, 2,710 active, 44% health

Telegram MTProto Proxy — 1,505 deployments, 1,397 active, 92% health

Teleproxy — "Self-hosted Telegram MTProxy with advanced Fake-TLS and anti-DPI features"

SEVO Panel — "VLESS panel over WebSocket + telegram mtproxy"

That is roughly 4,100 proxy instances running on Railway, from templates that have been listed for months and are one click from deploy. When the storefront sells a category, people reasonably conclude the category is allowed.

What I would like to see

Show the Fair Use Policy in the publish flow, and ideally check the template's category against it before the card goes live. A single dialog would have prevented this entirely.

Make the catalog consistent with the policy. If proxies are prohibited, the existing proxy templates should not be searchable and deployable — otherwise every deployment of them is a violation their authors and users don't know about.

For template authors, consider a warning before a permanent restriction on a first violation. I unpublished my card before anyone asked me to; there was no path from that to keeping the account.