You can now use PostHog for X less #8218
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@lottiecoxon Putting this on your radar. This will need some kind of custom art, but I don't have a good idea personally. Give it a read and see what you think. @joethreepwood might have an idea when he's back tomorrow. |
|
@jamesefhawkins Are you still planning to move forward with this piece? I think it'd be great if we had an article from you for when we do the louder announcement, but if you're unlikely to have time then I'll start drafting something up instead. |
|
Tracking some info on those remaining bits to add:
|
Co-authored-by: Raquel Smith <[email protected]>
contents/blog/cheaper-analytics.md
Outdated
| | 250M | $0.0000150 | $0.0000187 | | ||
| | ∞ | $0.000009 | $0.00001 | | ||
|
|
||
| (we can offer further discounts if you are beyond 250M events/month regardless - at that scale, we suggest you talk to us) |
There was a problem hiding this comment.
Is this line necessary? Makes me wonder why we'd even list a price at this level if we just go ahead and discount but not be transparent about the discount.
Maybe replace with:
| (we can offer further discounts if you are beyond 250M events/month regardless - at that scale, we suggest you talk to us) | |
| (we can offer further discounts for those paying more than $2k/mo on an annual contract - at that scale, we suggest you talk to us anyway) |
|
Comparisons are difficult because so few alternatives publish pricing. The only data I have is for Mixpanel, up to 20M events. I've added a chart which includes that. |
Co-authored-by: Raquel Smith <[email protected]>
contents/blog/cheaper-analytics.md
Outdated
| * Events with person properties cost a lot more for us to ingest and query. Allowing customers to choose to not send person properties for certain event types means we can cut our own costs of providing our product to our customers. | ||
|
|
||
| * This aligns our interests with our customers, and means we can make a positive margin on all events ingested (beyond our free tier), so it is sustainable but not greedy! |
There was a problem hiding this comment.
| * Events with person properties cost a lot more for us to ingest and query. Allowing customers to choose to not send person properties for certain event types means we can cut our own costs of providing our product to our customers. | |
| * This aligns our interests with our customers, and means we can make a positive margin on all events ingested (beyond our free tier), so it is sustainable but not greedy! | |
| * Because events with person profiles cost a lot more for us to ingest and query. Allowing customers to choose to not send person profiles for certain event types means we can cut our own costs of providing our product to our customers. | |
| * This aligns our interests with our customers, and means we can make a positive margin on all events ingested (beyond our free tier) so it is sustainable but not greedy! | |
| * We do hope to lower the person profiles cost at lower volumes in the somewhat near future. |
Restores @raquelmsmith's suggestion
There was a problem hiding this comment.
Can we be more specific about how we're going to reduce person profile costs? It'll be more credible if we can explain why we're doing to achieve this.
Changes
A few more bits to add in
Plan for context: