Whether to display pricing on the website is something we debated in the past, and continue to debate. (Your comment may wake up the debate for me.)<p>Pricing for analytics services (in the marketplace) is all over the map. Google picked $150K&#x2F;year as the price for GA  Premium because that&#x27;s the low end of an Adobe Analytics contract, who is the market leader. We&#x27;re typically cheaper than existing Adobe&#x2F;GA contracts. Non-competitive &quot;event analytics&quot; companies like MixPanel and Heap have variable per-event pricing that would break the bank for the customers we serve. We have a bit of an aversion to per-event pricing because it feels like &quot;punishing customers for success&quot;.<p>Meanwhile, per seat pricing, though attractive on the surface and popular in the SaaS segment, has several concerns in our space. First, we want customers to feel free to hand out access to our platform: part of our value proposition is democratizing access to analytics data. So we don&#x27;t want &quot;stingy seat quotas&quot; typical with tools like Salesforce. Second, for an analytics tool, seats are a bit easier to &quot;hack&quot; for a pricing model -- though our dashboards can be customized per user, a single shared account can access all the data. Meanwhile, our costs don&#x27;t scale with seats, but with site traffic&#x2F;users instead.<p>For these reasons, and more, we&#x27;ve settled on &quot;tiered pricing&quot;. Roughly speaking, our service is offered in three tiers. Each tier supports a larger class of site (more monthly uniques), which also bestows more features (e.g. more data retention in higher tiers). To work within the budget constraints of some companies, we will discount tiers while removing cost-affecting features, e.g. maybe you are in the highest class of site, but we disable API access and limit data retention. Because this is a tad more complex than a pricing page could express easily, and also because we think the value of the product comes through best in a guided demo, we made the decision to hide pricing and instead responsively provide demos on-demand.<p>So, the tl;dr is, pricing, and the display of it, is definitely something we think about, and we have (IMO valid)  reasons for not displaying pricing right now, but you make a fair point: if Musk can price his rockets publicly, maybe we can figure something out, too :)