Commercial usage using Hobby Plan
Hi,
I read somewhere quite a long time ago that Hobby plan is not intended to be used for commercial project. Does that rule still apply?
I read the ToS and it has nothinng about it.
Thanks!
Solution:Jump to solution
that's correct, as the name suggests the hobby plan is only to be used with hobby workloads, for anything above that the pro plan is needed
47 Replies
Project ID:
N/AN/A
Solution
that's correct, as the name suggests the hobby plan is only to be used with hobby workloads, for anything above that the pro plan is needed
Thank you @Brody, I will upgrade the plan in this case.
sounds good!
Sorry, one more question just to clarify: what if my current workload still does not require the pro plan? My billing usage is around $10 per month with the current Hobby plan (including waived fee)
if you dont have a pro workload and dont need anything from the pro plan then theres no reason to be on the pro plan
but there is often confusion around what is and what isnt a pro workload, so make sure you are aware that there is a line in the sand
So the limitation is not on the type of project (commercial vs personal/non-commercial) but it's more about workload requirements?
its both, if you are running a for-profit, commercial, etc service on railway, thats a pro workload
I see, understood. I think the ToS needs to be updated.
yeah there is a lot of room left for interpretation
Also, Brody, I don't think I believe this.
You seem to be answering most (if not all) the support inquiries (which is GOOD and thank you for that)
š
Thanks again
happy to help! š
also, if I upgraded to Pro and decided to downgrade again, will I still get the waived fee?
e.g. if one day I shut down the commercial project of mine
i cant see why not, the personal hobby plan is a separate workspace from pro
the waived fee bonuses are so good it's making me sad to let it go š
alright thanks, I'll be upgrading to Pro in the meantime just to comply with ToS
sounds good!
how do I switch the plan? shall I cancel my current plan first?
not unless you want to lose the waived fee
I am worried having downtime on my deployed services if I cancel my plan
there doesn't seem to be switch plan option
because it's not a switch, it's a new workspace https://railway.app/new/team
oh it's a separate workspace
so I can subscribe to both at the same time under 1 account?
after you upgrade you are asked what projects you want to move over, no downtime
I see, thanks. I'll try that link instead.
now I get what you mean by this
for context the link was copied from this page https://railway.app/account/plans
oh thats right. I didnt check that one. I went over to the billing section and clicked on "Manage subscription" instead.
fair assumption
Hi @Brody, sorry to bring this topic up again. I just talked to my other dev (we're just 2 people starting our own SaaS product), and we agreed to upgrade to Pro plan.
One feature that we'd like to use is region change.
However, we noticed that in the documentation it's said that there would be downtime:
Is there any estimation how long does it usually take?
We can't afford any downtime, especially during weekdays
depends on how much data you have in the volume
Ah okay it's kinda hard to determine, then. What if I have just about 50mb data in our MongoDB?
should only be 30 seconds or so then
sounds good
don't quote me on that though
I hope it does take that short amount of time
your volume most certainly isn't only 50mb
ah you're right, the data itself isn't a lot, just mere 30mb at max or so....
but the volume attached to MongoDB service is actually 5GB
we'll plan to migrate during the weekends instead then just to be safer
I highly doubt the volume usage is sitting at 30mb
I'm going to say somewhere around 250mb
you're right, the volume isage is a lot more than 30mb apparently
I was close enough
ok we'll plan it during the weekends instead. thanks again Brody!
no problem!
an update to this ticket in case anyone have some concerns regarding possible downtime during DB migration due to region switch: my 420mb MongoDB volume was migrated in just a minute or so.
the migration was seamless š
happy to hear that!!