惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Last Week in AI
Last Week in AI
阮一峰的网络日志
阮一峰的网络日志
P
Proofpoint News Feed
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
MongoDB | Blog
MongoDB | Blog
云风的 BLOG
云风的 BLOG
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
J
Java Code Geeks
WordPress大学
WordPress大学
T
The Blog of Author Tim Ferriss
V
Visual Studio Blog
小众软件
小众软件
Microsoft Azure Blog
Microsoft Azure Blog
博客园_首页
IT之家
IT之家
Vercel News
Vercel News
C
Check Point Blog
Google DeepMind News
Google DeepMind News
月光博客
月光博客
D
DataBreaches.Net
酷 壳 – CoolShell
酷 壳 – CoolShell
美团技术团队
Y
Y Combinator Blog
Hugging Face - Blog
Hugging Face - Blog

PostHog's RSS Feed

Training our own AI models - PostHog From 270GB RAM to 5GB: Moving local flag evaluation from Django to Rust The best analytics stack for vibe-coded apps The do's and don'ts of minimum viable product marketing - PostHog The best MCP servers for startups, by workflow 4,063 errors closed without a human opening PostHog – here's what we learned - PostHog PostHog Code and the self-driving product - PostHog Why attacking your competitors online is dumb - PostHog The best real-time analytics platforms for developers, compared DuckDB vs ClickHouse: Why we use both at PostHog - PostHog PostHog's next chapter - PostHog Making Claude Cowork actually useful - PostHog PostHog vs Matomo in-depth tool comparison You're doing lifecycle emails wrong Untangling Tokio and Rayon in production: From 2s latency spikes to 94ms flat The best HIPAA-compliant A/B testing tools - PostHog A beginner's guide to testing AI agents - PostHog I hate the standup bot (so I built an agent to do it for me) - PostHog The best CDPs for developers, compared The best error tracking tools for developers, compared The best feature flag software for developers, compared 7 best session replay tools for mobile apps 7 best free open source business intelligence tools right now 7 best free and open source LLM observability tools PostHog vs LogRocket in-depth tool comparison The most popular PostHog alternatives, compared Open source (and self-hosted) session replay tools - PostHog The 9 best GA4 alternatives for apps and websites - PostHog PostHog vs Google Analytics 4 in-depth tool comparison How we built automatic clustering for LLM traces - PostHog
Why we're giving away 100 times more cloud usage, free - ...
James Hawkin · 2021-05-17 · via PostHog's RSS Feed

Today, we're announcing that we're giving away 1 million ingested events/month on Cloud, for free. That's up from 10k/month that we were offering before.

Gee, thanks subtitle!

The magic of an open core business model is that giving away stuff for free often helps us make money.

Behold the virtuous circle:

  1. Create a valuable free product and a community around it. Collaborate with the community. The free product gets more valuable and more popular as a result. The community grows faster and faster.
  2. Larger companies using the free product think the paid product looks valuable. They email asking to buy PostHog Scale or they increase their usage to 10s or 100s of millions of events/month.
  3. Get money from paid product, to get even more money from venture capitalists, go to step 1.

We noticed in user interviews that a subset of our user base were self-hosting product analytics purely for cost reasons. Typically:

  • Small startups/hobby projects/charities
  • Up to a few thousand users monthly
  • Very little budget for product analytics or hosting product analytics
  • No need to self-host product analytics for privacy reasons

If the above is you, you can of course keep going with PostHog Open Source.

However, for most users that fit the above criteria, we'd recommend Cloud because:

  • No need to run updates
  • No hosting costs at all
  • You're likely to get an experience with fewer bugs if your usage is a little bit higher/grows

If we're doing our jobs right, your (!) product may get really popular. Oh no!

We sell to you when you get to this "champagne problem". Word of caution: it qualifies as humble bragging if you come to us because you're getting too popular ;)

When your product is successful, you'll usually have more event volume, and a larger team - you will need features around collaboration or even compliance if you become a big enterprise one day. At that point, you'll want PostHog Scale.

Serious sidenote: we don't lock you in - we're working on making our Open-Source product much more scalable, so you can at least do the basic analytics even with very high usage, without spending anything. That'll come later in the year.

We require a card to unlock the full 1m events/month.

It costs quite a bit to provide this free usage to people, so this felt fair to us. A little friction here ensures people place some value on product analytics so we don't end up with very poorly engaged users - this would create a lot of noise for us in judging how our own retention is performing, which makes it hard to judge what to build. Some users will go past 1m events/month in which case we don't want extra friction in our own sales process, although really for PostHog - we focus on PostHog Scale to drive revenue.

How easy is it to move from one edition of PostHog to another?

Current open source user -> PostHog Cloud?

If you are currently hosting PostHog Open Source and having read this would rather use PostHog Cloud for greater simplicity and enhanced reliability, then it may make sense to move. First of all, check above if you are one of the users we are targeting with this change.

We haven't built a way to automatically migrate your data over - that would have been non-trivial to build, and we didn't want to bottleneck releasing this change. However, after talking with many of you - our recommended way to migrate is this:

  • Set up PostHog Cloud now
  • Send events to PostHog Cloud and your self-hosted instance in parallel
  • Switch off your self-hosted instance once you've enough data built up to be useful in Cloud (around 3 months is what most people do)

PostHog Cloud -> PostHog Open Source in future

In future, you may want to self-host your analytics again as your product takes off - when increased volume and privacy needs both drive you to want to self host.

We don't have plans in the immediate future to build a feature for this as we've other urgent items to get built first that will benefit more users. You could use our APIs, but in reality - we'd recommend running both systems in parallel for a couple of months then switching one off.

The exception is if you wish to move to PostHog Scale (paid), in which case we provide extra support to migrate your data.

PostHog Cloud -> PostHog Scale

You can do this - we provide a little manual support in this case. Just contact us.

Does this mean PostHog is focusing more on cloud then?

Oh subtitle, you couldn't be more wrong.

A key goal is to provide a more reliable PostHog for all users.

We view Cloud as a way of generating awareness (charging high volume cloud users to cover its hosting costs) and improving scalability, and Self-Host as a way of generating high volume users that we retain very well and who may end up paying one day.

For those that self-host, we are putting a ton of engineering work into enabling ClickHouse in our open source product. That means users that self-host will be able to use PostHog at much greater scale, bug free, for free or paid depending on which features they need.

For teams with smaller volume and less of a focus on user privacy, this is where today's change comes in.

Existing customers should get treated just as well (or better, from time to time!) than new customers.

We've therefore already applied this increase to any customers who are paying per event on Cloud. Yep, that cost us a bunch of money. But it's the right thing to do.

After all, PostHog's mission is to increase the number of successful products in the world.

PostHog is an open source developer platform that helps people build successful products. We help you debug and ship your product faster.

Want to just try it already?

(Sorry for the shameless CTA.)