a month ago
Hello Railway Support Team,
My workspace was restricted with the message “Suspicious activity detected.” I believe this may have been triggered by mistake, and I am requesting a manual review.
I am the legitimate owner of the workspace and use it to deploy my own faceless video generation SaaS MVP. The production environment contains a web/API service, an asynchronous BullMQ worker, and Redis. The application uses Supabase PostgreSQL for application data, Cloudflare R2 for media storage, third-party AI providers for script, image, and text-to-speech generation, and FFmpeg/Remotion for video rendering.
Repository:
https://github.com/remeber-recovery-code/faceless
The workload has only involved normal development, deployments, and a small number of single-video smoke tests. I have not intentionally performed scanning, spam, credential attacks, fraud, cryptocurrency mining, proxying, or any activity intended to harm Railway or third parties. All external provider accounts and API credentials used by the application belong to me or are authorized for my use. Provider calls are disabled whenever active testing is not required.
Please manually review the restriction and restore access if the automated security system flagged this legitimate workload incorrectly. I am happy to provide proof of repository ownership, architecture details, screenshots, logs, identity verification, billing verification, or other information needed for your review.
Please preserve the existing project, Redis data, deployment history, and environment variables while the review is in progress.
Thank you for your help.
3 Replies
a month ago
We're not able to share the specifics of why a workspace restriction was applied. This type of restriction does not clear through any self-serve action such as upgrading or adding a payment method, and we're unable to provide access to export data or environment variables from a restricted workspace.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
We're not able to share the specifics of why a workspace restriction was applied. This type of restriction does not clear through any self-serve action such as upgrading or adding a payment method, and we're unable to provide access to export data or environment variables from a restricted workspace.
a month ago
I still need help and would like this case to be reviewed by a human support agent.
This is a legitimate SaaS development project deployed from my own GitHub repository. Some coding, deployment, log inspection, and a small number of single-video smoke tests were assisted by an AI coding tool under my direct supervision. All actions were initiated and authorized by me.
The project did not perform network scanning, spam, credential attacks, proxying, cryptocurrency mining, or uncontrolled high-volume workloads. If normal deployment retries or worker activity triggered the restriction, I am willing to adjust the deployment process, rate limits, and resource usage.
Please escalate this case for human review. I can provide repository ownership proof, logs, architecture details, identity verification, or billing verification if required.
Thank you.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We appreciate the detailed context you've shared. Unfortunately, we're not in a position to disclose the specifics behind this restriction or to restore access to the workspace, its data, or environment variables, and no additional information or verification from your side changes that outcome. We understand this is frustrating, and we're sorry we can't offer a different path here.
Status changed to Awaiting User Response brody • about 1 month ago
Status changed to Closed brody • about 1 month ago