Trust and safety
Railway's approach to trust and safety aims to protect users and infrastructure while keeping legitimate workloads running. When Railway restricts your resources, it explains what happened, what's affected, and what you can do next.
What isn't allowed
In practical terms, you must not use Railway for:
The Acceptable Use Policy also prohibits reselling compute resources, evading usage or billing limits, and running bots or scrapers that violate applicable terms of service.
You're responsible for what you host and how your applications are used. These examples summarize the rules, but don't replace the Acceptable Use Policy or Terms of Service.
If you're unsure whether your workload is permitted, ask through Central Station or email abuse@railway.com before deploying.
How Railway evaluates abuse
Railway uses automated detection and reviews abuse reports to identify suspected policy violations. Reports can come from users, rights holders, and security organizations.
The aim is to stop the abuse with the narrowest effective action while avoiding unnecessary disruption to legitimate workloads. For example, action against a compromised service can be limited to that service rather than the entire workspace.
What happens when Railway detects abuse
Railway either restricts the affected resources or bans the workspace.
A restriction limits part of what you can do, such as deploying a service or managing a domain. You keep access to your dashboard, where you can see what's restricted and what to do next.
A ban is reserved for serious or repeated violations of the Terms of Service. It blocks access to your account and takes every service in the workspace offline.
How restrictions affect your workspace
A restriction can affect an individual service or domain, a particular feature, or an entire workspace.
Depending on the restriction, Railway may limit certain actions, prevent new resources or deployments, or take running services offline. The restriction details explain what's affected.
What happens after a restriction
Most restrictions follow the same path from notification to resolution.
Check your notifications
By default, Railway sends you an email and an in-app notification whenever a resource is restricted.
Review the restriction
The restrictions page in your dashboard shows the recorded reason, affected resources, and consequences.
Resolve or appeal the restriction
Some restrictions have a specific resolution, such as upgrading to a paid plan. Others require an approved appeal before they can be lifted.
Redeploy stopped services
After a restriction is lifted, you may need to redeploy any services that were stopped.
If your account is banned, you only see the Account suspended page when you sign in. That page shows the recorded reason and, when available, the option to appeal.
Submit an appeal
If you believe a restriction was applied in error, use the appeal option in your dashboard when it's available. Restrictions remain in effect while an appeal is reviewed.
A useful appeal explains what your workload does, addresses the stated reason for the restriction, and describes any changes you've made. Follow the guidance for asking for help: include relevant resource IDs, logs, and code links where applicable. Check that your claims match what happened, and remove secrets or unrelated personal details before submitting.
You can generally appeal a restriction once, and the appeal decision is final. Not every restriction can be appealed. Follow the resolution instructions shown in your dashboard.
Report abuse or infringement
Report suspected abuse or trademark infringement to abuse@railway.com. Include the affected URLs and a description of the issue.
If you own copyrighted material or represent its owner, you can submit a DMCA takedown notice.