free hosting ends March 25, 2016

mLab Free Sandbox (used to be MongLab).

I agree. Packages demos should have a dedicated free tier, only for them. Indeed they benefit all.


They got rid of concept of having limited functionality spot instances "… we’ve unified the flexibility of utility pricing with every Galaxy feature into a single product that scales with your app and business needs.

1 Like

I just leave it here.
Quick and simple redirect guide. Found somewhere. For me it’s handy…

1). $ meteor create redirect-app
2). remove all files, leave just .meteor folder
3). create server.js file
4). paste the code:


  .use(function(req, res, next) {
    var location = REDIRECT_URL;
    res.writeHead(301, {'Location': location});

5). $ meteor deploy


I do welcome paid service because that means more ‘for-profit’ Meteor projects will be born.

However, as I am only checking out Meteor I am already stuck at MongoDB deployment stage.

  1. I have subscribed for Galaxy.
  2. I have subscribed for MLab.

Now MLab asks me: Provide URI for a cloud-accessible MongoDB

I really expected it to be that simple as:

meteor deploy myproject

(with config pointing to mLab)


meteor deploy myproject --dataprovider=mLab

As I suspect it is not a matter of weeks of months to make that easy it would be great to have Meteor To-Do Tutorial have clear Step 13 - Deployment. Meteor Guide talks about Deployment but it does not provide example of pushing database to cloud and connecting it with Galaxy either.

At the moment does not work for Windows and and other tutorials like are empty

Hopefully educational resources will catch up with the pace of change soon.

Update: I have taken Windows advice from Galaxy deployment DEPLOY_HOSTNAME is not recognized but my login/pass do not work. Maybe it is related to the fact that I am registered as part of organization?


If “it’s never go away” refers to deploy and not the free tier, then this is about as poorly worded as the Second Amendment. But surely I’m not misreading the part in blue too?


At this point I think we can all agree that MDG pulled a 180 on this one. Is it a permanent 180, who knows. Meteor is really tight lipped about their plans, especially infrastructure plans. While I thoroughly support their decision because I think it is what is best for everyone, they really went about it wrong!


I think we’ve seen in the last few months, that MDG has serious communication problems, an example we find in the Blaze/React thread where we’ve waited a long time for an official statement. I’ve just hoped that MDG learned from it and changed it’s communication level, but as we see, this didn’t happen (yet?).

I’m not using the free meteor service, but it is distressing to give all users only 2 weeks. Normally all people in management positions should know, that 2 weeks are ridiculous for a professional company which targets are professionals. What will happen if Galaxy isn’t profitable as expected? Will such users also get only 2 weeks until the service will be closed? If you say no, I think we can’t trust on that answer, because nobody knows, how
reliable MDGs statements are…


Completely understandable. When they suggested “it’s never going away” I’m pretty sure they didn’t anticipate such a huge drastic uptake in usage.

If they’re wasting a lot of money on it, for no reason other than showboating, it’s a good thing they removed it. Focus that money elsewhere and improve Meteor itself. We can pay for hosting ourselves.


I’ll clarify… “MDG doesn’t owe me anything” in that I haven’t paid them for a service or software at any stage. Therefore, I can’t expect too much in return.

I’m in the same position as you, I have taken more from the community than I have given. That’s partly a time constraint, partly because I found keeping pace and providing any real value challenging enough as to not bother.

I whole heartedly agree with your second point. That, is my fundamental upset.

I certainly don’t write that much here in the forums, but this time I feel I would like to highlight a few things about the latests MDG announments(including this one). All my opinions come from the perspective of a developer who understands what is to make a business sustainable and also from the perspective of someone who loves all the technology that MDG offers for free:

  1. Besides how good you are in bringing really cool tech to the table, I feel that your communication skills are somehow damaging the public opinion in some posts, and this has been spotted here in the forums multiple times:
  • Ther’s a huge difference in terms of communication depending on the author of the post. Since you have many great and loved communicators at MDG, I would only allow them (one or two would be enough) to do all the important announcements, because they make sure to get to the point without being too pushy or cold, and knowing how to please most of the readers.
  • It would always be good to have a small chat talk with a few community contribuitors before throwing this “bomb posts”. As someone already said, MDG is becoming popular for “what are they going to say in their next announcement?”(for good and bad). By talking to an external environment first, I think you would have to worry less about the final impact, and you won’t have to retreat from your original statements (like with Blaze or here giving hosting to well known package creators)
  1. Regarding the decission of shutting apps down, I’m not currently affected, so it’s easier for me to understand and support your decission, while there are many things that in my opinion could have been done in a better way:
  • Extend duration to at least summer.
  • Give a free period of time(2-3 months) to every package uploader with a limit of 1 container and no database (can be created easily at mLab if needed) which is more or less like a special trial. Once the free trial ends, renew the subscription for another X months based on the package downloads/likes on atmosphere.
  • Let X people from the community collaborate with MDG and make proposals for free “forever” test sites (those considered to help hugely in the adoption of the technology), rather than a list that might get spammed and filled with not always useful sites.
  1. Replace/Update the planned features Trello board. I think by now the Trello board is totally outdated, and I thought it was a terrific idea when it was used. Things like Uservoice or Trello can be really useful to match the needs of the industry/community/MDG etc. So if you are receiving input from many sides, I think all of them deserve to know what is being proposed or suggested at the overall level and your thoughts about it. (This is a simple as having X colums in trello one for community features, another from partners, another for MDG strategic features, … and then move the cards to a “Doing” column and sort them with priority tags). In this way, everyone could see what are you working on, where does the feature request come from and how likely is to be implemented. I don’t mean this board has to be the holy grail, but If people would have seen a card with “migration from free hosting to galaxy plan” in your column with a high priority, It would have helped to avoid such a dramatic reaction with this and many other matters.

P.s. Having said that, and after working with them for a a few weeks(checked many Meteor related things for improvement), I think NodeChef offers a cool hosting solution for those willing to pay less than the Galaxy entry point (and also eliminates the database creation hassle)


I only really used the free tier option for a couple of demo apps but it was definitely one of the things that attracted me to Meteor in the first place.

There’s already a lot of discussion about the short notice, the poor communication, all the great demo package apps that will be lost after this happens so I won’t go into this.

But I must say, I’m really surprised at this decision, simply from a business point of view more than anything else. I mean, obviously not being an employee, I have no idea how much the free hosting costs or what MDG’s future plans are so maybe if I had more knowledge it would make sense.

But as far as I know, MDG makes no money from Meteor. Their entire business model is in Galaxy which means that they’re positioning themselves to be the best company to host Meteor apps.

So with that in mind, why would they not have some sort of free tier, even if it’s a severely restricted one? It’s the perfect way to tie meteor to Galaxy and get every new developer using Galaxy from the get go. Now, every new developer is going to setup free hosting with something like Heroku while they learn and evaluate Meteor.

And then when they discover it’s awesome and start creating real Meteor apps that require professional hosting, well then they’ll probably just upgrade to a paid Heroku plan because it’s what they know and it already works for them.

Maybe the free hosting IS just prohibitively expensive, but I would’ve thought their entire current business model is dependent on it.


I wrote only one app on * - it was but it helped me many times to provide the best learning resources for Meteor framework to young Meteor adepts. It’s sad that it will go away!


… and they’ll have it up and running, ready to upgrade; and they’ll have sorted out a deployment solution and gotten used to it, blowing away Galaxy’s main selling point; and they’ll be paying substantially less for equivalent performance. Own feet successfully blown up.

For that matter I find it utterly incomprehensible why Galaxy doesn’t provide databases, even if it’s on a separate instance. It’s like they don’t understand their own framework/stack.


I respect the decision to charge money for a service, but why would you give just two weeks notice when your public docs only recently said this would be free forever? And no tools to help us estimate the cost/month should we move existing simple apps to one of the Galaxy services (e.g., I have no idea what $.0035/hour means for my small volume app - does that mean < $2.50/month since there is some way to know < 1 instance at a time runs?)

Two weeks notice (less for me - I just checked my email today to find I have only 11 days - and I feel bad for the poor bastards who are still on vacation and don’t yet know) is not a reasonable amount of time, will be very disruptive, and you are going to loose a chunk of your community if you follow through with this. I’m really hoping you change your timelines and add some planning tools to help existing customers make an informed decision.

On a personal note, I just built my first ever web site on Meteor (for about 40 of us that play in a racquetball ladder) and it’s been working fine for the last few months (save occasional short-term Mongo outages on, but this is a side-project for me and not sure if/when I’ll have time to try to migrate it in the next 10 days. And I know there are larger scale players that have bigger bets on the free tier (e.g., I’m just finishing up a series of Coursera classes on Meteor development which use the free site quite heavily for student created peer-graded assignments).

So what prompted this abrupt timeline for change? Is MDG in financial trouble?


The far more disturbing thing about this whole discussion is actually not even anymore the announcement itself. I find it more disturbing that within 3 days of the announcement nobody from MDG has thought it would be a good idea to respond and address all concerns properly.

@sashko talked about this in one of the transmissions that he dislikes these articles with shitty headlines that put meteor in a bad light but then you’re doing it yourself. The damage has been done but instead of fixing it you don’t clarify and respond to the community within 3 days. You can’t be surprised people write shit about MDG on hackernews if you can’t reply about one of the most major core decisions of your business within 3 days.


I don’t have much to add to this conversation as I’ve only hosted using * once.

I’ve been experimenting with creating packages and stuff, and as everyone knows, going to atmosphere and checking out a package at is for sure the most satisfying and helpful tool for developers to check out the usage of the package.

Besides that though, I don’t mind the removal of the free hosting. I think I took it for granted when it obviously hasn’t been good business practice for MDG.

If they can find a way to allow package developers to still free host, I think a large chunk of Meteor users will still be happy


Just posting to formally register my agreement that giving people two weeks notice is pretty crappy given previous proclamations that free hosting will always exist. I understand that businesses need to change to survive but are MDG haemorrhaging money that fast that two weeks notice is all they can give before flicking the off switch?

If MDG make this type of massive change at very short notice for free hosting it makes me worry about hosting my apps on Galaxy for fear of getting a polite letter after 6 months telling me my bill will be tripling in two weeks time, signed off with “Thanks for using Meteor and best of luck on migrating your projects from Galaxy”!

1 Like

I personally would like to know the reasoning for the short notice


I agree, and I won’t bother with my theories because that’s all they are, theories. I will say that I support the general decision, but not the short notice. I would also say that hopefully they’ll put the data on ice for a while while they sort out what decisions are being made regarding Community package docs, demos and other important websites on *