PostHog helps engineers build better products by combining product analytics, feature flags, session replay, a data warehouse, CDP and many more.
* open source, building a dev tool. We have a public handbook (posthog.com/handbook) if you want to learn how we work, pay and more in complete detail.
* we are a real business... nearly at $20M ARR / profitability in sight / lots of capital / grew revenue 4x last year but only added 3 people / just had first cashflow positive month in October this year!
* you decide what to build, and iterate with your users - we are growing through autonomy and transparency not through process.
* we have a ton of scale and a bunch of super interesting technical problems to solve
* we're building 50 more products over the next couple of years, so you could end up building one of those
* we need: product engineer, technical founder engineers, backend leaning full stack engineer
must say one of the most interesting applications I've had so far, even though I'm at the start. nevertheless, you made this process interesting and kinda even enjoyable. :)
hey (founder here), that shouldn't be happening, although this can take us some time (we get thousands of applications, although HN is a very high quality source) - could you email me james at our website.com? i'll double check what's going on.
We're an all remote company of just 50 with 8 products and significantly >$10M ARR. All inbound, no sales team. 70k companies have installed our software, 1,600 new companies install each week. Shipping tools to help developers build successful products.
We quadrupled our revenue, only added 3 people net last year, and now expanding as a result. We work in small teams, who fully own each product. Our engineers decide _what_ they will work on, not just _how_ to ship things.
See how our entire company works in a ton of detail at posthog.com/handbook, including how much we pay!
Hiring product engineers, a technical support engineer, a UX engineer, a distributed systems engineer, a site reliability engineer, and a community manager.
Please apply through our careers page on our website, or enter my email inbox lottery (james at you can guess it), but i would recommend the former!
Hi James, I applied for a full-stack role (focused on the backend), I just wanted to know if you are open to mid-level or if you're looking for a more senior. (I have ~3 years of experience)
Ah definitely email me then! If you are full stack but lean heavily front end and love taking pride in your craft / like working reactively based on what you think needs prioritising vs a more process oriented approach please email me!
(Founder) wanted to explain our intent behind the business… so here’s the origin story.
We tried to make the business work exclusively with self hosted and open source focus. I thought cloud would never work as we have so much competition. However we just couldn’t make hosting it at scale a good experience. We often have more data than customers production instances.
We wound up having to spend a ton of time debugging k8s in other people’s infra via screenshots. This wasn’t good for us or customers.
We kept having people hosting it themselves for no reason other than liking us so for the sake of a good experience for them, we made a cloud product. This represented the majority of users. It’s also cheaper for most people as we just have a big free tier and shared infra costs, so no hosting bill. Turns out cloud worked.
We didn’t want to abandon the OS project but we stopped trying to make money via an open core model. That means we call it a hobby instance because it just doesn’t scale very well.
> That means we call it a hobby instance because it just doesn’t scale very well.
Well you guys almost certainly operate posthog in Kubernetes yourselves. You either use a cloud-provided database, or you use a Kubernetes operator to run it on top of someone's infrastructure. Clickhouse, Kafka, whatever. They all have operators. I don't know when you adopted Temporal. Whatever. I may not be 100% right, but this is true in general.
The hobby offering doesn't have to scale poorly. It could scale just as well as your core offering. I am not saying you should, you are entitled to monetize something. It also doesn't have to be hard to install. You could author a Posthog CRD instead of using Helm as a low budget CRD. Maybe you already have that. Maybe your CRD exists as rows in some database and not in Kubernetes's dataplane. The interesting part of all of this is that you had an intuition that Kubernetes obsoletes a lot of the value proposition of traditional SaaS. The problem is figuring out, well, what IS the value proposition? People will endure a lot of brain damage to save on recurring costs, it is totally rational.
Another POV is this shows the limitations of Y Combinator's offering. It's true that enterprise sales goes way faster when it's startup CEO to startup CEO. Until you guys are worth billions of dollars, and even then, it's not 100%, your counterpart at a Fortune 1000 might be some CTO, some managing director with no real decisionmaking power. But he asks his team to pay the contractors in Pakistan to take the brain damage of self hosting Posthog and reimplementing your premium features, all because he cannot get meaningful approval for unlimited, use-based pricing, and then if you acquiesce to fixed pricing, you leave so much money on the table, and you sign up to dedicate a whole engineer to their customization and problems. While Kubernetes isn't to blame for this, it did make the Pakistan BANTA possible, and probably brought down pricing by a lot, hurting everyone trying to make good software for money. Very, very tough situation.
Something I can't really figure out is why Posthog hasn't gotten on Bitnami's (VMWare's) radar. Piwik and Matomo are. Mirantis has a great Kubernetes distribution, maybe the most painless one for people who are willing to take brain damage, and they could wind up doing this too. As always OSS is a value for someone else's thing that that someone else didn't pay for.
I can only tell you my experience as a newcomer to PostHog last year. I went to try it out, and visited the documentation to figure out how to get it up and running. The documentation sent a very clear message of “You’d be a fucking idiot to put this into production. The open-source version is pathetic and can’t handle real traffic. Pay us.”. This immediately killed all interest I had in PostHog and I didn’t go any further. Your open-source version doesn’t have to scale indefinitely, but if you can’t stand behind your open-source version at all, I don’t trust your commercial version at all either. A closed-source product is preferable to an open-source product where the maintainers strongly warn people not to use it.
This is well said and I agree. It is disingenuous and raises cognitive dissonance to offer something but not stand behind it and in fact warn people NOT to use it.
(Founder) we wanted to be able to capture questions on each page of our docs - so someone learning about our JS SDK (for example) could see questions about it under the main docs content, to try to avoid people missing gotchas.
In general we invest a ton in the website as we don’t do sales - it is our sales team!
And in future we anticipated building ie merch rewards for people that answer questions, people about to submit blog posts and stuff all through the same login… community based things. This is all pie in sky at moment but we’re going to experiment with it.
It seems that you want to take this under your wing because you think that this could be a key differentiator / value provider for you. Nice to see an example in the opposite direction to the outsourcing craze.
we mainly do this because it can just help with getting PRs approved if we want to fix an issue in something we rely on (and it is nice / we can list as a perk), and a little influence can be very valuable if we want to give feedback on a project's direction. doesn't do much on the growth side as far as i'm aware, for us at least.
Yikes, I'm the founder of this company (one of my colleagues wrote this piece) - just saw it appear here. We shipped a rather huge change to the website recently (we're trying to let other people post stuff too), think we accidentally made it janky and missed this. Will fix when the right person wakes up - he's west coast US! Sorry for QA via HN :)
FWIW, fully a quarter of the screen is taken up by fixed position elements that are entirely irrelevant to a reader. When I see this on sites I want or have to use, I add cosmetic rules to delete the sticky elements. When I see it on sites I don't have to use, I close the tab.
I don't claim that this makes it a net loss for you from a money standpoint, nor that I'm representative of a majority of your market, but I _do_ suspect I'm the sort of potential customer that isn't easily studied in an A/B test.
If you're talking about that obnoxious left sidebar, I agree. The table of contents widget on the right too. The article itself is squeezed between a bunch of shit I don't want to look at. It makes the page feel crowded and like it's trying to get me. Please just let us read the content! If it's any good, it'll speak for itself.
1. Just be yourself, proudly. Some people _will_ hate it, others will love it. Getting product market fit is so damned hard, you are way better off looking for a smaller number of people that love you.
2. I'd shoot for 5 reference customers (paying list price, using it as you'd expect and genuinely delighted). Along the way I'd track who you try to sell to in a spreadsheet (including those that just drag on and never close) and I'd score them across the behaviors/things you would expect your target audience would have in common. This will help you create an Ideal Customer Profile - which you can then target more and more heavily (where you do marketing / what you build next and so on in future). Be _very_ specific not just ie by industry. For example, paypal targeted ebay power sellers in the early days.
3. Absolutely not. I've more than 40K customers at my startup and I live in a village no one has heard of in the UK.
4. Don't worry about scaling up via marketing until you have 5 reference customers (and generally do more of what got you the first 5 as your first step)
5. Read Secrets of Sandhill Road to understand the VC model more deeply. If you bootstrap - you have total control, might make more if you sell (because of how preferred shares work) but it will probably cause you more personal financial stress. Decide what motivates you - lifestyle business or trying to build a $10bn company. VC is an irreversible door, more or less, whereas bootstrapping isn't. I'd default with bootstrapping if unsure.
> Absolutely not. I've more than 40K customers at my startup and I live in a village no one has heard of in the UK.
Haha this made me check your profile — don't know if it's quite fair to say PostHog is proof that you don't need to be in SV to succeed given that you guys went through YC and also started in a remote-first (mid-pandemic) world.
ok that is fair - going to SF frequently but not living there is something i should have been clearer on!
my cofounder and i go 3-4 x a year now, for 1 week at a time. it acts like an offsite - get out of usual routine, meet interesting people, do lots of meetings (we'd normally avoid this sort of thing), get ideas and up our ambition, then go home and build stuff for 3 months quietly. repeat!
in the early days, if you fundraise, then at least SF based firms are way better to deal with in general, of course with many exceptions
PostHog helps engineers build better products by combining product analytics, feature flags, session replay, a data warehouse, CDP and many more.
* open source, building a dev tool. We have a public handbook (posthog.com/handbook) if you want to learn how we work, pay and more in complete detail.
* we are a real business... nearly at $20M ARR / profitability in sight / lots of capital / grew revenue 4x last year but only added 3 people / just had first cashflow positive month in October this year!
* you decide what to build, and iterate with your users - we are growing through autonomy and transparency not through process.
* we have a ton of scale and a bunch of super interesting technical problems to solve
* we're building 50 more products over the next couple of years, so you could end up building one of those
* we need: product engineer, technical founder engineers, backend leaning full stack engineer
posthog.com/careers