I don't understand the name Posthog. Seems like it is prompting users to upload photos of their penis.
Posthog – open-source analytics and UX research tool
21–30 of 43 posts
Re: Posthog – open-source analytics and UX research tool
#22Anyone know how it compares to mouseflow?
Re: Posthog – open-source analytics and UX research tool
#23Earlier quoted context omitted.
Fairly accurate, you can only get support if you're using their cloud product. "We no longer support paid, open-source deployments and it is no longer possible to buy licenses for self-hosted versions - we instead recommend migrating to PostHog Cloud." - from: https://posthog.com/docs/self-host
Why are they obligated to provide support for a free open source project?
OP's ask was: "Is this another one ... where open source is used more as a marketing gimmick"
My original comment wasn't intended to indicate that there is an obligation to provide support. The deliberate choice to: a) not offer paid support for open-source deployments, and b) sunsetting the Kubernetes deployments in favor of their cloud version, is a signal that shows PostHog doesn't /really/ want you to be running the software in a self-hosted manner.
Just look at the "Open-source hobby deploy" (from the README in git) which calls out that it "should scale to approximately 100k events per month" but their cloud offering gives you 1 million events per month for free. What is the point of the hobby "deploy"?
Back to OP -- my answer is yes, this is a source-available service that you can modify and play around with locally. The source and documentation behind the operations of PostHog aren't available.
Re: Posthog – open-source analytics and UX research tool
#24Earlier quoted context omitted.
That’s a pet peeve of mine so I’ll chime in. I’ve actually used it self hosted pretty much since posthog launched and moved to their cloud after a couple years. Our product blew up and it was difficult to scale, as well as a few hosted only features that we needed (by then we raised and could afford it). I also contributed code (and got some swag) which was promptly merged. They’ve also open sourced how they run the…
I tried to self-host recently and there was a lot of brokenness, and they discontinued the helm chart. They clearly don't want you to actually self host anymore and it's a shame. I have security requirements and can't yet afford their security-approved cloud product.
yeah it's been a while since I ran it, might have changed course (wouldn't surprise me)
Re: Posthog – open-source analytics and UX research tool
#25I don't understand the name Posthog. Seems like it is prompting users to upload photos of their penis.
I noticed that their twitter ads had comments disabled. This is probably why.
Re: Posthog – open-source analytics and UX research tool
#26Earlier quoted context omitted.
That’s a pet peeve of mine so I’ll chime in. I’ve actually used it self hosted pretty much since posthog launched and moved to their cloud after a couple years. Our product blew up and it was difficult to scale, as well as a few hosted only features that we needed (by then we raised and could afford it). I also contributed code (and got some swag) which was promptly merged. They’ve also open sourced how they run the…
I tried to self-host recently and there was a lot of brokenness, and they discontinued the helm chart. They clearly don't want you to actually self host anymore and it's a shame. I have security requirements and can't yet afford their security-approved cloud product.
What was broken? Part of discontinuing the helm chart was putting more effort into supporting the docker compose deployment so we’d love to fix this!
Re: Posthog – open-source analytics and UX research tool
#27Why is the self hosted version framed as a "hobby"? Is this another one of those enshittification of open source where open source is used more as a marketing gimmick instead of following it's true ethos?
(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.
Re: Posthog – open-source analytics and UX research tool
#28I don't understand the name Posthog. Seems like it is prompting users to upload photos of their penis.
it grabs (hogs all of) the output from http POST.
Re: Posthog – open-source analytics and UX research tool
#29Earlier quoted context omitted.
That’s a pet peeve of mine so I’ll chime in. I’ve actually used it self hosted pretty much since posthog launched and moved to their cloud after a couple years. Our product blew up and it was difficult to scale, as well as a few hosted only features that we needed (by then we raised and could afford it). I also contributed code (and got some swag) which was promptly merged. They’ve also open sourced how they run the…
I tried to self-host recently and there was a lot of brokenness, and they discontinued the helm chart. They clearly don't want you to actually self host anymore and it's a shame. I have security requirements and can't yet afford their security-approved cloud product.
Maintaining a helm chart is a non-zero amount of work - why do you think this should be provided for you?
Re: Posthog – open-source analytics and UX research tool
#30Earlier quoted context omitted.
Why are they obligated to provide support for a free open source project?
OP's ask was: "Is this another one ... where open source is used more as a marketing gimmick" My original comment wasn't intended to indicate that there is an obligation to provide support. The deliberate choice to: a) not offer paid support for open-source deployments, and b) sunsetting the Kubernetes deployments in favor of their cloud version, is a signal that shows PostHog doesn't /really/ want you to be running…
I disagree with the notion that oss is used as marketing bait.
a) offering paid support for bespoke selfhosted installations is an entirely different business model than building a managed service on your oss offering
b) maintaining k8s/helm charts is work - who is paying for that? The selfhosting users certainly aren’t and usually contributions are not enough and even then still need reviews.
You think it’s a deliberate choice. Yes it’s the choice between going out of business and continuing.