Design: Usage-based pricing

[paolodamico]

As discussed in https://github.com/PostHog/ops/issues/67, we'll launch a new pricing strategy more similar to other SaaS companies. As such we need to think of a new design for the cloud section of the pricing page, and discuss implementation later.

As a side note, I would consider the possibility of going back to cloud vs. self-hosted (i.e. dropping the OSS distinction) to simplify things a little bit more. Let's look at the data here too :)

[lottiecoxon]

Could I possibly have some examples of how other companies deal with this layout in a successful way - I think my lack of tech language/knowledge is holding me back here. Alternatively I can look at our competitors (mixpanel, amplitude etc) to see how they structure this

[corywatilo]

For additional context, we played with the pricing page for my Superday and one of the things I tried to tackle was reducing from 3 tabs to 2, specifically for the sake of simplicity.

Figma mocks (You can click between the Self-hosted and Cloud tabs.)

This doesn't tackle the usage-based pricing aspect (nor is the actual design anywhere near up to snuff), but figured I'd share the above mocks for how we may be able to reduce from 3 tabs to 2.

[paolodamico]

Re @lottiecoxon, absolutely! here are a few examples that come to mind,

• https://stripe.com/pricing
• https://aws.amazon.com/api-gateway/pricing/ (this one is quite complex, but AWS is definitely dev-focused so worth considering)
• Almost any other product analytics, data warehouse, or API processing.

Re @corywatilo, this is great, and I think this is a great opportunity to bundle all changes and implement them together!

[paolodamico]

This has been addressed elsewhere