RailwayReviews of railway.com

Bad service. I payed for a 'hobbie' plan, and now it says that my trial has ended! Contacted 'support', just a dumb bot. I had my server there, so it not just ruined my experience, it ruined my income as well Time to go away.

Railway restricted my workspace, “Io Tradingview’s Projects,” and denied my appeal on 30 September 2026. On 1 October, support confirmed that it would not reactivate services, provide a database dump, grant read-only volume access, or offer another route to recover the data. The workspace contains business records and personal data. This inability to migrate is disrupting my business. I am requesting immediate preservation and either restoration or a secure export following appropriate identity and ownership verification. I will update this post when Railway provides a substantive response or recovery route.

I have been using Railway since 2022 and I had spent a considerable part of my last 8 months learning the platform from the ground up, from templates, to environment variables and all the way to the API, deployments, networking, databases, etc. I was working on a legit, open source project, namely the discovery of popular projects on GitHub, and the creation of valid Railway templates for these projects to be able to be deployed easier on Railway. I was going to create approximately 100 templates of popular open source projects. I took a lot of time on this as I really did enjoy Railway and wanted to learn its platform and getting some templates in there that would be useful. I was then banned from my account. I filed an appeal and detailed the project I was creating and how I would be using Railway. The appeal was rejected and Railway went on saying that the decision was final. This is what I find the most troublesome is I still don't know what I did wrong. I've questioned about any activity that caused the ban, such as API/GraphQL requests, CLI usage, template research, automated activity, etc, but haven't received any particular explanation. I understand that Railway has rules and the right to enforce them. When I have broken a rule I would like to find out what activity the rule was related to so I can learn about it and not do it again. Being banned for months for no clear explanation after months of learning and building about Railway has been very disappointing. I really enjoyed Railway and spent a lot of time getting to know about the platform. I hope Railway will communicate better with developers when their accounts are terminated, particularly if the developer is seeking to better understand what went wrong.

Our workspace access was disabled, leaving critical production services and data inaccessible. We supplied identifying details and requested urgent read-only access or an export, but received no substantive recovery path. This disrupted active Australian business operations. I will update this review if Railway restores access or provides the requested export.

We used Railway to host ordinary Australian ecommerce infrastructure, including web applications, APIs and PostgreSQL. Our workspace was abruptly disabled. We submitted a detailed appeal explaining what each service did and asked Railway to identify the exact project, observed conduct and Terms provision relied upon. The denial arrived 6 minutes and 46 seconds after the automated acknowledgement and did not answer those questions. Railway can identify this case from the account email beginning with bensem and ending in the digits 2311. The exact Railway project ID has been supplied privately through Trustpilot. I have intentionally not published the full address or project identifier. The most serious issue is access to our data. Our production Postgres volume was last shown as READY with approximately 1.2 GB used. Railway also sent us a notification stating that a pre-maintenance snapshot for that exact production database would be retained for 30 days. We explicitly told Railway it could keep every public service, deployment and automation disabled or quarantined. We asked only for a preservation hold and either temporary read-only access or a provider-created pg_dump so we could recover order, payment-reconciliation, fulfilment, customer-support and audit records. As of 29 August 2026, Railway has not confirmed preservation, snapshot availability, a deletion deadline or a data export. Providers should investigate legitimate security alerts. They should also provide a real human escalation and a safe data-return path instead of exposing a customer to irreversible data loss through a rapid, opaque decision. I will update this review if Railway assigns a human case owner and provides a safe export.

My workspace got disabled for "violating TOS". There's no proper way to contact support properly, only through their forums which can be public. I asked what I violated and they kept saying we cannot share it, I also asked if there is an email, which doesn't exist either. Horrible support.

They have charged $150 over several months, even though I was only trying it for one month. I cancelled the subscription. Their website or something went wrong, so it wasn't logged. They then sent countless promotional emails, so the invoice emails were buried. It's UNBELIEVABLE how these companies operate.

We used railway to host some of our custom apps. After over 1 year of usage, our account was suddenly closed due to "suspected phishing." We weren't doing any of that, instead hosted our own apps and some client apps. Despite giving detailed information about the usage, we received the feedback that the account is closed and we shouldn't contact them again. From one day to the next, we lost access to our data, our own and our client projects were offline. No more access to get a final backup or anything. So if you want to be sure that you will actually be able to host and use your apps, don't go to railway.