15 days ago
I am currently using Railway to host an n8n instance for use in my private MSP for my internal use. I am planning to offer automation servies to my MSP clients. My plan was to create their own n8n instance as a new project within my workspace. So each client would be their own Project inside of my railway account.
The clients would have zero access to railway or any of the backend, I am building and selling them specific automation solutions for their business use case. I would be billing them a flat fee for a end solution and not be billing them based on usage.
Does this comply with Railway's Terms of Service or do I need to revise my plan or find a different provider?
Thank You
2 Replies
Status changed to Awaiting Railway Response Railway • 15 days ago
15 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 15 days ago
15 days ago
Hey Andrew!
You are completely fine to do this. What you're describing actually fits perfectly within Railway's model and complies with their Terms of Service.
Railway doesn't have any restrictions against using their platform to host backend infrastructure for your own SaaS, agency, or MSP clients. Since your clients have zero backend access, aren't being directly re-billed for "Railway computing usage" as a reseller, and you are simply selling them a managed, flat-fee end solution, you're totally in the clear. Separating them into individual Projects inside your workspace is actually the best practice for keeping their data and private networks isolated.
The only thing to keep in mind is that since everything is under your account, you are ultimately responsible for the consolidated resource usage and the payment methods attached to that workspace. Other than that, you're good to go with your plan!
15 days ago
Your plan is VALID
- Complies with Railway's Terms of Service https://railway.com/legal/terms
Why It's Valid
Requirement : Your Setup
Client access: Zero backend access
Billing: Flat fee (not usage rebilling)
Project structure : Individual Projects per client
When It Becomes INVALID
- Give clients backend/Railway access
- Resell "Railway computing usage" directly
- Violate consolidated payment responsibility