The way Meteor works is that the client side framework is bundled with your code and pushed to the browser of the end user, it's this pushing of the merged fram

The way Meteor works is that the client side framework is bundled with your code and pushed to the browser of the end user, it's this pushing of the merged framework + your code that counts as distribution under the GPL. The code isn't just run server side. Also you should read the following sections of the GPL faq which should help clarify your understanding of the issues: http://www.gnu.org/licenses/gpl-faq.html#WhatCaseIsOutputGPL http://www.gnu.org/licenses/gpl-faq.html#WhatCaseIsOutputGPL (the output of a GPL program is also GPL "when the program copies part of itself into the output.") http://www.gnu.org/licenses/gpl-faq.html#MereAggregation http://www.gnu.org/licenses/gpl-faq.html#MereAggregation (linking doesn't have to be in the compiler sense of the term any form of tight coupling between code is covered)