> What is a transparency problem? It’s when a solution being closed source creates distrust between the client and vendor. Eterprises don't care that much abou

> What is a transparency problem? It’s when a solution being closed source creates distrust between the client and vendor. Eterprises don't care that much about code. And if they do, business continuity clauses may alleviate most of their closed source concerns. After all, how many financial firms switched to OpenOffice Calc from Excel? > She argues that Amplitude is pretty expensive, particularly prohibitive for some early-stage companies, and larger companies could save a fortune by using an open-source version. While this pitch might resonate with early-stage companies, those same price-conscious early-stage companies will either use an open-source version or a free tier. AWS' go-to-market (GTM) hinged on attracting startups and individual developers by offering them low cost (metered) services. They got this part very right, because Airbnb, Stripe, Twitch et al went on to become large enterprises and grew alongside AWS. There's not many things that can compete with low cost / free. You can always move upmarket later. Just ask ARM and Intel. For dev tool upstarts, open source has become the defacto GTM (it isn't, as TFA rightly points out, a business model). So, unless you're Snowflake level good (and you can fend off FOSS shops like Databricks), you're better off with an open core model.