<story><title>The Deno Company</title><url>https://deno.com/blog/the-deno-company</url></story><parent_chain><item><author>qbasic_forever</author><text>How does this business model survive Amazon AWS making a blog post, &amp;quot;Here&amp;#x27;s a template to run your deno code on Lambda!&amp;quot;?  They&amp;#x27;ll never beat AWS on costs in the long term.  They can burn VC cash to stay afloat and try I guess.</text></item><item><author>srmarm</author><text>Looks like &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;deno.com&amp;#x2F;deploy&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;deno.com&amp;#x2F;deploy&lt;/a&gt; will be a managed service - the implication seems to be that the default option will be to use their CDN to run code with an option to DIY if you prefer.</text></item><item><author>franciscop</author><text>Nice to see! How do they plan to monetize? I either became blind or missed it somehow. The article does say how they DON&amp;#x27;T plan on monetize:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    &amp;quot;Rest assured that Deno will remain MIT licensed. For Deno to grow and be maximally useful, it must remain permissively free. We don’t believe the “open core” business model is right for a programming platform like Deno.&amp;quot;
&lt;/code&gt;&lt;/pre&gt;
There are some hints though:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    &amp;quot;If you watch our conference talks, you will find we&amp;#x27;ve been hinting at commercial applications of this infrastructure for years. We are bullish about the technology stack we&amp;#x27;ve built and intend to pursue those commercial applications ourselves. Our business will build on the open source project, not attempt to monetize it directly.&amp;quot;
&lt;/code&gt;&lt;/pre&gt;
Does anyone have some insight into those? I haven&amp;#x27;t watch any Deno talk (maybe one actually?) so it feel a bit strange to make people watch technical talks to find hints of the monetization strategy.&lt;p&gt;PS, if I was a rich investor I&amp;#x27;d throw money at this project even as a donation, so no complain at all, but I&amp;#x27;m very curious on the monetization plan.</text></item></parent_chain><comment><author>carlosf</author><text>Lambda has a ton of caveats and limitations... but it seems their platform is full of limits as well:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;deno.com&amp;#x2F;deploy&amp;#x2F;docs&amp;#x2F;pricing-and-limits&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;deno.com&amp;#x2F;deploy&amp;#x2F;docs&amp;#x2F;pricing-and-limits&lt;/a&gt;&lt;p&gt;AWS sucks hairy balls at providing things that are simple for developers to use, so that could be their competitive advantage, but I&amp;#x27;m just guessing here.</text></comment>
<story><title>The Deno Company</title><url>https://deno.com/blog/the-deno-company</url></story><parent_chain><item><author>qbasic_forever</author><text>How does this business model survive Amazon AWS making a blog post, &amp;quot;Here&amp;#x27;s a template to run your deno code on Lambda!&amp;quot;?  They&amp;#x27;ll never beat AWS on costs in the long term.  They can burn VC cash to stay afloat and try I guess.</text></item><item><author>srmarm</author><text>Looks like &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;deno.com&amp;#x2F;deploy&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;deno.com&amp;#x2F;deploy&lt;/a&gt; will be a managed service - the implication seems to be that the default option will be to use their CDN to run code with an option to DIY if you prefer.</text></item><item><author>franciscop</author><text>Nice to see! How do they plan to monetize? I either became blind or missed it somehow. The article does say how they DON&amp;#x27;T plan on monetize:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    &amp;quot;Rest assured that Deno will remain MIT licensed. For Deno to grow and be maximally useful, it must remain permissively free. We don’t believe the “open core” business model is right for a programming platform like Deno.&amp;quot;
&lt;/code&gt;&lt;/pre&gt;
There are some hints though:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    &amp;quot;If you watch our conference talks, you will find we&amp;#x27;ve been hinting at commercial applications of this infrastructure for years. We are bullish about the technology stack we&amp;#x27;ve built and intend to pursue those commercial applications ourselves. Our business will build on the open source project, not attempt to monetize it directly.&amp;quot;
&lt;/code&gt;&lt;/pre&gt;
Does anyone have some insight into those? I haven&amp;#x27;t watch any Deno talk (maybe one actually?) so it feel a bit strange to make people watch technical talks to find hints of the monetization strategy.&lt;p&gt;PS, if I was a rich investor I&amp;#x27;d throw money at this project even as a donation, so no complain at all, but I&amp;#x27;m very curious on the monetization plan.</text></item></parent_chain><comment><author>tnolet</author><text>There are many, many companies competing with AWS on products that strictly speaking AWS also has.&lt;p&gt;I mean Zoom has no right to exist because you can use Chime?&lt;p&gt;There is always room for better UX, better support, different approach etc.</text></comment>