I moved off of Galaxy for now :(

I really hope it can be get better. The main reasons were:

  • no production MongoDB option (life is more difficult that way)
  • stability issues getting things to deploy properly (issues with push to deploy, too much work otherwise)
  • to expensive for the non-free option with no MongoDB

Competitor charges $9/mo, push-to-deploy simply works, super easy.

The ideal is: write an app. Push to deploy. Nothing more.

1 Like

Can I ask where you moved to?

Hey @trusktr, sorry to hear that.

Ideally: write an app. Push to deploy. Just it.

We plan to get there. We are evaluating how we could provide MongoDB for production. Possibly we will create integrations with other service providers, but this is still in the research phase.

About the P2D issues, I remember helping you with an issue in the past that got resolved. Did you have any new problems? It would be nice to know more details about this.
Our support team can always help with specific issues at support@meteor.com.
And I’d be happy to help you personally if you email me at fred@meteor.com.

1 Like

I went to NodeChef for now. Push to deploy is working great first try, plus with Mongo DB included, so that was really easy.

My only gripe with NodeChef so far is that...

when payment doesn’t happen with credit card on a Friday, there’s no way in the UI to pay with credit card again and you’re not gonna get a hold of anyone all weekend, and are gonna have a weekend-long downtime unless you make a PayPal account. The UI accepts only PayPal payments during this scenario. Really weird. lol.

Will be great!

Did you have any new problems

We did, but rn I don’t remember. Sorry I’m not so helpful here. Will be glad to try again later and report new issues.

1 Like

I’m not a paid user of gallaxy as it’s not providing anything more than a scalable app.

I created everything on digital ocean as I trust their uptime. I really don’t like devops and could be happy to be in gallaxy but it’s current features are not good enough.

This page is showing what should gallaxy be
Meteor.js Hosting | Lightning Fast Meteor App Hosting | Deploy Meteor.js to NodeChef Cloud

only mongodb is not enough for many, scaling both mongo and redis are big requirements. Besides that using s3 on gallaxy could be a plus.

1 Like

I’m using AWS for my app, MongoDb Atlas and Redis (at Redis itself). I prefer to leave MongoDb and Redis to the best experts out there, which is the companies that own and run their software.

AWS hasn’t given me any trouble, I’m using CodePipeline which works seamlessly to build and install new versions of my frontend or backend app. Upscaling and downscaling is obviously part of AWS, so it’s all in your configuration files or via their UI (which has gotten a lot better than it was some years ago).

Also all 3 companies provide 7x24h service, with different higher (paid) service levels should problems occur and you really need an expert to work on them.

I’m running my own company and I don’t understand why some owners of small companies don’t work a couple of hours over the weekend or holidays to fix urgent problems of users or at least communicate back to them. The customer should always come first but maybe that’s again a personal preference.


I will add my bit here too. I recently also moved away from Galaxy (to AWS).

  1. price - Galaxy compact container (512 MB RAM) is $29, while on AWS, the nano container is $4 (512 MB RAM).

  2. prerender - there is no control and it got really frustrating at some point (the pages were not being recached and google console kept complaining about it). I tried to set up my own account, but that was frustrating too and I could not somewhat fit in the free tier (which was likely my mistake) and the next cheapest option was $99 (there are other cheaper competitors though). So I moved away from prerendering to SSR and I am very happy about it.

  3. mongo - not really an issue for me. I was ok with the Atlas free tier. My app is quite small and have only a few documents in the DB.

  4. no naked domain redirect. I had to set up pizza.redirect. It worked well in the end, but it was another thing to care of. It is simple to setup in MUP without 3rd party redirects.

  5. APM - it is not a part of the essentials package. I am only trialling it for now, but MontiAPM is $0/$5 compared to $11 on Galaxy. I like that I can try it out for free first and if I am interested to keep ~1 week of logs, only then to start paying.

  6. Information about cost is difficult to find or make sense of because of a 3rd party subscription provider. In AWS, you get estimates, current cost and very detailed breakdowns.

I don’t use P2D or scaling for my apps yet. I liked the Galaxy deployment process and displaying the logs on the web and basic monitoring (monitoring RAM in AWS is complicated and costly). It is also much easier to manage it than the whole AWS infrastructure. I had a lot of expectations from the included prerendering, which was the major reason to try Galaxy, but that was not working for me.


Sounds good man, when your app goes large and you have traffic then AWS will be a burden also so I recommend getting a dedicated server in that case. But not until the bills are over $1k a month or it wont make sense